> 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/overview.md).

# Overview

A portal is the branded, user-facing environment in which your organisation delivers learning and assessments. Portal settings control the identity of that environment, how users enter it, what appears in their navigation, and the defaults used across the learner experience.

### What can be configured

* **Identity and appearance:** portal name, branding, registration page and search metadata.
* **Access:** registration, local and external authentication, and multi-factor authentication (MFA) policy.
* **Communication:** sender details, welcome emails, consent and notification preferences.
* **Experience:** language, time zone, role-specific pages, study settings and mobile-app links.
* **Structure:** sub-portals can provide distinct audiences with their own access and presentation.
* **Integrations and automation:** API tokens, webhooks, Zapier, identity providers and analytics connections.

### Before changing portal settings

Portal settings can affect every user. Changes to login methods, registration, role navigation and language should be tested with a representative account before a live assessment window. Some controls are entitlement-dependent and are disabled when the relevant feature is not included in the portal's plan.

Settings are available from **Portal dashboard → Settings**. The exact entries shown depend on the signed-in administrator's permissions and the portal's enabled features.

### Understand the scope of a change

| Setting area                        | Who is most likely to notice it             | Test with                                                    |
| ----------------------------------- | ------------------------------------------- | ------------------------------------------------------------ |
| General, branding, pages and locale | Most portal users                           | A logged-out visitor, student and administrator              |
| Registration and authentication     | Anybody creating or accessing an account    | A new user and a separate emergency administrator account    |
| Email and invites                   | New users and assessment participants       | A real test inbox on common mail providers                   |
| Study and mobile app                | Students using practice features            | A student account on desktop and mobile                      |
| User data and attributes            | Users, administrators and connected systems | Each affected role, plus imports and exports                 |
| Integrations, API and webhooks      | External services and operational workflows | A non-production endpoint and a governed integration account |

### Save and verify

Most pages in Settings use the shared **Save** action in the header. Moving to another page does not necessarily save an edited value. After a portal-wide change, refresh a separate test session and follow the complete user journey; previewing an individual field in the administrator session may not show cached navigation, login or student-facing behaviour.

{% hint style="warning" %}
Keep at least one tested administrator sign-in route while changing registration, single sign-on or Multi-Factor Authentication (MFA). Do not make the live assessment window your first end-to-end test.
{% endhint %}


---

# 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/overview.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.