> ## Documentation Index > Fetch the complete documentation index at: https://docs.autogrowth.farm/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > AutoGrowth runs social accounts on real phones. Everything a page describes happens on a physical device in the customer's own fleet, never through a social platform's API. > The Companion is a macOS desktop app that runs on the customer's own Mac and manages the phones over USB — iPhones through WebDriverAgent, GrapheneOS phones through ADB and scrcpy. Nothing runs while the Companion is closed. > The Companion builds, signs and installs WebDriverAgent on each iPhone itself. Never tell a customer to sign WebDriverAgent by hand in Xcode; Xcode is a prerequisite the Companion drives, not a step the customer performs. > Autogrowth MAX is a one-time, invite-only lifetime license bought from the organization's credit balance, not a subscription tier. It is required to run any automation, workflow or Incubator program. Without a price set for that organization, the purchase is refused. > An automation is one of AutoGrowth's built-in definitions; a script is a graph the customer builds in the Script Builder. The Script Builder is locked platform-wide, so never present building a script as something a customer can do today. > An API key is a bare 64-character hex string with no prefix. It is shown once, at creation, is sent as `Authorization: Bearer `, and can never be read back. > An API key sees only the key owner's own accounts, content, collections, prompts, scripts and executions. Devices and tags are organization-scoped, and a non-owner sees only the devices assigned to them or carrying one of their tags. The automation catalog is global. > There is no pagination. List endpoints return the whole set; the only limiting parameter anywhere is `limit` on `GET /v1/executions`, which defaults to 50 and has no offset to page with. > Remote control and the live screen are dashboard-only, over WebSocket and MJPEG. Neither is part of the public API. > The MCP server is hosted at https://mcp.autogrowth.farm and authenticates with OAuth. It is not an npm package and there is nothing to install locally. Its tools inherit exactly the scope of the API key behind them. > Android support is partial and GrapheneOS-only: those phones appear in the fleet and can be watched and remote-controlled, but they cannot run scripts or automations. > Never document Hi Katie or any persona feature. When a page and the code disagree, the code wins — check a claim against the source before repeating it. # Team and roles > Invite people to your organization and control what each of them can see and change. 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 ## 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: AutoGrowth makes the user there and then, with a generated temporary password, and puts them in the **Member** role. 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. 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. | Group | Permissions | | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Accounts** | View accounts · Manage accounts | | **Content** | View library · Manage library · View AI prompts · Manage AI prompts · View schedule · Manage schedule | | **Scripts** | View scripts · Create/edit/run scripts | | **Logs** | View logs | | **Devices** | Assign devices to users · Manage tags · Remote control devices | | **Admin** | Manage API keys · Manage integrations · Manage restricted apps · Manage billing | | **Organization** | Manage members · Manage roles | | **Jailbroken Devices** | View jailbroken devices · Manage containers, proxies, VPN & backups · Destructive actions (restore, delete, clear app data) · Provision & revoke licenses | 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](/guides/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](/guides/getting-help). ## What to read next Assign phones and tags, which is what member visibility runs on. Credits, slots and licences — and who is allowed to spend them.