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

# Sub-portals

Sub-portals let one Synap portal provide distinct experiences for different audiences while remaining connected to the main portal.

Use a sub-portal when an audience needs its own presentation or access context—for example, a customer, cohort, department or programme—without creating a completely separate platform.

Sub-portals are particularly useful when an organisation serves other organisations. They create a clearer separation of audience, presentation and administration than trying to reproduce organisational boundaries with a large set of fine-grained permissions.

### Configuration model

The Sub-portals settings area lists the portal's sub-portal records and provides their configuration controls. The feature is entitlement-dependent; controls are disabled when the **Sub portal** entitlement is unavailable.

Branding can be customised for a sub-portal. When a specific value is not set, the sub-portal inherits the main portal's branding. This inheritance is useful for shared organisation-wide defaults.

Depending on the portal's configuration, a sub-portal can also affect which users, content and administrative context are visible. Treat it as a user journey that needs its own test account, not merely an alternative logo.

| Use a sub-portal when…                                                      | Consider another feature when…                                                               |
| --------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| A customer or partner needs a distinct entry point and branded experience   | Staff inside one organisation simply need different editing responsibilities—use Permissions |
| Audience separation should remain understandable as the platform grows      | Students only need different learning content—use groups, assignments and collections        |
| External administrators should work within a defined organisational context | You only need to record an organisation name—use an Attribute                                |

### Planning considerations

Before adding sub-portals, decide:

* which audiences require separation;
* which settings should inherit from the main portal;
* which branding or access behaviour must differ; and
* who will be responsible for testing each experience.

Treat sub-portals as an information architecture decision, not just a branding shortcut. Too many overlapping audience spaces can make support, navigation and reporting harder to manage.

Before launch, test registration, authentication, navigation, branding, student delivery, staff access, email links and reports from inside the sub-portal. Confirm which settings inherit and who owns future changes.


---

# 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/sub-portals.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.