Skip to main content
Everyone works inside one organization. A person belongs to exactly one — there is no switching between customers’ workspaces, and no way to be in two. Team management lives on the Team page: Add Member, Create Role and Assign Role.
The Team page listing member cards with names, email addresses and role badges reading Owner and All Permissions or a permission count, beside a roles section and Add Member, Create Role and Assign Role buttons

The Team page.

​
Invite someone

Press Add Member. You need their email address and their name; both are required. What happens next is worth knowing, because it is not an invitation link:
1

An account is created immediately

AutoGrowth makes the user there and then, with a generated temporary password, and puts them in the Member role.
2

They get an email with credentials

The subject is “Welcome to” and your organization’s name. It shows their Email Address and their Temporary Password, with a Verify Email & Get Started button.
3

They verify and change the password

The email says it: “We recommend changing your password after your first login.” Nobody can sign in before verifying.
An address that already has an AutoGrowth user is refused with “This email is already registered”. There is no limit on how many people you add. The things you buy by the seat are phone slots and container licences, not users.

​
Owners and members

There are two seeded roles and no hidden third one.
  • Owner — the person who signed the organization up. An owner passes every permission check without exception and sees every phone. There is exactly one, set at signup.
  • Member — everyone else. A member starts with no permissions at all, and is given them through a role.
Custom roles are how you actually hand work out. Create Role, tick the permissions it should carry, then Assign Role to put someone in it. The Owner role cannot be edited or handed out, and deleting a custom role puts its people back on Member rather than leaving them stranded. Anything a role does not cover is refused with the same short message everywhere: Insufficient permissions.

​
The permissions

There are 24, in eight groups. These are the exact labels on the role editor. Two of these decide more than they look like they do:
  • Remote control devices covers driving a phone from the browser and managing its agent — and, on GrapheneOS phones, saving the keyguard PIN that unlocks a profile.
  • Manage billing is what lets someone spend the organization’s credit balance.

​
What a member sees

Permissions decide what someone can do. Two separate rules decide what they can see.
  • Phones. A member sees only the phones assigned to them, plus any phone carrying one of their tags. Everything else is absent from their Fleet page. Owners see all of them. Assign phones and tags from the phone’s card — see Your fleet.
  • Their own work. Accounts, content, prompts and runs are scoped to the person who created them.

​
Removing someone

Removing a member deletes their user account and everything attached to it — their tracked accounts, their uploaded content, their prompts, their scheduled and completed runs, their API keys and their workflows. It is not a suspension, and there is no undo.The organization’s phones are kept.
You cannot remove yourself, and you cannot remove the owner. There is also no ownership transfer and no way to leave an organization on your own. The owner is set once, when the organization is created; if it has to change, that is a support matter — see Getting help.

Your fleet

Assign phones and tags, which is what member visibility runs on.

Credits and billing

Credits, slots and licences — and who is allowed to spend them.