Table of Contents

Search

  1. Preface
  2. Introducing Administrator
  3. Organizations
  4. Licenses
  5. Ecosystem single sign-on
  6. SAML single sign-on
  7. Metering
  8. Source control and service upgrade settings
  9. Users and user groups
  10. User roles
  11. Permissions
  12. Runtime environments
  13. Serverless runtime environments
  14. Secure Agent services
  15. Secure Agent installation
  16. Schedules
  17. Bundle management
  18. Event monitoring
  19. File transfer
  20. Troubleshooting

Administrator

Administrator

Disabling or enabling a sub-organization

Disabling or enabling a sub-organization

If you are the administrator for a parent organization, you can disable or enable a sub-organization.
When you create a sub-organization, the sub-organization is enabled by default. You might want to disable a sub-organization if you have a separate license agreement with the sub-organization and the license agreement expires. You can re-enable the sub-organization after you disable it.
You can disable or enable a sub-organization even if the sub-organization administrator blocks parent organization access to the sub-organization.
You can perform the following actions:
Disable a sub-organization
When you disable a sub-organization, the organization exists, but sub-organization users cannot log in to the sub-organization or access it through the REST API. Scheduled jobs in the sub-organization do not run.
Enable a sub-organization
When you enable a sub-organization, sub-organization users can log in to the sub-organization and access assets and perform tasks based on their user roles. Users with the appropriate privileges can access the sub-organization through the REST API. Scheduled jobs resume according to their schedules.
Disable or enable a sub-organization on the
Sub-Organizations
tab of the
Organizations
page. In the
Actions
menu for the sub-organization, select
Disable
or
Enable
.


Updated October 29, 2020