Getting Started
Manage customer organizations
Create and administer every customer organization inside one SaaS app.
Open a SaaS app and choose Organizations to manage the customer accounts hosted by that product. The directory is limited to the selected app and shows each organization’s owner, status, user count, DataRole count, and Location count.
Create an organization
Choose New organization and enter the customer identity plus its initial owner. API-driven signup can include up to five initial DataRoles and five initial Locations in the same submission; the console provides the first role/location fields and supports adding the rest after creation. The account, owner, owner authority, roles, and locations are committed together; an invalid part leaves no half-created organization.
A builder-owned marketing site can create the same organization through the Developer API after its own signup service verifies the owner. The browser posts to the builder's backend; that backend keeps the app credential private and calls POST /v1/apps/{saasAppId}/accounts. API-created organizations appear in this directory without importing or synchronizing them, and the new owner can use the same account administration workspace inside the SaaS. Follow How customer organizations can signup from your website for the complete implementation.
Manage the account
- Rename the organization, change its primary email, or deactivate/reactivate it with revision protection.
- Add external tenant users and edit or deactivate existing users.
- Create, edit, and safely deactivate DataRoles and Locations.
- Assign each user the allowed DataRoles and either all Locations or a selected Location set.
Before adding ordinary users, enable at least one shared User Type for tenant assignment in the app’s presentation policy. The account-local owner type is reserved for the initial owner and cannot be assigned to ordinary users.
Organization IDs select a record; they do not prove authority. The server verifies the signed-in builder, selected app ownership, registered database route, SaaS identity, and AppAccount scope on every request. Browsers never receive database names or connection strings.
Deactivate accounts, users, DataRoles, or Locations when history must be retained. Hard deletion is intentionally not the normal administrative lifecycle.
Capability review: 2026-09-14. For exact current technical availability, use the generated API Map and first-class module inventory.