| Expand | ||||
|---|---|---|---|---|
| ||||
|
...
| Expand | ||
|---|---|---|
| ||
Accounts with the administration level ‘Organisation user’:
|
Role administrator
An administration level that provides access to role accounts and archive, and can add and manage role accounts that have been assigned the same role as they have.
| Expand | ||
|---|---|---|
| ||
Accounts with the administration level ‘Role administrator’:
|
Organisation administrator
The highest console administration level for a connected organisation.
| Expand | ||
|---|---|---|
| ||
Accounts with the console administration level ‘Organisation administrator’:
|
...
Platform administrator
The highest console administration level, reserved for the platform owner. This administration level is not available to connected organisations.
| Expand | ||
|---|---|---|
| ||
Accounts with the console administration level ‘Lequinox ‘Platform administrator’:
|
...
| Info |
|---|
When creating an internal role account, you also provide it with one of three a Console administration access levels . There is a fourth level in the platform organisation, Lequinox administrator, but it (this also applies if you do not grant them access to the Lequinox console immediately). The highest level, Platform administrator, should be reserved for a select few in the platform organisation that need to be able to connect customer organisations and other platform administrators. |
| Expand | ||
|---|---|---|
| ||
Role, organisationOrganisation and Lequinox Platform administrators can add and edit role accounts (but not their own). Regular Organisation users do not have access to the Role accounts page. Organisation and Lequinox Platform administrators can invite a new user to the Lequinox console by creating a role account for them. In the process, they also assign the user an organisation role and decide the console administration level of the account, and whether it shall be organisation or user managed. |
Internal vs external role accounts
| Anchor | ||||
|---|---|---|---|---|
|
Internal role accounts are primarily intended for users closely linked to your organisation, like employees. External role accounts are intended for users not part of your organisation, like contractors, vendors or corporate customers, but you want to interact with them via Lequinox enabled applications and get traceability for these interactions.
| Expand | ||||
|---|---|---|---|---|
| Before you can create a role account, the role and the adhering user agreement that you want to assign them to needs to be created first.||||
|
...
|
...
|
...
Organisation-managed
...
|
...
|
...
| Expand | ||
|---|---|---|
| ||
|
User-managed
A user-managed account is managed by the user via Lequinox professional ID, which the user can download from Google Play before they activate their account.
Set an account to User-managed if the user is to be able to sign transactions via Lequinox professional ID. Once created, a user-managed role account must be activated via the invitation email that the console sends to the user. Hence, the user must install Lequinox professional ID to complete their account activation.
| Expand | ||
|---|---|---|
| ||
|
Roles
...
...
Roles
When a role account is created, it must be assigned to one of the available roles. To activate their account and their role, the user must sign the agreement connected to that role. Accounts with the console administration levels Organisation and Platform administrator can add and edit internal and external roles associated with the organisation they belong to. Roles must also be connected to their respective agreements. When a role account is created, it must be assigned to one of the available roles. To activate their account and their role, the user must sign the connected agreement.
A role is internal or external, depending on whether it is to be assigned to internal role accounts or external role accounts.
| Info |
|---|
The user agreement you want to assign to the role must be created before you create the role. Note that external roles can also be created through a Lequinox enabled application via functions in the platform REST API. |
| Expand | ||
|---|---|---|
| ||
|
...