| Expand | ||||
|---|---|---|---|---|
| ||||
|
...
| Expand | ||
|---|---|---|
| ||
When the certificates of a server account – the digital identity of an application – are about to expire, users with organisation administration access receive an email informing them that the validity of the server account is about to expire. The certificates are renewed in the Lequinox console. Read more on how to renew an existing server account certificate. |
...
Console administration levels
...
| Expand | ||
|---|---|---|
| ||
Accounts with the administration level ‘regular user’:
|
...
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 | ||
|---|---|---|
| ||
|
...
A user-managed account is managed by the user via Lequinox professional ID, which the user can download from Google Play before they /wiki/spaces/LC/pages/1148587 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.
...
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 | ||
|---|---|---|
| ||
|
...
| Expand | ||
|---|---|---|
| ||
Read more about accesses on the developer concepts page. |
...
| Expand | ||
|---|---|---|
| ||
Read more about server accounts on the developer concepts page. |
...
| Expand | ||
|---|---|---|
| ||
The developer decides – together with stakeholders – which services should be activated or not for a transaction and, when applicable, which values should apply. Read more about /wiki/spaces/LPDA510/pages/1803930 transactions on the developer concepts page. |
...