---
title: "Customer Provisioning"
description: "Create customer workspaces, set seat caps, and manage the customer lifecycle from the partner portal."
canonical_url: "https://docs.basicmemory.com/partners/customer-provisioning"
---
# Customer Provisioning

> Create customer workspaces, set seat caps, and manage the customer lifecycle from the partner portal.

The **Customers** page in the partner portal is where you create and operate customer organizations. Each customer gets a **dedicated, isolated workspace** — its own database and file storage, physically separated from every other customer and tenant. There is no shared data layer between your customers.

---

## Add a customer

Click **Add customer** on the Customers page. Provisioning creates the customer's organization and workspace automatically — no infrastructure work on your side.

The customer list shows each customer's **status, workspace, seat cap, JIT state, and billing label**. SSO state lives on the customer's detail page.

---

## Seat caps

Each customer can have an optional **seat cap** — a per-customer limit on assigned seats:

- Leave the cap blank for no per-customer limit; the customer is then bounded only by your account-wide [seat commitment](https://docs.basicmemory.com/partners/billing).
- If an assignment would exceed the customer's cap, it's denied until you raise the cap.
- The customer's detail page shows assigned seats, cap, available seats, and utilization.

---

## Customer lifecycle

From a customer's detail page:

- **Suspend** — pauses access for all of the customer's users. Their data is kept and seats stay assigned.
- **Reactivate** — restores access for the customer's users.
- **Archive** — the offboarding path: access ends and all open seats are closed. You confirm by typing the customer's slug.

<note icon="i-lucide-eye">

**Transparency for your customers.** Administrative actions your staff take on a customer — lifecycle changes (create, suspend, reactivate, archive) and SSO changes — appear in the customer's own audit trail, labeled as performed by their MSP. Billing-metadata updates stay internal to your portal.

</note>

---

## Next Steps

<card-group>
<card icon="i-lucide-key-round" title="Customer SSO" to="https://docs.basicmemory.com/partners/customer-sso">

Connect the customer's identity provider before their users sign in.

</card>

<card icon="i-lucide-receipt" title="Billing" to="https://docs.basicmemory.com/partners/billing">

How customer seats turn into seat-days on your invoice.

</card>
</card-group>


## Sitemap

See the full [sitemap](https://docs.basicmemory.com/sitemap.md) for all pages.
