How to Manage Teams, Roles, and Permissions in xCloud

Updated November 20, 2026 · 7 min read

Summarize with:
Share:

xCloud teams let you collaborate without sharing the team owner’s account. Each member receives a role, access to specific servers or sites, and only the permissions needed for their work.

See the Team roles feature page for what it does, who it is for and which plans include it.

This guide explains the complete team-management workflow: creating and switching teams, inviting members, sharing or resending pending invites, accepting or declining invitations, managing roles and resource access, requiring two-factor authentication, removing members, leaving teams, and deleting teams.

Prerequisites

  • An active xCloud account.
  • A plan that supports additional teams or team members for the actions you want to perform.
  • Team Owner or Team Admin access to invite or manage members.
  • The email address of each person you want to invite.
  • At least one server or site in the team if you want to grant access to selected resources only.

Open Team Management

  1. Sign in to the xCloud dashboard.
  2. Open your account menu and select All Team.

The All Team page shows:

  • Your personal team, marked Primary.
  • Other teams you own.
  • Teams you have joined.
  • Pending invitations from other teams.

The team you switch to becomes your current workspace and displays that team’s resources and members.

Create a team

  1. Open All Team.
  2. Select Add New Team.
  3. Enter a Team Name and Team Email.
  4. Optionally add Tags and a team avatar.
  5. Select Save Changes.

Enter the Team Name and Team Email, and optionally add Tags.

Expected result: xCloud creates the team and lists it on the All Team page. You are the team owner.

Understand team roles

A role sets the maximum permissions a member can receive. Resource access then limits which servers or sites the member can use.

Role Intended access
Owner Full team control, including team deletion and owner-level billing responsibilities. The owner is created with the team.
Team Admin Broad team, provider, server, site, and support capabilities allowed by the role. Team Admins can perform supported team-management actions.
Server Admin Manages permitted servers, their sites, and the server-level actions enabled for the role.
Site Admin Manages permitted sites and the site-level actions enabled for the role.

The role is only one part of access control:

  • Role sets the member’s maximum capability.
  • Resource access determines which servers or sites the member can reach.
  • Role permissions determine which allowed actions the member can perform on those resources.

Invite a team member

1. Open the team

  1. Go to All Team.
  2. Open the menu for the team you want to manage.
  3. Select Manage Team.
  4. Select Add New Member.

Expected result: xCloud opens the invitation form with fields for the member’s email address, role, resource access, and role permissions.

2. Enter the member and choose a role

  1. Enter the member’s email address.
  2. Under User Role, select Team Admin, Server Admin, or Site Admin.

The form displays server access for Team Admin and Server Admin, or site access for Site Admin.

3. Choose server or site access

Choose one of three resource-access modes:

Access mode Current resources Resources created later Individual selection
All servers/sites Every resource in the team Added automatically Blanket access; individual resources cannot be excluded
Chosen servers/sites, plus new ones Only the resources you select Added automatically Selected resources can be changed later
Chosen servers/sites only Only the resources you select Not added automatically Future resources stay hidden until selected manually

For Team Admin or Server Admin, configure Server Access. If you choose a selected-resource mode, use the picker to add the initial servers.

Server access controls which current and future servers the member can reach.

For Site Admin, configure Site Access and select the initial sites when required.

Site access limits a Site Admin to all sites or a selected set of sites.

4. Configure role permissions

Use Allow new features automatically to decide how permissions offered by the selected role are maintained.

Automatic permission management can include eligible permissions added to the selected role later.

Setting Behavior
Enabled Grants every automatically managed permission offered by the selected role, including eligible permissions added to that role in future releases. It never grants permissions above the selected role.
Disabled Lets you select the currently available permissions individually. Future permissions are not added automatically.

Permissions labeled Grant by hand remain manual even when automatic management is enabled. Select each of those permissions separately when the member needs it.

5. Send the invitation

Review the email address, role, resource access, selected resources, and permissions. Then select Send Invitation.

