Teams & orgs

Run Anvil for an organisation — workspaces, roles, invitations, seat limits, and encrypted team chat.

Anvil isn't only a tool for one person. An organisation gets workspaces, roles, invitations, seat management, and end-to-end encrypted chat — so a team can run, publish, and collaborate together.

Workspaces

A workspace (org) is how a team shares Anvil. Create one, invite people, and give each a role. The workspace owns its packages, its artifacts, and its shared settings.

[!NOTE] Workspaces live in your command centre — create one, or open a workspace you've been invited to, from the Workspaces surface.

Roles & members

Every member has a role that sets what they can do — from viewing to publishing to full admin. From the workspace admin you can:

Invite people by email, and re-send or revoke invitations.
Re-role a member as their responsibilities change.
Suspend or remove a member.
Transfer ownership or leave the workspace.

Roles gate real capabilities (for example, publishing a package or writing to shared config), not just labels.

Seats

A workspace has a seat limit (or unlimited). The admin sees seats in use against the limit, so adding a member is a deliberate, visible act rather than a surprise.

Encrypted team chat

Each workspace carries end-to-end encrypted chat, so the conversation about the work lives beside the work — and stays private to the team.

[!NOTE] Team chat is end-to-end encrypted. The hub routes messages but cannot read them.

The team board

The workspace's live board shows what every bot and member is doing right now — a shared view of the team's activity, capped and filtered so it stays readable.