The **Authdog console** at [console.authdog.com](https://console.authdog.com) is where you configure everything Authdog does for your application: how people sign in, what they are allowed to do, what gets logged, and how tokens are issued.

This page explains how the console is laid out so the rest of the console reference makes sense.

![Console overview](/content/console/overview.png)

## The resource hierarchy

Every screen in the console is scoped by four nested resources:

**Organization > Tenant > Project > Environment**

| Level | What it is | Scope of settings |
|-------|-----------|-------------------|
| **Organization** | Billing and administrative boundary that groups tenants. | Subscription tier, linked tenants. |
| **Tenant** | The workspace. Holds projects, team members, and verified domains. | Team access, invites, APEX domains. |
| **Project** | One application — a web app, a machine-to-machine client, or an MCP server. | Display name, environments, deletion. |
| **Environment** | A deployment stage of that project (`dev`, `prod`, …). | Almost everything else: sign-in methods, roles, policies, secrets, branding. |

Most configuration is **per environment**, not per project. Enabling passkeys in `dev` does not enable them in `prod`. This is deliberate: it lets you roll a change through stages the same way you roll out code.

> **Tip**
>
> The **Overview** page shows the Project ID and Environment ID for the current
> selection. Those two values are what your SDK configuration needs.

## Top bar

The bar across the top of every page carries your current context and the global tools:

- **Context breadcrumb** — the selected project and environment. Click either one to switch. Switching the environment keeps you on the same page, so you can compare `dev` and `prod` side by side.
- **"+" button** — quick-create menu for a new project, tenant, or organization.
- **Search** — typeahead across your workspace. Prefix a query with `user:` to search end users, or `project:` to jump to a project.
- **Time range** — on analytics-bearing pages (Dashboard, Audit, Lidar), sets the window all charts and tables read from.
- **Notifications** and your **account menu**.

## Sidebar

The left navigation is grouped by what you are trying to do:

| Group | Modules | Purpose |
|-------|---------|---------|
| _(top)_ | Overview, Users, Projects, Dashboard, Organizations, Elevate, Billing | Your workspace and the people in it. |
| **Products** | Authentication, Authorization, Audit, Lidar, Vault, MCP Auth | The capabilities you turn on and configure. |
| **Developer** | Domains, Redirects, Branding, Notifications | How the hosted identity experience looks and where it sends people. |
| **Configuration** | Settings | Project details and environments. |

The sidebar footer holds **Support Center**, **Tenant Settings** (tenant owners only), and, for Authdog staff, review queues such as **Access Requests**.

Two modules appear conditionally:

- **MCP Auth** shows up only when the selected project is an MCP server.
- **Authorization** sub-items change with the environment's permission model — RBAC shows Resources/Roles/Groups, ABAC shows Policies, FGA shows Relationships.

## Module layout

Modules with several screens use one of two patterns. Larger modules (Authentication, Authorization, Users, Vault, Branding, Notifications, Elevate, Billing) use a **vertical rail** on the left that you can collapse; a **RELATED** block at the bottom of the rail links to neighbouring modules. Smaller modules (Audit, Lidar) use a **horizontal tab strip** under the page title.

Tabs are addressable. `?tab=methods` on the Authentication page opens the Methods tab directly, which makes console URLs safe to bookmark and share.

## Picking a context

When you sign in without a saved selection, the console walks you down the hierarchy:

1. **Tenants** — pick or create a workspace.
2. **Projects** — pick a project. Selecting one pins its first environment and drops you on the **Dashboard**.
3. From there every module reads the selected project and environment.

Visiting a tenant-level page such as **Organizations** clears the project selection, because those pages sit above a project in the hierarchy. Pick a project again from the Projects hub to return to environment-scoped modules.

> **Warning**
>
> Switching project clears the current environment selection. Save changes in a
> settings form before you switch context.

## Related

| Read | To learn how to |
|------|-----------------|
| [Tenants](/docs/console/tenants) | Create, join, and administer tenant workspaces |
| [Projects](/docs/console/projects) | Create web, M2M, and MCP projects |
| [Environments](/docs/console/environments) | Separate dev, staging, and production configuration |
| [Dashboard](/docs/console/dashboard) | Read the environment health board |
| [Multi-tenancy](/docs/concepts/multi-tenancy) | Understand the isolation model behind the hierarchy |