Expected result: The invitation appears under Pending invites on the Team Management page until the recipient accepts or declines it.

Manage pending invites

The Team Management page lists people you invited who haven’t joined yet in their own Pending invites section, below the team members. Each row shows the invitee’s email, role, server count and the date you invited them.

People who can manage team members also see each invite’s link and these actions:

Action What it does
Copy Link Copies the invite link, the same link the invitation email carries. Send it through chat or another channel when the email doesn’t arrive.
Change Role Changes the role, access and permissions the person gets when they accept.
Resend Email Sends the invitation email again.
Delete Cancels the invitation after you confirm.

To share an invite link:

  1. Open All Team and select the team.
  2. Scroll to Pending invites on the Team Management page.
  3. Select Copy Link on the person’s row.

Select Copy Link on the invite row in the Pending invites section of Team Management

Expected result: xCloud confirms that the link is copied, says which email address can use it, and that it expires in 7 days.

The link only works for the invited email address: the person must sign in or sign up with that address to join. It expires 7 days after it is created. If it has expired, copy it again from Pending invites or select Resend Email. To invite another person, select Add New Member at the top of the page.

Accept or decline another team’s invitation

When another team invites you, the pending invitation appears on your All Team page.

  1. Open All Team.
  2. Find the invitation under the pending invitations section.
  3. Select Accept to join the team, or Decline to reject the invitation.

Use Accept to join the inviting team or Decline to remove the invitation.

Expected result: After you accept, the team appears in your team list and you can switch to it. Declining removes the invitation without adding you to the team.

Change a member’s role, access, or permissions

  1. Open All Team and select the team.
  2. Find the member on the Team Management page.
  3. Select Change Role.
  4. Update the role, server or site access, selected resources, or role permissions.
  5. Select Update Member.

Expected result: xCloud applies the updated role boundaries, resource access, and permission settings to the membership.

When you change a member’s role, review every setting again. Site Admin uses site access, while Team Admin and Server Admin use server access, so the available resource selector changes with the role.

Who can change a deploy script

Only the team owner and members with the Manage deploy scripts permission can set or change a deploy script. A deploy script runs on your server after every later deploy, so this permission is labeled Grant by hand and is never granted automatically. Team Admin, Server Admin and Site Admin are all offered it. Members who could already edit deploy scripts before this permission existed kept that access.

The permission also covers the rest of a site’s Git settings, such as the branch, plus the staging push and pull scripts.

The member also needs Manage update to open Git Settings. Manage deploy scripts comes on top of it and doesn’t replace it.

Only the team owner, or a Team Admin who already has this permission, can grant it. To grant it:

  1. Open All Team and select the team.
  2. Find the member on the Team Management page.
  3. Select Change Role.
  4. Type deploy in Filter permissions….
  5. Tick Manage deploy scripts.
  6. Type update in Filter permissions… and make sure Manage update is ticked.
  7. Select Update Member.

Tick Manage deploy scripts, labeled Grant by hand, in the member’s permissions

Expected result: The member can now change the deploy script. On the site’s Git Settings page, the script is editable and the read-only notice is gone.

A member without the permission can still deploy from Git. They see the standard script read-only and can’t replace it: see Deploy via Git and Custom Docker from Git. Laravel and PHP apps have a standard script. Other app types, such as Node.js, don’t, so the Build & deploy script switch starts off. With it off, xCloud runs npm install, plus the build command if it detected one in your repository. If your app needs a build step that xCloud didn’t detect, ask a team admin for the permission. Turning the switch on without the permission doesn’t help: the box is empty and xCloud asks for a script.

On an existing site, a member with Manage update but not Manage deploy scripts can open the Git Settings page (Git in the site menu). It shows them a notice, and Save and deploy and Save Changes stay disabled.

The notice on Git Settings for a member without the permission, with both save buttons disabled

Remove a team member

