Domain customization via contexts

Prev Next

Customizing user experience accessing a specific Application Workspace domain with the Contexts Functionality

Using multiple domains is useful when your organization undergoes a name change or if you want multiple organizations to connect to the same zone while retaining branding per domain and still delivering applications from a single portal.

Customizing a workspace for a specific domain enhances the user experience by tailoring access, settings, and branding to meet specific needs while maintaining organizational identity. It increases security through domain-specific access policies and ensures efficient allocation of packages and compliance with the internal organization data access hierarchy.
Such a customization can be obtained in Application Workspace by through the contexts feature.

Requirements

Your user account should be assigned an access policy with the privileges to create, modify and remove domains in Application Workspace.
Your user account should be assigned an access policy with the privileges to modify identity sources and configure the authentication of users according to your needs.

Creating a filter type context

You can define the filter type context in Manage > Identities > Context.
Within the new context, you need to define a filter with the following parameters:

Type - Select Hostname
Compare - Select Equal
Value - Write the new domain

Configuring custom settings for the new domain

With the new filter type context in place, you configure various aspects of the Application Workspace for your users such as
variables, access policies, content access, agent settings, portal settings, user settings, login settings, packages and deployments.

Recommendation

You should proceed carefully when configuring the new domain, as Application Workspace offers a range of configurations from simple setups to complex, intricate configurations, requiring careful planning to avoid misconfigurations that could impact functionality or security.
Once configured, we recommend you test the context to ensure it aligns with the intended customization goals, on a small number of test-designed workspaces, before applying it globally.