Team & roles
A workspace can have more than one person in it. You invite teammates, and each one gets a role that decides what they can see and change. There's no per-plan cap on how many members you can add.
Manage everyone under Settings → Members.
Invite a teammate
From Settings → Members, choose + Invite, enter their email address, and pick a role. big emails them an invite with a Join button for your workspace. There's no link to copy and send yourself.
- Invites expire after 7 days. A pending invite shows whether its email went out. Use Resend to send a fresh one (you can resend once a minute). Resending replaces the invite, so the button in any earlier email stops working. Use Revoke to cancel it.
- Someone who's already a member can't be invited again. To change what they can do, change their role in the member list instead.
- To protect people's inboxes, there's a daily limit on how many invite emails a workspace can send, and on how many any one address can receive.
Accepting an invite
Your teammate opens the email, chooses Join, and signs in with Google using the same address the invite was sent to. If they don't have a big account yet, this creates one.
If they open the invite while signed in to big with a different Google account, big tells them which address it's for and offers Switch account. That signs them out and brings them straight back to the invite with the right account. Joining always takes one more click on the invite page (Accept and open your workspace), and they land in your workspace when they do.
Switch between workspaces
Everyone has their own workspace, and you can also be a member of other people's. Accepting an invite doesn't take you out of yours.
When you belong to more than one, a workspace switcher appears at the top of the sidebar (on a phone, at the top of the screen). It lists Your workspaces and Shared with you, with your role in each. Pick one to move there. big remembers your choice on that browser until you switch again or sign out.
API tokens and MCP connections are tied to the workspace they were created in, so switching in the dashboard doesn't change what an existing token can reach. To use the CLI or an agent in another workspace, switch to it here first and create a token (or connect the remote MCP client) there. Switching is dashboard-only.
The four roles
Roles are ranked owner > admin > editor > viewer. Each higher role can do everything the one below it can, plus more.
| Role | Can do |
|---|---|
| Viewer | Read-only. See automations, conversations, contacts, connections, integrations, links, link pages, forms and client records, the member list, and the billing page — but not change anything. |
| Editor | Everything a viewer can, plus make changes: build and toggle automations, react in the inbox, tag contacts and set lead status, create or delete short links, edit link pages and forms and delete forms. |
| Admin | Everything an editor can, plus invite people and manage editors and viewers, publish and unpublish forms and link pages (and approve a publish someone requested), erase a contact, manage integrations (connect, reconnect, rotate, re-verify, disconnect), set up client records in Notion, sync past calls, and see and revoke every member's API tokens. |
| Owner | Everything. Only the owner can promote, demote or remove admins, change billing, export or delete the account, and link a coach to a member's login. |
Every role can see the member list, open the billing page and create API tokens. A token is capped by its creator's role — it can never do more than that role allows — and the cap is re-checked on every request, so a demotion shrinks the person's existing tokens at once. Each member sees and revokes their own tokens; admins and the owner see and can revoke everyone's in the workspace. Sending a DM by hand isn't available yet for any role — automations still reply.
Members, invites, roles, billing and API tokens are dashboard-only: no API token, CLI command or MCP tool can reach them, and a token sent to one of those endpoints gets 403 with code: dashboard_only.
Rules worth knowing
- Only the owner can promote or demote admins, or remove an admin.
- You can't remove or change your own role.
- Integrations belong to the workspace, not to the admin who connected them. Demoting or removing that admin doesn't disconnect anything. Connecting, reconnecting, rotating and disconnecting happen only in the dashboard; an API token can at most read an integration's status, and no role, token or member of big staff can read a stored credential. See Integrations.
- There's exactly one owner, and ownership can't be transferred yet — not from Settings → Members, and not by any API. If you need to hand a workspace to someone else, contact support.
Change a role or remove someone
From Settings → Members, pick a member to change their role or remove them from the workspace. Admins can manage editors and viewers; only the owner can manage admins.