Workspace invitations, seats and roles

A workspace groups private actions and collaborators under an owner. Its plan capacity belongs to that owner. Inviting someone to a paid workspace does not rename the invitee’s personal plan, and an invitee’s own paid account does not increase a free owner’s workspace capacity. Seats include current members and unexpired pending invitations so a team cannot overbook its allowance.

Create the workspace and invite people

Sign in, open Workspaces and create a name that explains the project. Use Invite by email and select the intended role. The invitation is recipient-bound and expires; the recipient must sign in with the intended account and accept it. Forwarding the link does not grant a different person membership. Review the email address before sending. If a person was invited under the wrong address, revoke the pending invitation and issue the correct one. Do not ask the recipient to share a login with another member. When the team reaches its seat limit, remove an unused pending invitation or review the owner’s plan before inviting another person.

Understand the roles

The owner controls workspace membership and the owner’s billing relationship. Editors can work on workspace actions and their configuration, subject to server-side permissions. Viewers can read and respond, join discussion and complete responsibilities assigned to them; they cannot configure workspace actions or manage membership. The available controls reflect the actual role; a hidden button is not the only security check. Editing permission does not automatically include deletion permission. Treat membership changes as operational decisions, especially when a project includes sensitive discussions. A person removed from a workspace loses future authorized access, but the system cannot recall screenshots or information previously copied outside the site.

Use the licensed workspace

Choose the workspace in the action builder and use private visibility when the project needs restricted access. Actions created in that workspace use the owner’s resource allowances, including participant capacity and eligible planning or branding features. Capture and optional provider-AI requests made in workspace context use the owner’s shared monthly pool. A personal action outside the workspace uses its creator’s personal plan. If a collaborator sees an unexpectedly small allowance, check which workspace is selected before assuming the plan is broken. Upgrading a collaborator separately does not necessarily change the existing workspace owner’s limits.

Resolve an invitation problem

Confirm that the recipient signed in to the invited address, the invitation has not expired and a seat remains reserved. Ask the owner to check whether the invitation was revoked or already accepted. An action being paused, pending or archived can still prevent access after membership succeeds. If a role seems wrong, the owner should review the membership list. Do not make a private action public merely to get around an invitation error. Support needs the workspace name, stage of the problem and exact error, not an invitation token, password or private participant content.

Continue with related help

• Discuss actions and assign responsibilities

Search the help center · Current plans and limits · Contact support

Still need a hand?

The site assistant can find related guides. For an account-specific issue, use the support form and include the page URL and exact error, without passwords or payment details.

Contact support ↗