Enterprise Sub-workspaces

An Enterprise workspace can run sub-workspaces — separate workspaces for your clients, business units or engagements, owned by you and billed under one agreement. Each is a real workspace with its own members, data, agents and audit trail, and nothing leaks sideways between them.

This is the right model when you are running the environments. If instead you're collaborating with an organization that already has its own Portablemind workspace, see Workspace Sharing; if you're bringing in an individual contractor or client, see Guest Users.

Who can have them

• Sub-workspaces are an Enterprise feature.
• Only a workspace that sits directly with us can have them — a sub-workspace never has sub-workspaces of its own.
• A sub-workspace is always on one of the standard plans (Free through Business), never Enterprise itself.
• Your workspace needs an active billing agreement with us before you can create any.

You manage them from the Tenants page, using New Tenant.

The billing agreement

Sub-workspaces are covered by an agreement between you and us rather than a self-service setting, so the terms match your contract. The agreement names two things:

Term	What it controls
Allowance	How many sub-workspaces your agreement covers
Contract tier	The highest plan you can place a covered sub-workspace on. You can always choose a lower one

While an agreement is in force, the Tenants page shows how many of your allowance are in use. Reach the allowance and New Tenant is disabled, with a note telling you to contact sales or support to add more. On Enterprise without an agreement yet, the page says so and offers a way to get in touch.

Creating a covered sub-workspace needs no card — it's billed under your agreement. Existing sub-workspaces are brought under a new agreement automatically, oldest first, until the allowance is full. Sub-workspaces that already pay for themselves never use up your allowance.

Tip: trying to put a sub-workspace on a plan above your contract tier is refused with a message saying so. Choose a lower plan, or talk to us about changing the tier.

Billing, and what your customers see

You're billed by count, not by people: a standard agreement includes the first few sub-workspaces, then charges per additional one, with the rate dropping at volume. It arrives as a single line on your existing subscription and is prorated when the count changes. Negotiated agreements can use different bands — your agreement is what bills.

How you charge your own customers is entirely up to you and happens outside Portablemind. A sub-workspace you cover deliberately sees no platform price on its billing page — just a note that billing is covered by your agreement — and it has no plan-change or payment buttons, because you control its plan.

Everything else about a sub-workspace is normal: it has its own plan limits, its own fair-use guardrails and its own AI tokens, exactly as described in Plans, Limits & Fair Use.

Sharing agents and models downward

Agent templates

Train an agent once in the parent workspace — instructions, persona, memories, runbooks, skills — and publish it as a versioned template your sub-workspaces can install. Find it under AI Studio → Agents & Skills → Agent Templates, and publish from an agent's menu with Save as template.

• You choose who gets it: private, all sub-workspaces, or selected ones.
• Installing creates the sub-workspace's own copy. It's theirs from that moment on.
• Installation asks for consent and lists what the template brings: tools, resources, code, permissions, schedules.
• Anything that looks like a credential is stripped when a template is saved, and listed so the installer knows what to configure.
• A new version is opt-in — or automatic, if that workspace's admin turns it on. Either way, an upgrade keeps what the installed agent has learned and only replaces what the template provided.

See Building AI Agents for what goes into an agent in the first place.

Shared models

You can share an AI model you've configured down to your sub-workspaces, so their work runs on your provider account:

• Sub-workspaces never see your API key.
• You can set an optional monthly spend cap per sub-workspace.
• Withdraw the share and those workspaces simply move back to their own model.

Setting Up AI Models covers configuring the models themselves.

If you stop covering a sub-workspace

This happens when you leave Enterprise, end your agreement, or lower your allowance below the number of sub-workspaces you have. Nobody loses their workspace or their data.

A sub-workspace that already pays for itself simply becomes independent straight away, and its admins are told.

A sub-workspace that was relying on you gets a 14-day grace period:

1. Everything keeps working, and the grace period is free — you stop being billed for it immediately. A banner tells that workspace's admins the date they need to set up billing by, and they get an email when the grace begins.
2. One reminder follows, a few days before the deadline.
3. If the deadline passes, the workspace enters billing-only mode: it's locked except for billing, and its agents are paused. Nothing is deleted.
4. Taking it over — an admin of that workspace chooses a plan and supplies their own card. Access returns immediately and the paused agents resume. We never reuse your card for this.

Change your mind during the grace period — return to Enterprise, or reactivate the agreement — and the whole thing is cancelled automatically, with nothing lost.

Tip: lowering your allowance starts this process for the sub-workspaces past the new number, so check the coverage figures on the Tenants page before saving.