> For the complete documentation index, see [llms.txt](https://rawctx.gitbook.io/rawctx-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rawctx.gitbook.io/rawctx-docs/help-center/login-registry-and-token-problems.md).

# Login, registry, and token problems

## Login succeeds but a workspace call fails

Run `rawctx login` again and confirm the selected workspace. The command saves both a user token and tenant registry. Avoid overriding the registry unless the automation deliberately selects a reviewed workspace host.

Check environment precedence:

```bash
rawctx --version
rawctx login --help
```

`RAWCTX_REGISTRY` overrides the saved registry and `RAWCTX_TOKEN` overrides the saved token. The Hub browser BFF is never a valid SDK registry.

## 401 versus 403

* 401: the credential is missing, expired, invalid, or presented to the wrong host.
* 403: authentication succeeded, but token type, role, scope, tenant, or bound application key does not authorize the action.

Application runtime media retrieval cannot use a user token. It requires an application JWT with `answer_audit:evidence:read`.

## Logout and exposure

`rawctx logout` attempts remote revocation and clears local auth. If a token is printed or committed, revoke or rotate it immediately; deleting the log line is not sufficient.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://rawctx.gitbook.io/rawctx-docs/help-center/login-registry-and-token-problems.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.