Early Access to Black Friday DealsFlyWP Lifetime Deal → Pay Once, Fly Forever
Grab Early Bird DealGranular team permissions
Invite developers, clients, and colleagues to FlyWP by email, then decide exactly what each person can reach: your whole team, specific servers, or specific WordPress sites. Role-based access control that keeps collaboration simple and sensitive systems protected.
WordPress team management works best when everyone can do their job and nothing more. Granular team permissions give each person the right level of access to the servers and sites they work on.
Get Started with FlyWPLimit Server and Site Administrators to the specific servers or sites they work on.
Invite people by email so each team member works from their own FlyWP account.
Billing and deleting the team stay with the team owner, whatever role others hold.
Update a member’s role or assigned resources at any time, and cancel invitations that are still pending.
FlyWP includes three predefined roles you can invite people into. Pick the one that matches each person’s responsibilities.
Whole team
The Administrator role gives broad access to every resource in the team. Invite it for the people who run your FlyWP account day to day.
Assigned servers
The Server Administrator role manages only the servers you assign, plus the sites on those servers. Invite it for developers and ops staff who look after specific servers.
Assigned sites
The Site Administrator role manages only the individual sites you assign, with no access to the server underneath. Invite it for clients, freelancers, and contributors working on specific websites.
Everything happens in Team Settings > Members.
Click Add New Member and enter the person’s email address.
Select Administrator, Server Administrator, or Site Administrator.
For Server or Site Administrators, select the specific servers or sites they can access.
Click Invite Member. FlyWP emails an acceptance link, and the invitation shows as pending until it’s accepted.
Need to change something later? Use Update Role to switch a member’s role or assigned resources, or cancel a pending invitation from the members list.
Administrators work across the whole team. Server Administrators work across the servers you assign. Site Administrators stay inside the sites you assign. Here’s how the three roles compare.
| Access area | Administrator | Server Administrator | Site Administrator |
|---|---|---|---|
| Scope | All team resources | Assigned servers and their sites | Assigned sites |
| Server configuration | All servers | Assigned servers | No access |
| Server services | All servers | Assigned servers | No access |
| Sites | All sites | Sites on assigned servers | Assigned sites |
| SSH keys | Server SSH keys | Server SSH keys | Site-level SSH keys |
| Team settings and members | Yes | No access | No access |
| DNS management | Yes | No access | No access |
| Billing and deleting the team | Team owner only | ||
Team access
From agency client work to in-house website teams, give each person the access their role calls for across your servers and sites. See FlyWP hosting for agencies, and pair team permissions with built-in security to keep every site protected.
Give developers Server Administrator access to client servers, and give each client Site Administrator access to their own website. See FlyWP hosting for agencies.
Bring in a contractor for one project with access to just the sites they’re working on.
Offer WordPress client access to individual sites while server configuration stays with your team.
Let IT manage the infrastructure while marketing and content teams look after the sites they own.
Direct answers about WordPress team permissions and server access in FlyWP.
Invite your developers, clients, and collaborators to FlyWP and give each one the access they need, nothing more.
