Skip to content

Grids, orgs, and spaces

A grid is your organization’s home on CloudGrid. Every entity belongs to exactly one grid. A user can belong to several grids, and switches between them with grid use.

Terminal window
grid whoami # see your identity and grid memberships
grid use my-company # set the active grid for subsequent commands
grid get grids # list the grids you belong to

The active grid is where new entities land unless you override it with the --grid <slug> flag on a single command.

You become the admin of any grid you create:

Terminal window
grid create grid my-new-grid

A space is a group within a grid that shapes discovery — think of it like a channel. Members see entities scoped to their spaces. Spaces do not change who can access an entity (that is visibility); they shape what shows up in discovery.

Terminal window
grid space list # list spaces in the active grid
grid space create dev-tools # create one (admin only)
grid space show dev-tools # details
grid space invite dev-tools alice@example.com

Spaces are membership groupings — create one, then invite members and manage them with the grid space subcommands above. See the Spaces CLI reference for the full command set.

Admins manage grid membership:

Terminal window
grid admin invite alice@example.com --role developer
grid admin members
grid admin member-role alice@example.com admin
grid admin remove bob@example.com

Roles govern what a member can do in the grid (creating and deploying entities, managing members and settings). See the Admin CLI reference.

When a command targets an entity, the CLI resolves it in this order:

  1. No argument, inside a linked directory — reads .cloudgrid/link.json.
  2. A UUID — globally unique, unambiguous.
  3. org/slug — globally addressable.
  4. A bare slug — searched across all your grid memberships. If the slug matches entities in more than one grid, the CLI errors and asks you to disambiguate with org/slug.

The --grid <slug> flag scopes resolution to one grid.