Workspaces and projects
A workspace holds people, plan and credits; a project is one website.
A workspace is the unit of membership, plan and credits. Every record belongs to exactly one workspace, and the database enforces that separation with row-level security, so one workspace can never read another's data.
A project is one website, identified by its canonical domain. It has its own audits, pages, business profile, connections, tracking, opportunities, proposals and activity.
Roles
| Role | Can |
|---|---|
| Owner | Everything a member can, plus: connect and disconnect services and keys, verify the domain, set autonomy, draft the profile with AI, rebuild page intelligence, save brand terms, remove a project, rename the workspace and read the credit ledger |
| Member | Read the workspace and do the day-to-day work: run audits, edit the profile, competitors and tracking, decide on opportunities, create, approve and execute proposals, run research |
Verification
A project is verified when you connect a Search Console or GA4 property whose site matches the project's domain. DNS TXT verification is also available for owners (Create challenge, then Verify domain).
Add and remove projects
Add a project from New project with a website address, or by saving a free audit. Adding a domain the workspace already has opens that project.
An owner removes a project in Project → Remove project, after typing its domain. The project leaves the workspace for everyone and no longer counts toward the plan; scheduled syncs, tracking and page intelligence stop. Its history is kept, and connections stay linked (disconnect Google or GitHub first to revoke access). Adding the same domain again brings the project back with everything it had, if the plan has room.
Limits
The Standard plan allows 3 projects in a workspace. Creating a fourth is refused with the plan limit; remove a project to make room.
Executing a change (a pull request or a CMS draft) needs a verified project.