1.3 · Find your way around
Accept the invitation, sign in, and learn the 5 areas GrowthOS is organized around.
Accept the email invitation sent to you, sign in (Google, or email and password), and you land in your workspace, the container holding everything GrowthOS knows and does for your brand. From there, GrowthOS is organized around the work, not around features: one area to see where you stand, one to manage your pages, one to create new ones, one for reports, and one that holds what the system knows about your business. Once you know which door leads where, nothing in the product is more than 2 clicks deep.
This guide tours the layout, explains the two roles, and covers both ways to bring teammates in.
The areas
The top bar carries 5 tabs. During onboarding some arrive locked and open in stages, which is covered in the previous guide.
| Tab | What lives there |
|---|---|
| Home | At a Glance: your workspace's current state, momentum, and what needs attention |
| Pages Portfolio | The Pages Portfolio: every page on your site, scored and classified, one record per URL |
| Page Creation | The production floor, in 3 views: In Production, Opportunities (proposed pages worth writing or rewriting), and Clusters (groups of related opportunities around one topic) |
| Insights | Your reports, ready to read and share |
| Context | Your context, what GrowthOS knows about your business: foundation docs, personas, competitors, taxonomy, and your writing profile, the compiled version of how you sound |
A rough map to the rest of this tutorial: stage 3 happens in Context, stage 4 in Page Creation's Opportunities and Clusters views, stage 5 in In Production, and stage 6 in Insights.
The two roles
A teammate with a seat holds one of two roles.
| Role | What it's for |
|---|---|
| Operator | Runs content operations day to day: research, assignments, and publishing to connected CMS platforms |
| Owner | Full workspace access. Does not include CMS publishing |
Both roles see and manage the same day-to-day surfaces: pages, opportunities, drafts, reports, and context. The differences sit at the edges: the person who will push pages live needs Operator, and the person who owns the account needs Owner. The full breakdown is in Roles and permissions.
Invite a teammate
Open Manage Users
Click the workspace logo in the top left and choose Workspace Admin, then Manage Users in the left rail. The Team Members page lists everyone with access and what they can do.
Send the invitation
Click Invite, enter their email, pick a role, and click Send Invitation. They get an email with a signup link, and the moment they finish signing up they land in the workspace with the role you chose. If they already have a GrowthOS account, they're added instantly with no email step.
Pending invitations appear below the members list, where you can resend, change the role, or cancel. From a member's row menu you can change their role or remove them later.
3 guardrails apply to everyone: no one can remove themselves, no one can change their own role, and a workspace must keep at least one Operator. When you genuinely need one of those changes, ask your GrowthX team.
No seat needed: magic links
Not everyone who touches the work needs an account. Two kinds of magic link give someone exactly one job's worth of access:
| Link | What the recipient can do | Where you create it |
|---|---|---|
| Review link | Read a draft, highlight passages, and leave notes. No login | A draft's Invite Feedback step, covered in stage 5 |
| Report link | View a finished report | The Share button on any report, covered in stage 6 |
The rule of thumb: if someone will do this weekly, give them a seat. If you need their eyes once, send a link. Both link types are revocable at any time.
Common questions
Who should get seats first? The person running content day to day (Operator) and the person who owns the engagement (Owner). Add subject-matter reviewers later as magic-link guests, and upgrade them to seats only if they end up in the workspace weekly.
Why can't I invite my GrowthX contacts? GrowthX team members have their own access path, so the invite form only takes emails from your own team.
Last updated at August 13, 2026