---
title: Profile
description: The account view at
---

# Profile



## Purpose

PROFILE shows who you are signed in as, your effective role, and the session details for this console. The top-bar identity chip opens it.

Deep link: `ops.useargus.co/#/profile` (nav group ACCOUNT).

## What it shows

Two cards, with content depending on the console mode:

* Identity and session. In proxy mode (the console embedded in the portal): signed in as, name, organization, role from your Clerk portal session, and the backend principal (a platform-admin token injected by the portal proxy). In standalone mode (ops.useargus.co): whether a token-based session is active and the operator token's last 4 characters, never the value. Both modes show the active tenant, the backend URL, and the mode.
* Role and access: your effective role badge with a note on where it comes from, plus the staff role model for reference: Super admin (full platform and ops access), Developer (DevTools, logs, schema, metrics; no billing or user management), Support (read-only tenant health, audit logs, sign-in events), and Fundraising (reporting and partner-facing views; scope being defined). The page is honest that role-based access is display-only in the console today; navigation gating by role exists but degrades to show-all for admin operators.

In standalone mode the console can also derive the role from the operator PAT's preset via the whoami endpoint (`GET /v1/operators/me`).

## Actions

* SIGN OUT: in proxy mode signs out of the Clerk session; in standalone mode it scrubs the operator token from the browser.
* CF ACCESS LOGOUT (standalone only): ends the Cloudflare Access perimeter session, which is separate from the local token.
* SET TOKEN (standalone) or SIGN IN (proxy) when no session is active.

## Matching CLI

```bash
argusctl whoami
```

See [argusctl core commands](/docs/cli/core).

## Notes

* This view does not poll; identity is static within a session and refreshes in place on a credential change.
* Standalone sign-out clears the local token only; the Cloudflare Access session must be ended separately with CF ACCESS LOGOUT.


---

For a semantic overview of all documentation, see [/sitemap.md](/sitemap.md)

For an index of all available documentation, see [/llms.txt](/llms.txt)

For agent-facing discovery, including API and MCP surfaces, see [/agents.md](/agents.md)