Removing a member detaches them from the team and removes access granted through team, server, or site invitations. It does not delete the person’s xCloud account.

  1. Open the team from All Team.
  2. Find the member on the Team Management page.
  3. Confirm that you selected the correct member.
  4. Select Delete beside that member.
  5. Confirm the removal when prompted.

Use Delete on the member’s row to remove that member from the team.

Expected result: The member disappears from the team list, and their team, server, and site access associated with that membership is removed. Their xCloud account is not deleted. The team owner cannot be removed as a member.

Switch to another team

  1. Open All Team.
  2. Open the menu for the team you want to use.
  3. Select Switch to Team.

The team menu provides the actions available for that team and your membership.

Expected result: xCloud changes your current workspace to the selected team and loads that team’s resources.

Leave a team

You can leave a team you joined, but you cannot leave a team you own.

  1. Open All Team.
  2. Open the menu for the joined team.
  3. Select Leave Team.
  4. Confirm the action.

Expected result: The team is removed from your team list and your access to its servers and sites ends.

If you need to leave the team that is currently active, switch to another team first.

Edit a team

Team owners and authorized Team Admins can update supported team details.

  1. Open All Team.
  2. Open the menu for the team.
  3. Select Edit from the team menu, or select Edit Team from the team’s management page.
  4. Update the available team details.
  5. Select Save Changes.

Expected result: xCloud updates the team’s displayed information without changing its owner or memberships.

Require two-factor authentication for your team

You can make two-factor authentication (2FA) mandatory for everyone in a team. Members without 2FA then can’t use the team’s servers, sites or settings until they turn it on for their own account. This keeps a stolen password from opening your team’s servers.

Turn on 2FA for your own account first. If you haven’t, xCloud refuses to save the setting with: “Turn on two-factor authentication for your own account before requiring it from the team.” See Two-Factor Authentication to set it up.

Step 1: Turn on the requirement

  1. Open All Team and select the team.
  2. Select Edit Team.
  3. Tick Require two-factor authentication for all members.
  4. Select Save Changes.

Tick Require two-factor authentication for all members on the Edit Team page

Expected result: The team’s Team Management page shows a 2FA required badge next to the team name.

Step 2: Check who still needs to turn on 2FA

On the Team Management page, the 2FA column shows Enabled or Not enabled for each member. Only people who can edit the team see this column.

The 2FA column on Team Management shows Enabled or Not enabled for each member

Ask each member marked Not enabled to turn on 2FA.

What members without 2FA see

A member without 2FA who opens the team is sent to their Authentication settings, with the notice Your team requires two-factor authentication. Until they turn on 2FA, they can only:

  • open their Authentication settings to turn on 2FA (members who signed up with Google or GitHub set a password there first),
  • switch to another team,
  • open the payment page.

The same applies when they open a link to one of the team’s servers or sites while another team is selected. As soon as they turn on 2FA, they can use the team again.

To remove the requirement, untick Require two-factor authentication for all members in Edit Team and select Save Changes.

Delete a team

Warning: Deleting a team is irreversible. xCloud removes the team’s services, sites, and other associated data, and that data cannot be recovered. Back up anything you need before continuing.

Only a deletable team that you own can be removed. You cannot delete your personal team or your current team. Switch to another team first if Delete Team is unavailable because the target is current.

  1. Open All Team.
  2. Open the menu for the team you own and select Delete Team. You can also open the team and use Delete Team from its management page.
  3. Read the deletion warning.
  4. Select the acknowledgement checkbox.
  5. Enter the exact team name.
  6. Select Delete.

Deletion requires both an acknowledgement and the exact team name.

Expected result: xCloud permanently removes the team and its associated resources and data.

