Organizations
Create, switch, configure, and safely remove Parix organizations.
An organization is the access and billing boundary for Parix databases. Membership, billing state, database lists, notifications, and audit events are resolved against the active organization in your session. The global API-key page has a current cross-organization listing limitation described under API key security.
Create an organization
Open Settings → Organizations, select New, and enter an organization slug.
The current creation flow requires a slug that:
- contains lowercase letters, numbers, and dashes only
- is not a reserved Parix route name
- is not already used by another organization
The slug is used as both the initial organization name and its URL segment. A successful create immediately makes the new organization active. The authentication service currently allows a user to belong to at most five organizations.
Switch organizations
Open Settings → Organizations to see every organization you belong to. For another organization, select either:
- Databases to activate it and open its database list
- Settings to activate it and open its General page
Parix changes the active organization before navigating. Organization-scoped routes validate that their URL slug matches that active organization, so do not keep using an old organization tab after switching without checking the organization name in the shell.
API key management is under global settings. Switch to the intended organization before generating a key, but do not assume every existing row belongs to the active organization: the current loader can include keys from other organizations you belong to. Follow the safeguards in API key security before rotating or deleting a row.
General settings
Open /<organization-slug>/settings. Owners and administrators can edit:
| Setting | Current behavior |
|---|---|
| Organization name | Lowercase letters, numbers, and dashes only. Changing it does not change the organization URL slug. |
| Billing email | Required when saving; billing notices and invoices use this address. |
| Backup retention | An integer from 1 to 365 days. The default is 7 days. |
Members can open the page but the organization fields are read-only. The same page links to each database dashboard and database-specific settings.
Backup retention controls cleanup of completed backup artifacts. It does not make an unsupported backup or restore path available; see Backup and restore.
Roles at a glance
The shipped organization roles are owner, admin, and member.
| Role | Shipped organization behavior |
|---|---|
| Owner | Initial ownership role. Can delete the organization and manage settings, billing, members, invitations, API keys, backups, and database control-plane changes. |
| Admin | Can manage the same current settings and database operations except organization deletion. Can invite either administrators or members. |
| Member | Can use member-visible organization and database surfaces, but cannot perform operations guarded for owners and administrators. Can leave the organization. |
The dashboard does not currently expose custom roles, a role editor, or an ownership-transfer flow. See Members and invitations for the exact member lifecycle.
Delete an organization safely
Only an owner can complete organization deletion. The route can display the destructive control to an administrator, but the underlying organization authorization rejects the delete. The dialog requires the exact current organization name and describes the operation as permanent and irreversible.
Before deleting:
- Delete each managed database from its database settings.
- Wait for each decommission workflow to finish.
- Review billing, members, API keys, and recent audit events.
- Return to General settings, select Delete organization, and type the organization name.
The organization action itself does not queue database decommission workflows. Do not use it as a shortcut for removing provider resources.
After deletion, Parix activates the first remaining organization. If none remain, it returns you to onboarding.