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.

Accounts with the administration level ‘Organisation user’:

• Have access to transactions they have taken part in when they go to Archive in the top navigation bar.
• Have access to the account overview.

Accounts with the administration level ‘Role administrator’:

• Can see and do the same things accounts with the administration level regular user can.
• Can see all organisation transactions in which participants with the same role as them have participated, regardless of console administration level.
• Can only manage role accounts that correspond to their own role.
• Have access to My transactions and Role transaction events, a list of all transaction events relating to the same role that they are assigned to.

Accounts with the console administration level ‘Organisation administrator’:

• Can do everything that accounts with the administration levels ‘regular user’ and ‘role administrator’ can do.
• Can create and edit roles and role accounts, and add new applications, user groups and server accounts.
• Can see detailed information about all the organisation's transactions in the archive.
• Are authorised to edit information on their organisation under Settings.
• Can add role and application agreements.
• Has access to create statistical reports on a recurring basis.

Accounts with the console administration level ‘Lequinox administrator’:

• Can do everything that accounts with the administration level ‘organisation administrator’ can do.
• Can also add new organisations but for integrity reasons, they cannot not view their roles, role accounts, applications or transactions.

Role, organisation and Lequinox administrators can add and edit role accounts (but not their own). Regular users do not have access to the Role accounts page.

Organisation and Lequinox 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 administration level of the account, and whether it shall be organisation or user managed. 

• 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.
• External role accounts can be created through a Lequinox-enabled application using functions in the Lequinox platform REST API.
• Internal role accounts can only be created via the Lequinox console, not via the platform REST API.

• With an organisation-managed role account, the user will not be able to sign in to the Lequinox console.
• No activation email is sent to the user (see User-managed below).
• You cannot reinvite an organisation-managed user. If you change first name, last name, email address or administration level, the updated information must be fetched via the REST API. The updated information is not pushed to any connected applications.
• Once set, ‘Managed by’ for a role account cannot be changed.

• With a user-managed role account, the user will be able to sign in to the Lequinox console or a Lequinox-enabled application via Lequinox professional ID.
• An activation email is generated and sent to the user.
• You can reinvite a user-managed account. If you change first name, last name, email address or administration level, the updated information is pushed to Lequinox professional ID.
• Once set, ‘Managed by’ for a role account cannot be changed.

• External roles can be created from a Lequinox-enabled application using functions in the platform REST API.
• Internal role accounts can only be created via the Lequinox console, not via the platform REST API.

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 transactions on the developer concepts page.