Workspaces

A workspace is your team on Amp. It holds your members, the threads they create, the projects they work in, and one shared bill. It is also where you configure Amp once for everyone: plugins, skills, agents, secrets, MCP servers, and model routing set at the workspace level apply to every member.

Without a workspace, you use Amp on your own: your threads are private, your credits are yours, and your settings only affect you. A user belongs to at most one workspace.

Why Create a Workspace

Create a workspace when more than one person on your team uses Amp. You get:

• Shared threads. Threads are visible to the whole workspace by default, so you can read how a teammate solved a problem, search each other’s threads, and point the agent at them as context. Tag a teammate with @ in a thread to pull them in and pair on the live orb, and agents in the same workspace can message each other.
• Shared projects. A workspace project is visible to every member, and each member’s orbs get the project’s setup scripts and secrets. See Projects.
• One bill. Workspace credits are pooled and shared. Admins buy credits, manage the payment method, and can manage members’ subscriptions.
• Configure Amp once. Workspace plugins, skills, agents, secrets, MCP servers, and model provider keys load for every member without each person setting them up.
• Policies. Admins decide whether threads can be shared outside the workspace, whether members can use their own model provider keys, whether passkeys are required, and more.

Create a Workspace

Open Workspace Settings and fill in Create a Workspace. You choose a display name and a short name. The short name becomes the workspace URL, ampcode.com/workspaces/<short-name>. If you already have threads, Amp asks whether to share them with the new workspace.

You become the workspace’s first admin. Your personal paid credits move into the workspace pool.

To join an existing workspace instead, ask a member to invite you. The invitation shows up on the same page and in your email. If your company uses SSO, sign in with your work email and Amp adds you to the workspace automatically.

Invite Members

Open the Members section of workspace settings. Admins can invite people by email, create a shareable invite link with an expiry and a use limit, and change members’ roles. Admins can also let regular members send email invitations.

There are two roles:

• Member: uses everything the workspace provides and sees shared threads and projects.
• Admin: everything a member can do, plus managing members, billing, settings, and policies. Admins can also see members’ private threads.

Enterprise workspaces can give members narrower roles such as Billing Manager, Auditor, and Group Manager, restrict joining to a verified email domain, and provision members with SSO and directory sync.

Personal vs. Workspace

Most things you can configure in Amp exist at two levels. The Personal Settings and Workspace Settings tabs at the top of the settings page switch between them. The rule of thumb:

• Things you add (plugins, skills, agents, secrets, MCP servers, model provider keys, domains) exist at both levels and combine. Everyone gets the workspace’s, and you get your own on top. When names collide, your personal one wins.
• Things admins set as policy (sharing, security, what members may use) apply to everyone and override the personal setting.
• Things that are owned (threads, projects, credits) have one owner, either you or the workspace.

Workspace Settings

Admins manage the workspace from Workspace Settings. Members can open the same page and see the sections that apply to them.

• Workspace: name and icon, the shared balance, subscriptions, and high-level policies such as whether members can use orbs or share threads outside the workspace.
• Members: invitations, invite links, roles, and removal.
• Usage: credit usage across the workspace, by member and over time.
• Billing: payment method, invoices, and credit purchases.
• Model Routing: the workspace’s model provider keys and whether members may use their own.
• Project Defaults: whether members can create workspace projects, and defaults for new projects such as orb size and ship behavior.
• MCP: MCP servers shared with every member.
• Domains: custom domains for portals and the workspace default.
• Secrets & Env Vars: values available in every member’s orbs.
• Plugins, Skills, Agents: the workspace repositories that load for every member. See Global Plugins & Skills.
• Integrations: Slack, GitHub, and other connectors, and whether members may use them.
• Advanced: install instructions shown to members, passkey requirements, data retention, and other policies.

Billing

A workspace pays for Amp in two ways, and you can mix them: pooled credits that any member’s usage draws from, and subscriptions for individual members that the workspace pays for. A workspace does not need subscriptions; members can run entirely on pooled credits at standard usage rates.

Workspace credits are pooled and shared by all workspace members. Admins (or Enterprise Billing Managers) purchase credits for the pool and manage the payment method.

• When you create or join a workspace, your personal paid credits move to the workspace pool. They are not returned if you leave or are removed. Your personal free credits are used before the workspace pool.
• Purchased credits expire twelve months after purchase.
• When an admin deletes a workspace, the remaining paid credits move to that admin’s personal balance. Remaining free credits are lost.
• Subscriptions stay assigned to individual members. Joining a workspace does not change or refund the current paid period; the next renewal or upgrade uses the workspace’s billing. If the workspace paid for the current period and you leave, it will not renew unless you resume with personal billing. Any remaining free subscription months stay unused until you resume. If you paid for the current period yourself, renewal continues with personal billing.
• When an admin deletes a workspace, subscriptions paid by that workspace remain active until their current periods end, but their renewals stop. Subscriptions paid personally or by another workspace continue.
• Subscription charges use the first source that covers the full amount: your eligible personal free credits, workspace free credits, workspace paid credits, then the workspace’s payment method.
• By default, members can start, change, cancel, and resume their own subscriptions, paid from workspace credits or the workspace’s payment method. Admins and Billing Managers can turn this off and can manage any member’s subscription either way.
• Admins start or change a member’s subscription with Choose Plan next to that member in the Members list. There is no way yet to subscribe every member automatically.

Enterprise

Enterprise adds controls and support for larger organizations. Enterprise usage costs 50% more than individual and team usage. To upgrade, open your workspace and click Plan; see Enterprise pricing for details. Enterprise adds:

• SSO and directory sync for provisioning members and groups, and a required email domain
• Narrower roles: Auditor, Billing Manager, Group Manager, Usage Viewer, Global Plugin Manager, and Model Provider Key Manager
• Thread visibility controls and groups for sharing threads with part of the workspace
• Entitlements for per-user usage quotas
• An MCP registry allowlist
• Controls to stop members from using personal model provider keys and personal subscriptions
• Minimal data retention