Contents

Certificates

A digital certificate is used as a proof of identity, and can be compared to a driver’s license or a passport.

More

In the Lequinox® platform, all personal identities, role accounts, application accesses and server accounts have three certificates used for authentication, encryption and signing. The Lequinox platform uses self-signed X.509 certificates.

Expired certificates

Every certificate has a set validity period, and once it has expired, it is no longer accepted in the Lequinox platform and needs to be renewed. For example, a sign certificate generally has a validity period of three years.

More

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

The administration level applies to internal role accounts and is set when an account is created.

Organisation user

The lowest console administration level.

More

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.

Organisation administrator

The highest console administration level for a connected organisation.

More

Accounts with the console administration level ‘Organisation administrator’:

Can do everything that accounts with the administration levels ‘Organisation user’ 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.

Platform administrator

The highest console administration level, reserved for the platform owner. This administration level is not available to connected organisations.

More

Accounts with the console administration level ‘Platform 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.

User accounts tuesday

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, corporate or server type.

The private and corporate types can be provided with application accesses within or between platforms. In addition to these, the private and corporate user account types are backed by a personal (identity) account, which acts as a witness in transactions.

Role accounts and external personal identities must be configured as platform-managed. These, in turn, may be connected to a platform-managed access.

A server account is platform-managed by design and cannot have a personal identity or any accesses.

Add matrix, or save that for Developer Concepts?

Role accounts

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.

The highest administration 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.

More

Organisation and Platform administrators 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.

Internal vs external role accounts

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.

More

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

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.

A role is internal or external, depending on whether it is to be assigned to internal role accounts or external role accounts.

The user agreement you want to assign to the role must be created before you create the role.

More

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

External personal accounts cannot be assigned any role.

Transactions

The Lequinox platform allows users or applications to create, send and open encrypted transactions via Lequinox-enabled applications. Transactions also include a number of services that affect what a transaction creator or participant can and cannot do, and when.

More

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.

The term transactions does not refer to financial transactions, but traceable transfers of data with integrity intact.