Learn how data ownership, access, authentication, and Credits differ between personal and enterprise spaces in Qoder Cloud Agents.
The Qoder Cloud Agents console provides both personal and enterprise spaces. Their data, authentication methods, and billing ownership are independent. Before creating or configuring resources, confirm which space you are using.
Personal and enterprise spaces coexist. Agents, Environments, Files, and other resources in a personal space do not automatically appear in an enterprise space or migrate when you join an organization.
After signing in to the Cloud Agents console, use the space selector in the lower-left corner to view and switch the current space:
An enterprise space must be bound to an available SA before it can authenticate and use enterprise execution capabilities. Qoder Cloud Agents does not create or manage SAs. Enablement, creation, and credential management are performed in the Qoder management console.
If you can access an enterprise space but do not see an SA available for binding on the Enterprise credentials page, the current Qoder organization usually has not enabled Service Accounts or does not have an available SA. Complete the following steps:
Enterprise spaces are currently available only to administrators and configuration administrators of Teams or Enterprise organizations. Regular members can only access their personal space.
Access to an enterprise space and Service Account enablement are separate requirements. Confirm that Service Accounts are enabled for the current organization and that an available SA has been created in the Qoder management console.
No. Data in the two spaces is isolated, and personal resources are not automatically migrated to the enterprise space.
After confirming the space and binding an enterprise SA, continue with Quickstart to create an Agent, Environment, and Session.
How the spaces differ
| Comparison | Personal space | Enterprise space |
|---|---|---|
| Eligible users | All Qoder users | Administrators and configuration administrators of Qoder Teams or Enterprise organizations |
| Data ownership | The current individual user | The current Qoder organization |
| Collaboration | Only the current user can configure and use resources | Administrators and configuration administrators in the same organization can view and configure resources together |
| Authentication | A personal access token (PAT) | A Service Account (SA) bound to the enterprise space |
| Credits deduction | Personal Credits | The enterprise SA's dedicated Credits pool |
Access an enterprise space
- Users who have not joined a Teams or Enterprise organization can only use a personal space.
- Regular members of a Teams or Enterprise organization can only use a personal space.
- Administrators and configuration administrators of a Teams or Enterprise organization can switch between their personal space and the organization's enterprise space.
Switch spaces
After signing in to the Cloud Agents console, use the space selector in the lower-left corner to view and switch the current space:
- Select My personal space to use personal resources, a PAT, and personal Credits.
- Select the Enterprise space labeled with the enterprise name to manage enterprise resources together and authenticate with the bound SA.
Bind an SA before using an enterprise space
An enterprise space must be bound to an available SA before it can authenticate and use enterprise execution capabilities. Qoder Cloud Agents does not create or manage SAs. Enablement, creation, and credential management are performed in the Qoder management console.
If you can access an enterprise space but do not see an SA available for binding on the Enterprise credentials page, the current Qoder organization usually has not enabled Service Accounts or does not have an available SA. Complete the following steps:
- Follow the Qoder Service Account Dedicated Credits guide to enable Service Accounts for the current organization.
- Create an available SA in the Qoder management console and complete the required billing configuration.
- Return to the enterprise space in the Cloud Agents console, open Enterprise credentials, and bind the SA.