> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Access Manager via Lerian Console

> Manage supported Access Manager operations visually through Lerian Console — users, groups, machine-to-machine applications, and permission assignments.

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.

<Tip>
  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](/en/platform/access-manager/using-access-manager) guide.
</Tip>

## Prerequisites

***

Before using Access Manager features in Lerian Console, make sure you have:

* Access Manager plugin installed and running
* Access Manager [enabled in your environment configuration](/en/platform/access-manager/enabling-access-manager)
* Admin credentials to log into Lerian Console

<Danger>
  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.
</Danger>

## Accessing Access Manager settings

***

Access Manager features are available through the Settings area in Lerian Console:

<Steps>
  <Step>
    Log into Lerian Console with your admin credentials.
  </Step>

  <Step>
    Click the gear icon (<Icon icon="gear" />) in the top navigation bar.
  </Step>

  <Step>
    Select **Users** or **Applications** from the sidebar to manage the respective features.
  </Step>
</Steps>

## What you can do

***

Lerian Console Settings offers two main Access Manager areas:

<CardGroup cols={2}>
  <Card title="Managing Users" icon="users" href="/en/platform/console/managing-users">
    Create, edit, and delete user accounts. Manage passwords and assign users to permission groups for human access.
  </Card>

  <Card title="Managing Applications" icon="layer-group" href="/en/platform/console/managing-applications">
    Create and review machine-to-machine applications for service integrations. Use generated client credentials for secure service communication.
  </Card>
</CardGroup>

## 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](/en/reference/access-manager/am-identity-apis) and [Auth APIs](/en/reference/access-manager/am-auth-apis):

| Area              | Use APIs for                                                                                    |
| ----------------- | ----------------------------------------------------------------------------------------------- |
| Providers         | Create, update, delete, link, unlink, and set default communication providers for MFA delivery. |
| MFA               | Initiate setup, verify passcodes, enable, disable, and change the preferred MFA method.         |
| Token flows       | Request tokens, refresh tokens, retrieve user information, and end sessions.                    |
| Permission checks | Validate a resource-action decision or retrieve the authenticated user's effective permissions. |

<Note>
  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.
</Note>

<Note>
  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.
</Note>

## Next steps

***

* Learn about [best practices for Access Manager](/en/platform/access-manager/am-best-practices)
* Understand the [technical components](/en/platform/access-manager/am-components) of Access Manager
* Review [API reference](/en/reference/access-manager/am-api-introduction) for programmatic access