Authdog
Back to journal
Product UpdatesConsoleNavigation

Jump to users and projects from console search

Operators can jump to users and projects from a command-palette search in the console top navigation.

From the changelog: Global search in the console

Authdog Team

2 min read
Centered Authdog mark with an angled Search word plate on a grainy teal wash with dashed command rings

Finding a user or a project in a busy tenant meant walking the sidebar, opening Users or Projects, then scanning a list. Operators can now jump there from a command-palette search in the console top navigation.

This is the longer note behind the July 23 changelog entry.

How it works

The top bar already holds the project and environment switcher and the account menu. Search now opens as a command-palette modal scoped to Users and Projects.

Queries can be narrowed with prefixes:

  • user: — search environment users
  • project: — search projects in the current workspace

Results recognize the three project types the Projects hub already lists: web, machine-to-machine, and MCP. That matches the type rail on the Projects page, so a search hit for an MCP server is not mistaken for a web app.

Selecting a result navigates to that user or project. It does not change organization membership or create resources.

Set it up

Nothing to enable. In the Authdog console:

  1. Open the search control in the top navigation.
  2. Type a name, or prefix the query with user: or project:.
  3. Confirm the project type in the result before you jump — web, M2M, or MCP.
  4. Land on the user or project and continue the work you came for.

Search follows the same console scope as the rest of the shell: organization, tenant, project, and environment selected in the top bar. A tenant-level page that clears the selected project still does so; search will not invent a project context that the page has dropped.

Trust boundaries

Search only lists users and projects your session can already see. It is a navigation control, not an elevation path and not a directory export. Do not treat a search hit as proof the record is safe to edit — open the resource and check audit history when the change is sensitive.

Prefixes reduce noise. They do not bypass tenant isolation. An MCP project still only shows MCP Auth after you select it; a web project does not gain those tools because it appeared in the same palette.

Try it

Open search, type project: plus part of a name, and confirm the type badge before you jump. Layout context is in the console overview. The original release note is in the changelog.

More from Authdog
ShareLinkedInX