> For the complete documentation index, see [llms.txt](https://synap.ac/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://synap.ac/docs/platform/portal/pages-and-navigation.md).

# Pages and navigation

Pages and navigation control the main areas available to each User type and how those areas appear in the portal menu.

{% hint style="info" %}
**Location:** Settings → User access → Administrators, Managers, Educators or Students
{% endhint %}

Administrators, Managers, Educators and Students can each have a different set of pages, labels and menu order. This lets the learner experience remain simple while staff roles retain the tools they need.

### Page controls

| Control          | What it changes                                         | What to check                                              |
| ---------------- | ------------------------------------------------------- | ---------------------------------------------------------- |
| Enabled          | Makes the page available to this User type              | Content access and Permissions still apply inside it       |
| Menu order       | Changes where the page appears in navigation            | Keep frequent tasks easy to find                           |
| Navigation label | Replaces the default menu wording                       | Use short, recognisable text and check translations        |
| Description      | Adds supporting text where the page exposes it          | Explain the page’s purpose rather than repeating its label |
| Icon             | Changes the page’s navigation icon                      | Use a familiar, distinct symbol                            |
| Redirect         | Sends the user to another enabled page when appropriate | The destination must remain enabled and accessible         |
| Page components  | Configures supported sections, cards or tabs            | Options vary by page and enabled portal features           |

### Standard page areas

Learner configurations can include Home, Exams, Progress, Collections, Assignments, Insights and Diagnostics. Administrative configurations can include the Portal dashboard, Library, Courses, Collections, Assignments, User groups, Exams, Attempts and Attempts marking. Portal Store and Marker’s Inbox appear when their related features are available.

Some pages contain configurable components. For example, Home can expose Study overview, Assignments, Mock Exams, Flags or Tips. Student Insights can expose Overview, Attempts and Learning Records; at least one available tab must remain enabled.

### Page visibility and access are different

Enabling a page does not give unrestricted access to everything inside it. The effective experience can also depend on:

* the person’s User type and group memberships;
* staff Permissions;
* learner content access;
* portal or Subportal scope;
* the availability and schedule of the content; and
* enabled portal features.

Likewise, hiding a navigation entry is not a security boundary. Apply the relevant Permissions and access policies when sensitive administrative data or actions must be restricted.

### Pin a Note to the menu

A Library Note can be added as a role-specific menu page. This is useful for a custom information page that should be easy to reach. The same Note cannot be pinned twice for one role, and each role can have up to three active Note pages. A pinned Note can have its own label, description and icon.

### Test navigation changes

After changing a User type, sign in with a representative account of that type and check:

* desktop and mobile menus;
* the default landing page;
* renamed navigation items;
* redirects and direct links;
* empty states where no content is available; and
* pages that should remain inaccessible.

Navigation changes can require a browser refresh before they appear. Avoid renaming established pages immediately before training or a live assessment when existing instructions may still refer to the old wording.


---

# 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://synap.ac/docs/platform/portal/pages-and-navigation.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.