Access and roles
Growth-OS belongs to our team. There is no plan and no checkout. You get in because an owner or an admin invites you, and your role decides what you read, change and approve.
How you get in
Four steps, and a person decides at every one of them.
Ask a colleague
01Access starts with a person, not a checkout. Say which project you need and what you will do there. If you are not in the workspace yet, the contact page reaches us.
An owner or admin invites you
02The invitation goes to your email address from team settings, with your role on it. It covers the organization or one project, and it expires after fourteen days.
Sign in
03Sign in with the Google account for the invited email address. An account on its own is not access. Accepting the invitation creates your membership.
Open your project
04You land in the project you were invited to. Start at Today: what changed, what needs attention and what is waiting on a decision.
What each role can do
Four ranks. The server checks your current membership on every request, so what a page hides was never the protection.
Viewer
Read the records, discuss them, comment on a roadmap request and cast a vote when the voting group includes you. You edit nothing and finance stays closed. Advisory can also read shared finance records, without salaries.
Editor
Everything a viewer can do, plus creating and changing records: companies, people, meetings, evidence, decisions, campaigns, content. No finance and no salaries. First hire has the same access.
Admin
Everything an editor can do, plus people, settings and the finance pages, salaries included. Invitations and role changes live here. Founder has the same access.
Owner
Full access to the organization, its projects and its numbers. Ownership moves through its own transfer and never through an invitation.
What your access covers
Most of the work belongs to a project. People, settings and money have their own boundary.
A project
Records, meetings, decisions and finance entries belong to one project, and a link between records has to stay inside that same project. A project invitation gives you that project and nothing else, and never team management across the organization.
The organization
People, settings and ownership belong to the organization. An organization membership reaches its projects, and an explicit project membership replaces the role you would inherit there. Owners keep their access either way.
Finance
Admins see all seven finance pages. Advisory sees only explicitly shared records and customer payments; salaries, budgets and private files remain restricted.
Questions about access
No access to Growth-OS yet?
Say which project you need and what you will do there. An owner or an admin invites you and picks your role.