website/docs/users-sources/user/user_basic_operations.md
The following topics are for the basic management of users: how to create, modify, delete or deactivate users, and using a recovery email.
Policies can be used to further manage how users are authenticated. For example, by default authentik does not require email addresses be unique, but you can use a policy to enforce unique email addresses.
If you want to automate user creation, you can do that either by invitations,
user_writestage, or using the API.
You should see a confirmation pop-up on the top-right of the screen that the user has been created, and see the new user in the user list. You can directly click the username if you want to modify your user.
:::info To create a super-user, you need to add the user to a group that has super-user permissions. For more information, refer to Create a Group. :::
You can create advanced queries to locate specific users within the list shown under Directory > Users in the Admin interface. Use the auto-complete in the Search field or enter your own queries to return results with greater specificity.
Field: username, path, name, email, path, is_active, type, attributes
Operators: =, !=, ~, !~, startswith, not startswith, endswith, not endswith, in, not in
Values: True, False, None, and more
Example queries:
is_active = Falseusername = "bob"email = "[email protected]"attribute.my_custom_attribute = "foo":::info
In the Directory > Users menu of the Admin interface, you can browse all the users in your authentik instance.
To view details about a specific user:
In the list of all users, click on the name of the user you want to check.
This takes you to the Overview tab, with basic information about the user and quick access to perform basic actions on the user.
To see further details, click any of the other tabs:
After the creation of the user, you can edit any parameter defined during the creation.
To modify a user object, go to Directory > Users, and click the edit icon beside the name. You can also go into user details, and click Edit.
You cannot directly grant a user any permissions. Instead, either assign the user to a role with the appropriate permissions, or add a user to a group that has the appropriate permissions (via the group's role/roles).
On the flipside, to grant permissions on a user object to a role, review "Manage permissions".
:::info Users also inherit roles from the groups they belong to. The Roles tab has two sub-tabs: Assigned Roles shows roles directly assigned to the user, while All Roles shows all roles including those inherited from groups. Inherited roles are marked with an "Inherited" label. :::
These bindings control which users can access an application, and whether or not the application is visible in the user's My applications page. If no bindings for an application are defined, this means that all users and groups can access the application.
For instructions refer to Manage applications.
If a user has lost their credentials and needs to recover their account, there are two available options:
Both options require you to configure a recovery flow and set it as the Default recovery flow for the active brand.
To get started, you can import this example flow: Recovery with email verification flow
Then, set this as the default recovery flow for the active brand:
default-recovery-flow.Now that you've configured a recovery flow, you can select one of the following options:
:::info Email stage not required The example recovery flow includes an email stage. However, if you're manually sending the recovery link to the user, this email stage is not required and can be removed. :::
A pop-up will appear on your browser with the link for you to copy and to send to the user.
:::info Email stage required This option is only available if the default recovery flow has an Email Stage bound to it. The example recovery flow includes an email stage. :::
You can send a link with the URL for the user to reset their password via Email. This option will only work if you have configured email and set an email address for the user.
If the user does not receive the email, check if the mail server parameters are properly configured.
As an Admin, you can simply reset the password for the user.
The active sessions are revoked and the authentication of the user blocked. You can reactivate the account by following the same procedure.
:::caution This deletion is not reversible, so be sure you do not need to recover any identity data of the user. You may instead deactivate the account to preserve identity data. :::
The user list refreshes and no longer displays the removed users.
With authentik, an Admin can impersonate a user, meaning that the Admin temporarily assumes the identity of the user.
:::info An Admin can globally enable or disable impersonation in the System Settings. By default, this option is set to true, meaning all users can be impersonated.
An Admin can also configure whether inputting a reason for impersonation is required in the System Settings. :::
You can export your authentik instance's user data to a CSV file. To generate a data export, follow these steps:
To review, download, or delete past data exports, navigate to Events > Data Exports in the Admin interface.