Accounts management
When managing multiple applications, you can assign specific applications to your accounts and control which users within those accounts can access each application. Let's explore how to make the most of this feature.
Creating new accounts and dashboard
Account management is performed via your_Accounts_ tab in every environment. Here, you can create an account, edit its settings, manage users, and assign/remove applications. Go to Accounts under [ENVIRONMENT] → Management → Accounts sections to learn more about account management.
Single account management
Each of your accounts will have its own dashboard complete with data, KPIs, and configuration options. Upon creating an account, it will not have applications associated with it other than the default app or an auto-assigned app. You will need to go to the Applications tab and choose which applications will be assigned to that account. Note that you can assign applications even if they haven't been integrated yet (they will be marked as inactive
in this case), but should you want your users to access it, you will have to integrate it via the app configuration tab. Go to [Creating Multiple Applications] to learn more.
Applications tab
The Applications tab within your backoffice allows you to assign applications to that specific account. To assign new applications, click the Assign application button.
A drawer listing all of the available applications will be opened to the right. You can choose the applications you want to assign to that account and then click Assign.
You can add applications even if they are not yet set to Active (i.e., not integrated).
Default and auto-assigned apps
While you can set a default app for users to be allocated with when managing multiple applications, this setting is optional, in case you have at least one application per environment. Note that to ensure users can login to an app, you will need to add an appID
in your integration's contextOptions
(see note).
If an application is marked as auto-assigned, then all accounts and users will be assigned with it automatically. This is relevant whether the application was created prior or post to the creation of the accounts/users.
Possible errors when you don't set a default app
Possible errors when you don't set a default app
If a user navigates directly to the login URL without you specifying the appId
in the path, they won't be able to log in and will be redirected to an error page instead. To solve this issue, ensure you provide an appId
within your contextOptions
.
When there is no default nor auto-assigned application, you will need to assign users to an application manually, either via our APIs or via the backoffice.
SSO (SAML and OIDC)
SSO (SAML and OIDC)
Login with Single Sign-On is not supported when an application is not auto-assigned and there is no default application. New users that do not have explicit assignments to an application will not be able to login.