Workspace

Where an organization’s structure lives: who’s on the team, how workspaces and environments are organized, each environment’s API key, and a log of what happened.

📷 Screenshot: the Workspace page on the Environments & API Keys tab with a workspace expanded — pending Task 2.

What you see

Up to three tabs, gated by plan and by whether an org is selected.

Team

Members and pending invitations for the current org — a role badge per member (owner / admin / member / viewer), plus invite and remove actions. This tab only appears on plans with team management — it’s the destination the old /settings/team URL redirects into.

Environments & API Keys

A drill-down: Workspaces group environments, and each environment holds exactly one API key. Renaming an environment only changes its label; rotating a key issues a new one and gives the old key a 24-hour grace window before it stops working, unless you choose to expire it immediately (for a compromised key).

A Show Demo workspace in switcher toggle sits below the workspace list — it controls whether the read-only Demo workspace appears in your workspace switcher, not your own data.

Activity

The organization’s activity log, rendered inline on this tab.

How to use it

Select a workspace to see its environments, then rotate or rename a key from there.
Copy a rotated key immediately — it’s shown once.
Use “Expire old key now” only if the previous key was compromised; otherwise the 24h grace window avoids breaking an in-flight deploy.
Invite teammates and set their role from the Team tab, if your plan includes team management.

Before you have data

Team and workspace management require selecting an organization first — both the Team and Environments & API Keys tabs show a plain “Select an organization to manage {team members / workspaces}.” line instead of an empty table until one is selected.

Settings — your personal account: profile, security, danger zone.
Integrations — where alert channels like Slack and PagerDuty are configured.