# Resource-Specific Roles

> Give team members access to specific servers, sites, or DNS zones instead of the whole team.

Source: https://flywp.com/docs/account/granular-team-management/resource-specific-roles/

Resource-specific roles let you give a team member access to only the servers, sites, or DNS zones they need. Use them for developers, freelancers, clients, and auditors who should not see the rest of your team.

A member can hold several roles at once, for example Site Administrator on one site and Viewer on all servers.

![Member Access Drawer with granular server and site permissions](https://flywp.com/wp-content/uploads/2026/11/member-access-drawer-granular-roles.png)

:::note
Inviting members and editing their access needs a plan that includes the Team feature. On other plans the Members page shows **The team feature is not available on the current plan.**
:::

## Roles

| Role | Applies to | What it allows |
| --- | --- | --- |
| **Team Admin** | The whole team | Everything on every server, site, and DNS zone, plus members, team settings, and the White Label panel. Does not include billing. |
| **Server Administrator** | One server or all servers | Manage the server and its databases, cron jobs, daemons, firewall rules, and SSH keys. Create, manage, and delete sites on that server. |
| **Site Administrator** | One site or all sites | Manage and delete the site. |
| **Viewer** | A server, a site, or all of either | View servers, server status, cron jobs, daemons, firewall rules, SSH keys, and sites. Cannot change anything. |
| **DNS Manager** | One DNS zone or all zones of an integration | Work with DNS records through your connected DNS provider. |
| **Billing Manager** | The whole team | Manage plans, add-ons, cards, and invoices. Only the team owner can give or remove this role. |
| **White Label Manager** | The whole team | Manage the White Label panel: branding, domain, plans, customers, and email. Shown only when your team has White Label. |

A server role also covers every site on that server. A member with a server role cannot create, delete, or scale servers. Only a Team Admin or the owner can do that.

Docker Compose apps are stricter: only the owner and Team Admins can edit, deploy, change settings for, or delete them. Site Administrators can restart them.

:::tip
Give clients, junior developers, and auditors the **Viewer** role. They can see what is going on without being able to change anything.
:::

## Give a member access

1. Click your team name in the top bar and choose **Team**, or go to **Settings → Members**.
2. Click **Add New Member** to invite someone, or click **Edit Access** on a member's row.

   ![Team Settings Members page with the Add New Member button and the Edit Access button on a member row](https://flywp.com/wp-content/uploads/2026/11/nav-new-pages-1-members.png)

3. The drawer opens from the right. It is titled **Invite Team Member** for a new person, or **Edit Access** followed by the member's name. When you invite someone, enter their email first.
4. Choose the member's roles and permissions, as described below.
5. Click **Send Invitation**, or **Save Changes** when editing.

You cannot change your own access.

### Team Admin

Turn on **Team Admin** to give full access to every server, site, and DNS zone, including member management. The permission list is hidden while it is on, and any permissions you set there are ignored.

### Team-wide roles

These switches sit under **Team Admin** and work on their own:

- **Billing Manager**: Manages plans, add-ons, cards, and invoices. Only the team owner can turn it on or off.
- **White Label Manager**: Appears only if your team has White Label. A Team Admin already has the White Label panel, so the switch is locked on.

### Permissions

With **Team Admin** off, add one row for each resource the member needs:

1. Under **Permissions**, choose the type in the first dropdown: **Server**, **Site**, or **DNS**.
2. Pick the resource:
   - For **Server** or **Site**, search by name, or pick **All servers** or **All sites** to cover everything of that type, including ones you add later.
   - For **DNS**, choose a DNS provider under **Integration…** first, then a zone or **All zones**.
3. Choose the role. **Server** offers **Server Administrator** and **Viewer**. **Site** offers **Site Administrator** and **Viewer**. **DNS** always uses **DNS Manager**.
4. To add more, click **Add Another Permission**. To remove a row, click the trash icon on it.

A member can have up to 100 rows, and the same resource cannot be listed twice.

If another row already gives the same role, the row shows an amber note such as **Already covered by All servers** or **Already covered by the Production permission**. You can delete a covered row without changing what the member can do.

If **Team Admin** is off and the member has no team-wide role and no rows, the drawer warns **This member won't have access to anything in this team. Add a permission or make them a Team Admin.** The member list shows **No access** for them.

## Examples

- **Freelance developer**
  - Site: `clientapp.com`, **Site Administrator**
  - DNS: Cloudflare, zone `clientapp.com`, **DNS Manager**
  - Result: they can manage that site and its DNS records, and see nothing else.
- **Auditor**
  - Server: **All servers**, **Viewer**
  - Site: **All sites**, **Viewer**
  - Result: they can look at everything and change nothing.
- **Staging sysadmin**
  - Server: `Staging-VPS-01`, **Server Administrator**
  - Server: `Production-Cluster`, **Viewer**
  - Result: full control of staging, read-only on production.

## What members see

- **Navigation**: Menu items such as **Servers** and **DNS** only appear if the member's roles include them. A Viewer on a site, for example, can open **Servers** but only sees the servers they have access to.
- **Lists and search**: The server and site lists and the pickers show only what the member can access.
- **Server names**: On a site page, the server name is plain text instead of a link when the member has no access to that server.

## Related guides

- [Team Members](https://flywp.com/docs/account/granular-team-management/team-members/)
- [Remove a Team Member](https://flywp.com/docs/account/granular-team-management/removing-a-team-member/)
- [Team Activity Log](https://flywp.com/docs/account/granular-team-management/activity-log/)
- [Teams Overview](https://flywp.com/docs/account/granular-team-management/)
