Every push, preview, and token belongs to a project. A project is your collaboration unit: a set of members with roles, working on the same plugin or service.Documentation Index
Fetch the complete documentation index at: https://docs.grounds.gg/llms.txt
Use this file to discover all available pages before exploring further.
Roles
There are three roles, with strictly nested permissions:| Role | Push | View pushes | Manage previews | Invite / remove members | Mint tokens |
|---|---|---|---|---|---|
viewer | — | ✓ | — | — | — |
editor | ✓ | ✓ | ✓ | — | — |
owner | ✓ | ✓ | ✓ | ✓ | ✓ |
owner on one project and a viewer on another.
A project must always have at least one owner. Trying to demote or remove the last owner returns a
409 last owner protection error from forge.Default project
When you sign up, a default project is created for you with you as the sole owner. You can create more from the portal or via API. CLI commands without a project flag use your default project. Pin a different one for a single command:Inviting members
There are two flows.Add by username
Owners can add a known account directly from the portal Members page. The user must have signed in at least once so we have a record of them.Invite link
For people who haven’t signed up yet, mint a one-time invite link:- Portal → Project → Members → Invite link.
- Pick the role (
editororviewer) and an expiry (default 7 days, max 30). - Send the URL. The recipient signs in with their Grounds Account and is automatically added to the project.
owner (only existing owners can promote).
Service-account tokens
For unattended use (CI, scripts, bots) projects can mint long-livedgnds_* API tokens scoped to a single project. See CI / service-account tokens.
