Skip to main content
Lerian Console offers a visual interface for the access tasks most administrators handle day to day. From Lerian Console you can create and manage users, assign permission groups, and set up machine-to-machine applications without touching the Identity APIs.
If you need the full API surface, including providers, application-provider links, token flows, or explicit permission checks, use the Using Access Manager guide.

​
Prerequisites

Before using Access Manager features in Lerian Console, make sure you have:
After you enable Access Manager, protected API requests must include an Authorization header with a valid Bearer access token.Without this header, protected requests will be rejected, even for endpoints that were previously accessible without authentication.

​
Where the Access Manager screens live

Lerian Console holds the Access Manager screens in two areas. Settings holds Applications and Security. Authorization holds Users, Roles, Groups, and Permissions, with its own sidebar.
1
Log into Lerian Console with your admin credentials.
2
Click the gear icon () in the top navigation bar.
3
Select Applications or Security to open Settings. Select Authorization to open the Authorization area.

​
What you can do

Managing Users

Create, edit, and delete user accounts. Manage passwords and assign users to permission groups for human access.

Managing Applications

Create and review machine-to-machine applications for service integrations. Use generated client credentials for secure service communication.

​
What still uses APIs

Console covers the common cases. For anything the Console does not cover, use the Identity APIs and Auth APIs:
Users enroll and manage their own multi-factor authentication methods in the Console, under Settings › Security.
On Lerian Cloud, Console follows the same tenant boundary as the APIs. The logged-in administrator only sees and manages users and applications in their own tenant.
You cannot delete your own user. Another administrator with the delete permission on users can delete a seeded administrator account. A later run of the install step can recreate it with its default password. Change that password before exposing the deployment. Make sure another administrator exists before removing one. You can update its details through the Console.

​
Next steps