GoBuildWP Cloud Team and Client Access: Roles and Seats
Set up GoBuildWP Cloud team and client access: invite admins and members, give clients a read-only view of their sites, and know the seats each plan has.
A Cloud workspace starts with one person, the owner who created it. On a Pro plan with team seats you can bring in the people who look after the sites, and give a client a view of their own sites in Cloud: no WordPress login, nothing they can change, and only the sites you pick.
What you will do 6 steps
Check your plan's seats
Open Team in Cloud
Enter an email and pick a role
For a client, pick their sites
Send the invite
The person accepts with that address
Roles in a workspace
Owner: the account that created the workspace. Licences stay with the owner, and the owner cannot be removed. Admin: everything except licences, including the team. Member: runs the sites, which means updates, backups, safety policies and AI connections. Client: sees only the sites you pick, read-only.
Owners and admins can invite people, change roles and remove people. Only the owner can invite, promote, demote or remove an admin. Nobody can change their own role.
Seats on each plan
Seats count people, the owner included, and open invites count until they are accepted, withdrawn or expire. From 10 Sites up, clients and client invites take no seat. Without a Pro licence a workspace has 1 seat, the owner's. With Pro: Single Site: 1 person; 10 Sites: 3 people; 100 Sites: 10 people; Unlimited Sites: no limit.
Clients do not take a seat on the 10 Sites plan and above. On Single Site and without Pro they would, and since the owner already fills the one seat, those workspaces have no room for anyone else. When every seat is taken, the Team screen says so; on plans where clients are free, it still lets you invite clients.
Invite someone
Open Team in Cloud, enter the person's email under Invite someone, and choose a role. For a client, tick the sites they may see; a client invite needs at least one. Select Send invite.
They get an email with a link. They sign in, or create a free Cloud account, with that address, confirm it, open the link and select Accept and join. An invite stays open for 7 days; after that, send a new one. Open invites are listed on the Team screen with their expiry date, and Withdraw cancels one.
Joining your workspace does not touch the person's own: anyone in more than one workspace switches between them in the sidebar.
- The address the person really signs in with
- The right role
- A client's sites ticked
- Accepted within 7 days
What a client sees
A client sees the sites you shared and nothing else: each site's status, its pending updates and its last backup. They cannot start updates, backups or bulk runs, see safety policies or the SEO report, create tokens or see licences. Sites you did not tick do not appear for them at all.
To change which sites a client sees, find them under Members, change the ticked sites and select Save. Changing a client into a member takes a seat, so it needs a free one.
Remove someone
Select Remove from workspace on their row. Their AI connections and personal access tokens for this workspace are revoked with them, and the gateway refuses any connection whose person is no longer a member. Anyone except the owner can also leave a workspace themselves.
Questions this guide answers
Does a client need a WordPress login?
No. A client signs in to GoBuildWP Cloud with the address you invited and sees status, pending updates and last backup for the sites you shared, without access to wp-admin.
Do clients count as seats?
Not on the 10 Sites plan and above. Without Pro and on Single Site they would, and the owner already fills the one seat those plans have.
What happens to an invite nobody accepts?
It expires after 7 days and stops holding a seat. Send a new invite if the person still needs access.
Review noteRequirements and credential methods follow the shipped GoBuildWP source (WordPress 6.9+, PHP 8.0+). Client menus, account plans and third-party behaviour can change; use the installed version and live schema. Our evidence standard.