Before you can create a role account, the role that you want to assign them to needs to be in place first.

When creating an internal role account, you also provide it with a Lequinox console administration access level (this applies even if you do not grant them access to the Lequinox console immediately).

If the Allow sign-up to the Lequinox console was selected, an activation email is sent to the user. If you want to revoke a user's access to the Lequinox console, you need to disable their access manually by disabling their access in the ‘Console user group’. (See Edit a user account in a user group)A user account can be given console access later if it is not provided when their account is created.

If you change any information, Lequinox enabled applications must fetch the information via the REST API if it is to be updated there as well. Information updated in the Lequinox console is not pushed to any other application.

Administrators can change

• name
• email
• console administration level
• status (enabled/disabled)
• access to Lequinox console

Note:

• You cannot change the console administration level of your own role account.
• Role accounts that are still in the INVITED state cannot be enabled or disabled. Also, you cannot disable of your own role account.
• Editing information in a role account does not affect the information in any corresponding access. You need to make corresponding updates via the corresponding user group if they are to agree.
• If a role account is disabled, the status is accompanied with information clarifying why it is disabled. For example, if a role is disabled, role accounts assigned to that role are disabled as well.
• If you want to revoke a user's access to the Lequinox console, you need to disable their access manually by disabling their access in the ‘Console user group’. (See Edit a user account in a user group).