Envelope

Organisation settings

Your workspace belongs to your organisation. This guide covers everything in org settings — inviting your team, managing shared credentials, controlling who can do what, and keeping an eye on activity.

Access your workspace settings by clicking your workspace name at the top of the left sidebar, then clicking Full workspace settings — or go directly to /orgs/{your-slug}.

Overview

The workspace overview shows a snapshot of your org:

  • Number of members and their roles
  • Teams owned by the org
  • Billing and payout status

From here you can jump to any section, or use the left sidebar to navigate directly.

Templates

The Templates section lists every AI team owned by this org — draft, published, and archived. Click any team to open it. Ownership is set when a team is created; transferring ownership to an org means all members can manage it and the org billing applies.

Members and roles

Invite anyone to your workspace from the Members section. Enter their email address, choose a role, and send the invite. They'll receive an email with a link to join.

Roles

| What they can do | Member | Admin | Owner | |---|:---:|:---:|:---:| | View the workspace and run history | ✓ | ✓ | ✓ | | Run and manage AI teams | ✓ | ✓ | ✓ | | View the audit log | ✓ | ✓ | ✓ | | View analytics | ✓ | ✓ | ✓ | | Invite new members | — | ✓ | ✓ | | Approve or reject governance requests | — | ✓ | ✓ | | View tools and connection status | ✓ | ✓ | ✓ | | Manage tools and credentials | — | ✓ | ✓ | | Manage billing | — | — | ✓ | | Delete the org | — | — | ✓ |

Only the owner can manage billing, transfer ownership, or delete the workspace. Admins can handle everything else — inviting people, managing tools and credentials, and approving installs.

Removing a member

Members can be removed at any time from the Members section. Removing a member revokes their access immediately — any runs they triggered continue to completion but they can no longer log in or take action.

Tools and credentials

The Tools panel (in your workspace sidebar) is a shared encrypted store for credentials your AI teams need to run — API keys, tokens, connection strings. Instead of every team member managing their own credentials, admins register tools and store credentials once, and all teams in the workspace can use them.

Members can see which tools are connected and which are missing credentials. Adding, editing, or removing tools and credentials requires admin or owner access.

Adding a credential

  1. Open the Tools panel from the workspace sidebar (plug icon)
  2. Find the tool you want to connect, or click + Add tool to register a new one
  3. Click + Add key on the tool row, enter the secret name (e.g. OPENAI_API_KEY) and value, and save

Secret values are encrypted at rest. Once saved, the value cannot be read back — only deleted and replaced. This is intentional: the vault is write-once for security.

Using vault secrets

Any AI team running in your workspace can reference vault secrets by name. When a team runs, Envelope injects the value automatically — your team members never need to see or copy the actual credential.

Typical use: Store your OpenAI API key once. Every team member who runs a team that uses OpenAI draws from the shared key, and you rotate it in one place when it expires.

Pro feature — Vault requires a Pro or Scale workspace plan.

Approvals & governance

Governance gives admins oversight of new AI team deployments before they go live. When enabled, any new team a member wants to run goes into a pending state and requires explicit approval.

Enabling governance

Go to the Governance section in the sidebar and toggle governance on. Once enabled, all new deployments require approval.

The approval flow

  1. A member creates a new AI team in their workspace room thread
  2. Before it can run, a request is submitted for review
  3. Admins and owners receive a notification
  4. An admin reviews the request and approves or rejects it (with an optional note)
  5. The member is notified of the decision
  6. Approved teams go live; rejected ones stay inactive

Every decision is recorded in the audit log. Governance can be turned off at any time — existing approved teams continue running.

Pro feature — Governance requires a Pro or Scale workspace plan.

Audit log

The audit log is a permanent, uneditable record of every significant action taken in your workspace:

Members

  • Invitation sent, cancelled, or accepted
  • Member joined, role changed, or removed
  • Ownership transferred

Teams

  • Team created, published, unpublished, archived, or deleted

Credentials & access

  • Vault secret created, updated, or deleted
  • API key created or revoked

Governance & billing

  • Approval requested, approved, or rejected
  • Billing plan changed

The log is visible to owners and admins. It cannot be modified or deleted.

Pro feature — Audit log requires a Pro or Scale workspace plan.

Notifications

The Notifications section controls where org-level alerts are sent. Three delivery channels are available — enable as many as you need:

  • Email — sends alerts to your configured address. Reply to any notification email and your message is routed back to the agent — it runs and replies directly to your inbox. Enable or disable reply routing with the Allow email replies toggle.
  • Webhook — sends a notification to any URL you specify (useful for connecting to Zapier or other automation tools)
  • Discord — posts to a Discord channel via webhook URL

For each channel you enable, you can choose which events trigger a notification:

| Event | When it fires | |---|---| | Run completed | Any team run finishes successfully | | Run failed | A run ends in a failed state | | Security event | The security proxy blocks or flags a request | | Observability alert | A success-rate drop or token spike is detected |

All four events are on by default. Uncheck any you don't need. Only admins and owners can change notification settings.

Analytics

The analytics section shows aggregate activity across your workspace — run volumes, success and failure rates, and usage trends over time. Useful for understanding how actively your teams are being used and spotting any reliability issues.

Analytics are available on all plans. Free workspaces see up to 30 days of history; Pro and Scale workspaces have full history available.

API keys

Org-level API keys authenticate API calls on behalf of the organisation — not any individual member. They're useful for server-to-server integrations where a personal key would be tied to one person's account.

Create and delete org API keys from the API Keys section. Keys can be labelled to indicate what they're used for.

Workspace plans

| Plan | Price | Includes | |---|---|---| | Free | $0 | Members, invitations, basic settings | | Pro | $39/mo | Vault, governance, audit log, unlimited analytics history, 14-day trial | | Scale | $99/mo | Everything in Pro, higher run limits, priority support |

Upgrade or downgrade from the Billing section at any time. Downgrading from Pro disables the vault and governance features but does not delete stored data — reactivate by upgrading again.

Settings

The Settings section covers org identity and ownership.

Rename — Change the org's display name at any time. The slug (@your-slug) cannot be changed once set.

Transfer ownership — Pass ownership to any existing admin. You become a member after the transfer. Requires typing the org name to confirm.

Delete org — Permanently removes the org and all memberships. Templates revert to personal ownership. Requires typing the org name to confirm. Only available to the owner, and only when all active installs have been removed.

‹ All guidesDocs ›