Limits and edge cases

  • Additional team members are unavailable on the Free plan. Upgrade the team before inviting members.
  • Team-member limits depend on the team’s plan.
  • All servers/sites includes current and future resources; individual resources cannot be excluded in this mode.
  • Chosen servers/sites, plus new ones adds future resources automatically while retaining individual resource control.
  • Chosen servers/sites only never adds future resources automatically.
  • Automatic permission management remains limited by the selected role.
  • Permissions labeled Grant by hand are never granted automatically. That includes Manage deploy scripts.
  • Ownership, team deletion, and owner-level billing responsibilities remain with the team owner.
  • You cannot delete your personal team or the team that is currently active.
  • Only people who can edit the team see the 2FA column and can require two-factor authentication.
  • Invite links work only for the invited email address and expire after 7 days.

Troubleshooting

Problem What to check
Add New Member is unavailable Confirm that your plan supports additional members, the team has not reached its member limit, and you have Team Owner or Team Admin access.
A member cannot see a server or site Check both the member’s resource-access mode and the selected server or site. Role permissions alone do not grant resource visibility.
A member can see a resource but cannot perform an action Open Change Role and confirm that the required role permission is enabled. Check Grant by hand permissions separately.
A member sees “ask a team admin for the Manage Deploy Scripts permission” Open Change Role and tick Manage deploy scripts. Only the team owner, or a Team Admin who already has this permission, can grant it. It is a Grant by hand permission, so Allow new features automatically does not include it.
A newly created resource is hidden from a member Use All servers/sites or Chosen servers/sites, plus new ones, or add the resource manually to a chosen-only membership.
Delete Team is disabled Confirm that you own the team, that it is not your personal team, and that it is not your current team.
A member keeps landing on the Authentication page The team requires two-factor authentication. The member turns on 2FA under Authentication, or you remove the requirement in Edit Team.
xCloud won’t save Require two-factor authentication for all members Turn on two-factor authentication for your own account first, then save again.
An invitee says the invite link doesn’t work The link works only for the invited email address and expires after 7 days. Copy a fresh link from Pending invites or select Resend Email.
Leave Team is unavailable Team owners cannot leave teams they own. Joined teams show Leave Team when leaving is allowed.

FAQ

Why can’t my Team Admin change a deploy script?

Changing a deploy script needs the Manage deploy scripts permission, and no role gets it automatically. The team owner always has it. Anyone else needs it ticked by hand under Change Role, whatever their role, unless they could already edit deploy scripts before this permission existed.

Does automatic permission management give a member every xCloud permission?

No. It grants only automatically managed permissions offered by the selected role, including eligible permissions added to that role later. It does not grant higher-role permissions or items labeled Grant by hand.

What is the difference between “plus new ones” and “only”?

Both modes start with the resources you select. Plus new ones automatically adds resources created later; only keeps future resources hidden until you add them manually.

Can I exclude one server or site while using “All” access?

No. All servers/sites is blanket access. Use one of the chosen-resource modes when you need individual exclusions.

Can I change access after an invitation is accepted?

Yes. Open the member from Team Management, select Change Role, update the role, resource access, selected resources, or permissions, and save the changes.

Does removing a member delete their account?

No. It removes the membership and access associated with that team. The person’s xCloud account remains available to them.

What happens to members without 2FA when I require it?

They can only open their Authentication settings, switch to another team or open the payment page until they turn on two-factor authentication. Once they turn it on, they can use the team again.

Only people who can manage team members see the Invite link column and Copy Link. The link works only for the invited email address and expires after 7 days.

Can I transfer team ownership from Team Management?

The team-management controls covered in this guide do not include an ownership-transfer action.

Next steps

Review team membership regularly, especially after creating new servers or sites, changing a member’s responsibilities, or enabling automatic access to future resources. Remove members who no longer need access and keep destructive team deletion as a last resort. If a server belongs in a different team, you can move the server to another team or account instead of deleting it. To check who on your team did what over the last 30 days, open View All Events in the events menu at the top of the dashboard. To get the same list from a script or an AI agent, see team activity with the xCloud Public API and MCP.

If you run into any issues while managing your team, feel free to reach out to our support team.