# FAQ and troubleshooting

## I cannot see a control

**Settings** and **Credits** require the Admin role.
**New audit** requires Member or Admin access and an active workspace.
The audit's available actions depend on its current state and your access.
Ask a workspace Admin to check your membership. [Roles](/docs/features) lists what each role can do.

## My key stopped working

HTTP `401` means credentials are missing or invalid. Check expiry and revocation in **Profile → API keys**.
HTTP `403` means your workspace role does not allow the request. That role is your account's workspace role, limited by the key's role. A new key does not raise it. HTTP `404` also covers resources outside your access.
Use [API keys](/docs/api-keys) to replace a key safely.

## The quote or launch failed

- HTTP `402`: the workspace lacks credits. See [Add credits](/docs/flows/credits). In a funded workspace, ask a funding workspace Admin.
- Missing private repository: ask an Admin to [connect GitHub](/docs/flows/github) and grant access to the repository.
- Missing commit: push the commit and use its full hash.
- Active audit on the revision: inspect the existing audit before submitting another.
- Invalid context: use non-empty UTF-8 text with a document title and description.

## Where is my report?

Open the audit and use **Export**. See [Comment, share and export](/docs/flows/comment-share). Or run `zerocool report <job> -o report.md`.
If a newer fork exists, use that audit to add comments and response statuses.
Read the status message when an audit is interrupted or fails.

## Contact Zero Cool

Open **Help and feedback** in the account menu. Select **Feedback** or **Bug report**.
Include the action you tried and the message you saw. Do not include an API key.