Workspaces and projects

When to use one workspace vs many

A workspace is an isolation boundary: separate graphs, separate retrieval indexes, separate audit ledgers. Most companies should start with a single workspace because cross-departmental search is the highest-leverage outcome Mnemos enables.

Adopt multiple workspaces only when one of the following is true:

• Regulatory isolation — a subsidiary must not see another's data even with restrictive roles.
• M&A staging — the buyer and seller are merging knowledge but contractual exposure is still being negotiated.
• Customer-facing instances — you operate Mnemos on behalf of clients and each client's data must be fully partitioned.

Creating a workspace

Owners can create additional workspaces from the organization admin surface. New workspaces inherit the organization's SSO and SCIM connection by default; you can opt a workspace out of either with a settings toggle.

curl -X POST https://api.mnemos.ai/v1/workspaces \
  -H "Authorization: Bearer $MNEMOS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Acme — Revenue Operations",
    "slug": "acme-revops",
    "data_residency": "us-east",
    "inherit_sso": true
  }'

Projects

Projects partition the work inside a workspace without splitting the graph. They are the natural unit for retention policy, access override, and per-team reporting. Common patterns:

• By department: Sales, Finance, Engineering, HR.
• By function: Onboarding, Compliance, Vendor Management.
• By initiative: Q3 Launch, EU expansion, ERP migration.

Retention and residency

Each workspace has a data-residency region (US-East, EU-West, AP-Sydney) selected at creation. Region is immutable; if you need to move data, the platform exports and re-imports under a new workspace rather than mutating in place. Retention policies are per-project and per-artifact type, default 7 years for SOPs and 2 years for raw transcripts.