Skip to main content
Version: 2024.1

Associating Automation to Domains

CloudShell supports multi-tenancy for CloudShell components (scripts, resources, services, and Apps), allowing users in other domains to also use them. However, in the Global domain, you can manage all components regardless of their association to any particular domain.

Scripts in multiple domains​

When you add a script, it is associated to the domain you are currently in.

  • To expose a script to all domains, add the script to the Global domain.
  • If you added a script it to a blueprint or resource that has additional domains, the script will be accessible in those domains as well.

Resources in multiple domains​

To enable users of a specific domain to access and use a resource, you must associate that resource to the domain.

  • If you add a resource to a blueprint that is associated with multiple domains, the resource will be accessible in those domains as well.
  • You can add a resource directly to an additional domain through Resource Manager. See Adding resources to a domain.

Services and Apps in multiple domains​

Services​

When you import a service shell, most shells are automatically assigned a default service category which is associated with the Global domain. For custom shells, this may not be true.

To expose a service to users of a non-Global domain, either associate the service to a category that is assigned to that domain or associate the service's category to that domain.

Apps​

By default, all Apps are associated with the Applications category, which exposes those Apps in the Global domain.To expose an App in a non-Global domain, associate the App to a category in that domain. However, you also need to associate the App's deployment to that domain. To learn how to do this, see Managing Public Cloud Apps in Domains or Managing Private Cloud Apps in Domains.