Skip to main content
Not everything in Access Manager needs an API call. Lerian Console gives you a visual home for the access tasks most administrators handle day to day. From the Console’s Settings area, 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, MFA setup, 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:
Once Access Manager is enabled, 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.

​
Accessing Access Manager settings

Access Manager features are available through the Settings area in Lerian Console:
1
Log into Lerian Console with your admin credentials.
2
Click the gear icon () in the top navigation bar.
3
Select Users or Applications from the sidebar to manage the respective features.

​
What you can do

Lerian Console Settings offers two main Access Manager areas:

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, but not all of them. For anything that isn’t in Console settings, reach for the Identity APIs and Auth APIs:
In multi-tenant deployments, Console follows the same tenant boundary as the APIs. The logged-in administrator only sees and manages users and applications in the tenant carried by their authenticated context.
You cannot delete the user you are logged in as. The default admin user created during Access Manager installation can be deleted by another administrator, and the installer does not recreate it afterwards — make sure another administrator exists before removing it. You can update its details and password through the Console.

​
Next steps