Instances Manager
Customer environments for product partners building on AIOS.
How it fits together.
An instance groups product configuration for an environment built on AIOS. Its display brings together associated organizations, onboardings, emails, calculation and usage. An organization is a specific business or work context within that structure. Switching organizations in the account menu is therefore different from configuring an instance.
Instance editing offers General, Onboarding, Configuration and Usage limits. Configuration includes Permissions and Integrations. Further settings appear according to access and instance type. System Manager remains the area for infrastructure and runtimes; Instances Manager helps product partners manage their customer environments.
Step by step in AIOS
Open Account menu → Instances Manager with an enabled partner account.
This entry point is for enabled product partners. The account must offer instance management; ordinary organization administration alone is insufficient.
Open an instance from the collection. It is a separate environment and differs from ordinary organization switching.
An instance groups product configuration and associated customer organizations. It is not synonymous with a dedicated server and is configured separately from organization switching.
Inspect available organization, usage and activity information.
The display contains Organizations, Onboardings, Emails, Calculation and Usage. Use these sections to understand customer context and existing configuration before making changes.
With the appropriate permissions, edit General, Onboarding, Configuration and Usage limits. Align branding and capabilities with the product.
General contains fields including name, URL identifier and software name. Configuration manages Permissions and Integrations; Onboarding and Usage limits have their own sections.
AIOSAn example for your work.
Product name: Service Workspace
Audience: Consulting teams
Customer organizations: A separate organization context for each customer
First workflow: Project brief → tasks → reviewed handover
Required integrations: Select together before enablement
Onboarding: Agree contact person and introductory text
Usage limits: Set according to the agreed operating model
Operations: Identify the person responsible for infrastructure and runtimesUse this brief to plan with GROON and add the arrangements for your customer environment.
Product environment, customer context and operations
| Area | Meaning in daily work |
|---|---|
| Instance | Product configuration and associated organizations. |
| Organization | A specific business and work context. |
| Instance configuration | Permissions, integrations, onboarding and usage limits. |
| Instances Manager | Management for enabled product partners. |
| System Manager | Infrastructure and runtime operations for authorized operators. |
If something does not work.
- Instances Manager is missing: Your account requires instance-management permission; organization rights alone are insufficient.
- A setting is not editable: Check instance type and your management access. Operator-related settings have additional access restrictions.
- You are investigating a runtime error: Use System Manager with operator access, not ordinary organization switching.