After activating the Enterprise Toolkit add-on, your organizational account is effectively upgraded to what we call a Master account.
The Master account is your top-level account that provides the default values and settings for any Environments you create thereafter.
Most customers use the Master account as their “production” or “live” account for everyday business use while using Environments for testing or departmental-specific use cases.
One essential function that you gain from a Master account is the ability to create Environment accounts as desired. These could be for testing or development purposes, or to separate different departments or business units from each other completely.
Environment accounts are completely standalone – each has its own set of Users, Screens, Data Sources, Tasks, etc. These accounts are linked to your Master account, and you are billed according to the total number of users across all your accounts.
Users in your Master account can also be created in your Environment accounts using the same email address. When you do so, these Master users will count as a single-user license instead of an extra user license per the Environment in which they appear.
Creating a New Environment
- Go to Platform & Billing or Manage Platform > Environments
This will take you to the “Environments” page. - Click the Add New option (top right)
This will take you to the “Create Environment” page.
On the “Create Environments” page, you’ll be able to fill out the Environments Basic Settings (Name, Description) and configure its Regional Settings (Country, Time Zone, Date/Time Formats, Measurement System) if they differ from the Master Environment.
Once complete, hit “Create” (top right), and you should be presented with an “Organization XXX was created successfully” message.
Once you have created a new Environment, remember that it starts as empty – it has no screens, data sources, users, etc. You now need to add users, screens, etc., which you can do while being logged into the Environment’s context.
Either start from scratch and add users and context as desired, or copy over content from your Master (or other Environment) account using our Repository feature.
What is an Environment Context
When you create a new Environment, the system also switches your operating context into that Environment account. What this means is that the system will act as if you are logged into that account as an administrator.
Note you are not an actual user of that account. You are essentially an invisible administrator by virtue of your Master account login.
By default, only users with the access level of “Enterprise Admin” in your Master account gain this context-switching facility unless a lesser user role has been granted permission to switch context (See Switching Context User Permissions section below.)
You should also notice the Context Identifier at the top-center of the page, which has the name of your current Environment context. If clicked, you’ll be taken to the Environments page, where you can switch context to your Master account or other Environments as desired.
Switching Context User Permission
When adding users to an Environment and granting them website access, additional permissions become available to access areas depending on the user’s role (Read-Only, Read/Write, Administrator).
One permission in particular, unique to Master account users that aren’t administrators, is Can Switch Context, which grants access to the Environments page and to switch Environments when necessary.
This Can Switch Context feature can be applied to Read-Only, Read/Write, and Administrator users. EnterpriseAdmin users have this permission hard-set.
When a user has the Can Switch Context checked, the user will be allowed to navigate to a different environment, but the permissions for this user will be the same as the permissions set where the Can Switch Context is checked.
For example, you could have support personnel that needs access to all Environments of your organization but are prevented from editing. Before, access to all Environments was only possible with users set to Enterprise Admin. Now, with the Can Switch Context permission checked, Non-admin users can be granted access to navigate between all Environments swiftly.
Deleting an Environment
If you ever need to delete an Environment, please refer to our documentation Deleting an Environment.