> For the complete documentation index, see [llms.txt](https://docs.netmap.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.netmap.dev/troubleshooting/permission-errors.md).

# Permission Errors

`403` means authentication succeeded, but the user or API-key owner lacks the required role or permission.

Check Admin role permissions for:

* `topology_write`
* `security_view`
* `tools_passive`
* `tools_active`
* `inventory_export`
* `firewall_export`
* `report_export`
* `ipam_write`
* `monitoring_write`
* `alert_write`

## 401 Versus 403

`401` means NetMap did not accept the authentication. Check the session, bearer token, or API key.

`403` means authentication worked, but the role does not allow the action.

## API-Key Example

If this succeeds:

```bash
curl --fail-with-body \
  --url "https://netmap.example.com/api/v1/auth/me" \
  --header "X-API-Key: <api-key>"
```

but a feature endpoint returns `403`, update the owning user's role or permissions.

## SuperAdmin-Only Actions

Some actions require SuperAdmin regardless of named permissions, including user administration, many system settings, OIDC configuration, global API-key oversight, diagnostics, backup, and restore.

## Related Pages

* [Permissions](/security/permissions.md)
* [API-Key Permissions](/api/api-key-permissions.md)
* [Administration](/using-netmap/admin.md)


---

# 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://docs.netmap.dev/troubleshooting/permission-errors.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.