SurfacedBySurfacedBy Docs

Workspaces and Roles

Multi-domain workspaces, the command center home, and team roles.

Ask an AI:Open in ChatGPTOpen in Claude

A workspace is the container for the brands you track, the team that works on them, and the plan that pays for it. One workspace can hold many domains, so an agency running several brands or an owner running several of their own sites manages everything from one place. The command center is the workspace home; it summarizes every brand in the workspace and points you at what needs attention.

Multiple domains in one workspace

A workspace holds as many domains as your plan allows. Each domain has its own scans, analytics, opportunities, and actions, and the workspace ties them together for billing, team access, and the cross-domain view. You can belong to more than one workspace, and switching between them changes which set of brands you are looking at.

When a workspace holds a single domain, the dashboard links straight to it. When it holds several, the command center is the landing surface and you move into a specific brand from there.

The command center

The command center is the cross-domain home for a workspace. It brings together a portfolio view of every brand you track, an attention queue that surfaces what needs action across domains, and trends across the workspace, so you can triage many brands without opening each one.

To keep a large portfolio manageable, the command center supports a few organizing tools:

  • Groups. Organize the brands in a workspace into named groups.
  • Assignments. Assign team members to specific brands so the right person owns the right work.
  • Saved views. Save and share filtered views of the portfolio so the team starts from the same lens.

Throughout the dashboard a tracked website is a brand or a domain, never a client; the workspace serves both agencies and owners running several of their own brands.

Team roles

Every member of a workspace has one of four roles. They form a hierarchy: owner, admin, editor, viewer, each able to do everything the role below it can plus more.

  • Owner. Full control of the workspace. Owners alone manage billing and the subscription, delete the workspace, remove members, and transfer ownership. There is one path to a new owner: an existing owner transfers ownership, which makes the previous owner an admin.
  • Admin. Manages the account and its structure: adding and removing domains, inviting and updating members, renaming the workspace, managing API keys, webhooks, and MCP connections, connecting integrations, and organizing the command center. Admins do everything except the owner-only billing and ownership actions.
  • Editor. Does the day-to-day work: managing tracked prompts and competitors, working the plan and opportunities, generating and publishing content, running tools, and approving engagement and outreach. Editors act on the data but do not manage the account.
  • Viewer. Reads everything in the workspace and changes nothing.

Permissions are resolved per action against this hierarchy, so a member below the required role for an action is told they cannot perform it.

Inviting members

Admins and owners invite members by email and assign the new member's role at the time of the invite. An invite can be scoped to specific domains, so a member sees only the brands they are meant to work on rather than the whole workspace.

The invite is sent as a signed link that expires after a set period. Until it is accepted, the invite is pending; admins can list pending invites, resend them, or revoke them. Accepting an invite requires the recipient to be signed in with the same email the invite was addressed to, which is verified when they accept. Once accepted, the member joins the workspace with the role and domain scope the invite carried.

Per-plan limits

How many standalone workspaces you can create depends on your plan tier. Every account starts with a personal workspace, and higher tiers unlock the ability to create more. See the Plans page in the dashboard for the limits on your tier.

On this page