Organizations

An organization is a tenant: one isolated catalog with its own products, attributes, channels, members, API keys, connectors and audit log. Nothing is shared between organizations, and the separation is enforced in the database, not just in the app. One person can belong to several organizations, for example an agency running a catalog per client.

In the admin

The organization switcher sits at the bottom of the sidebar under Organization.

1. Click the current organization’s name to open the list of organizations you belong to. Each entry shows its slug.
2. Click another organization to switch. The admin reloads into that organization’s Products.
3. To add one, click Create organization at the bottom of the list.
4. Enter a Name. The Slug fills itself from the name; edit it if you like (lowercase letters, numbers and hyphens).
5. Click Create organization. You are added as its first member and land in its empty catalog.

To rename an organization or change its slug, use System → Settings. Deleting one is also there, under Danger zone. See Organization settings.

With the API

Method	Path	What it does
GET	/v1/me/orgs	Organizations the signed-in user belongs to
POST	/v1/organizations	Create an organization (name, slug, optional settings)
GET	/v1/organizations/me	The current organization, its settings and optional-feature state
PATCH	/v1/organizations/me	Update name, slug or settings
DELETE	/v1/organizations/{id}	Delete the current organization; body { "confirm": "<slug>" }

curl https://api.minipim.com/v1/organizations/me \
  -H 'Authorization: Bearer pim_…'

An API key always acts in the organization that issued it. To work in several organizations from a script, issue one key per organization.

Rules and limits

• Slugs are globally unique and must match ^[a-z0-9-]+$.
• A new organization starts empty: no products, attributes, channels, locales or connectors.
• PATCH /v1/organizations/me merges settings into what is stored rather than replacing it.
• Deleting an organization first exports its data to storage, then permanently deletes everything in it: products, media, attributes, channels, connectors, members, API keys and audit history. The response includes the export’s storage key and per-table counts.
• Deletion requires confirm to equal the organization’s slug, and can only target the organization you are currently in.
• Deletion never calls connected platforms and sends no per-entity webhooks. Your BigCommerce or Shopify store is not touched, but anything reading from minipim loses its source.
• Self-hosted deployments started with PIM_TENANT_MODE=single run exactly one organization. Creating another fails, and the sidebar shows a fixed Tenant label instead of the switcher.
• Creating, updating and deleting an organization emits organization.created, organization.updated and organization.deleted.

People are added per organization; see Members and invitations. Each organization’s changes are recorded in its own audit log.