> For the complete documentation index, see [llms.txt](https://docs.cw.crisisworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cw.crisisworks.com/security-and-support/faqs/troubleshooting/system-administration/cant-access-the-system-administration-menu.md).

# Can't access the System Administration menu

## Problem

You've signed in, but can't access the System Administration menu.

## Explanations

### The menu may not have loaded correctly

Certain factors can sometimes cause a delay in menus loading after going on duty, such as the loading of system permissions.

#### Solutions

Refresh the webpage. If this doesn't help, try running the [Diagnostics](/concepts-and-fundamentals/on-a-computer/your-user-profile-and-duties.md#diagnostics), this can help reload the permissions for the menus.

### Don't have the right position

You need the [Data Entry position](/system-administration/configuring-the-system.md#system-administration-positions) to be able to access the System Administration menu.

#### Solutions

Check your [user profile](/concepts-and-fundamentals/on-a-computer/your-user-profile-and-duties.md) and make sure you have the Data Entry position. If you don't have this position, ask your administrator to add it.

{% hint style="info" %}
Service Desk cannot add this position for you without written authorisation from an authorised contact within your organisation due to Information Security policy.\
If you need access straight away, please contact your administrator.
{% endhint %}

## More Help

If you still need help, [contact the Service Desk](/security-and-support/maintenance-and-support/accessing-support.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cw.crisisworks.com/security-and-support/faqs/troubleshooting/system-administration/cant-access-the-system-administration-menu.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.