| Expand | ||||
|---|---|---|---|---|
| ||||
|
...
In the platform, a user account can be represented in the form of an internal or external role account, an external personal account (in the REST API referred to as an external personal identity) or a server account. As such, a user account is either of the private, organisation (referred to as corporate in the REST API) or server type.
The private and corporate organisation types can be provided with application accesses within or between platforms. In addition to these, the private and corporate organisation user account types are backed by a personal account (in the REST API referred to as a personal identity) account, which acts as a witness in transactions.
...
A role account is used as an identifier for a user in an organisation in the Lequinox platform. When created, a role account is assigned a role and – if it is an internal account – a console administration level as well.
...
.
| Expand | ||
|---|---|---|
| ||
Accounts with the console administration level Organisation and Platform administrators can Platform administrator can add and edit role accounts (but not their own). Organisation users do not have access to the Role accounts page. Organisation and 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. Accounts with the console administration level Organisation user only have access to their transaction archive. |
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 | ||
|---|---|---|
| ||
|
...