Users

Administration › Users lists the people who can sign in, their roles and whether they still have access. Search by name or email to find someone.

Administrators can manage every user. Other people can manage users when one of their roles has the administration permission Invite, edit and deactivate users, within the limits described below.

Adding a user

New user asks for:

• First name and last name;
• Email, which the person signs in with;
• a password of at least 8 characters. Tell it to the person, who can change it after signing in;
• their roles: what they may see and do. See roles and permissions;
• their main role, which decides their home page and defaults when their roles differ. If you leave it, the first of their roles is used.

Qorekit does not send email yet, so there is no invitation message: give people the address of your installation, their email and their password yourself.

Changing a user

Select a user to change their details, roles or password. Leave New password empty to keep the current one.

You cannot change your own roles or deactivate yourself, so that nobody locks themselves out by accident.

Deactivating a user

Turn off Active when someone leaves. An inactive user cannot sign in, and is signed out everywhere at once. Their records, and their name on the records they created or changed, stay.

There is always at least one active administrator: Qorekit refuses to deactivate the last one or take away their role.

Your own fields on users

Users are an entity, so you can add fields to them, such as a department, a phone number or a manager. Design on the Users page opens the users entity's fields. Built-in fields such as the name and email cannot be removed.

User managers

A role with the permission to manage users does not make its holders administrators. A user manager:

• can give and take away only the roles that their own roles allow (see roles a user manager may give);
• can change the password, email or active state only of users whose every role they could have given themselves. They cannot, for example, reset an administrator's password and sign in as them;
• cannot change administrators at all.