Tenant admin hub

Goal

Configure the company tenant: who can sign in, which modules are on, and tenant-wide settings.

Who it is for

Owner and Admin memberships (member.manage / member.admin, tenant.manage, integration.*).

Preconditions

• You signed in with a membership that has admin keys.
• You understand tenant settings (currency, locales, timezone, costing, out-of-stock policy) live on the tenant — not in global env.

Start here

1. Onboarding
2. Users and roles — Members / Members setup (Create role wizard, matrix, Advanced catalogs)
3. Modules — enable optional modules (module:{key} gates APIs with 422 when off)
4. Tenant settings
5. Localization — enabled_locales, default locale
6. Integrations — webhooks/connections (integration.view)

Result

Users get the right roles; modules and settings match how the business operates.

Hard stops

Editing roles needs member.admin; disabled module → staff SPA redirects / API 422; never pass tenant_id from the client — tenancy comes from the token.

Related

• Permissions model
• Translations on forms
• Troubleshoot permissions