> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended**:
> ```bash
> npx @scalekit-inc/cli setup
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for 40+ agents.
> Features: full-stack-auth, agent-auth, mcp-auth, modular-sso, modular-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Inspect a user connection in the dashboard

Find a specific connected account in the Scalekit dashboard and read its state without adding logging to your agent.
When an agent suddenly cannot reach a user's Gmail, Calendar, or GitHub, the cause is almost always
the state of that user's **connected account** rather than your code. The dashboard shows that state
directly, which is faster than adding logging and redeploying.

This guide covers only where to look. For what each state means, and the code that fixes it, follow
the links to [Troubleshoot connection errors](/agentkit/authentication/troubleshooting/).

## Find the connection

Go to **Dashboard > Connections** and select the connection the agent uses — the name you pass as
`connection_name` in your code, such as `github-connect`.

Each connection lists the connected accounts created against it. One row exists per user identifier
you have authorized.

> note: One account per user, per connection
>
> A connected account is scoped to a single connection. A user who has authorized both Gmail and
> GitHub has two connected accounts, and they can be in different states.

## Read the row

The row's status is the diagnosis. Only `ACTIVE` accounts can serve tool calls; every other status
names the exact step the user or your app still owes.

The dashboard reports the same value your code reads from `account.status`, so the row and the SDK
never disagree. Use the dashboard for a one-off answer and the SDK when you need the check in code.

For the full status list and the fix for each one, see
[Start with diagnostics](/agentkit/authentication/troubleshooting/#start-with-diagnostics). For the
webhook that pushes these changes to your app instead, see
[Detect when re-authentication is needed](/agentkit/connected-accounts/#detect-when-re-authentication-is-needed).

## Narrow one user versus every user

The row count is the useful signal the SDK will not give you in a single call:

- **One row is failing** — that user needs to re-authorize. Send a fresh authorization link.
- **Every row is failing** — the connection is at fault, not the users. Open the connection's own
  settings and confirm its credentials. A rotated or expired OAuth client on the provider side takes
  down every account beneath it at once.


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |