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

# Registration

Registration settings control whether users can create their own account and how the registration experience is presented.

{% hint style="info" %}
**Location:** Settings → Portal settings → Registration
{% endhint %}

### Sign-up method

* **Open:** users can register with an email address.
* **Closed:** users must be created manually or invited by an administrator.

Closing registration does not remove existing users. Choose the method that matches how access is governed in your organisation.

| If your users…                                                         | Consider                                                                                                          |
| ---------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Should be able to discover the portal and create an account themselves | Open registration, optionally restricted by domain                                                                |
| Must be approved, purchased or assigned before entry                   | Closed registration with invitations, imports or an integration                                                   |
| Enter through an organisation identity provider                        | Registration and Authentication together; do not assume closing local registration disables external provisioning |
| Receive access through an exam voucher                                 | Voucher login and the exam's voucher configuration                                                                |

### Allowed domains

Use the domain allowlist to limit self-registration to approved email domains. This is most useful with open registration. Review consumer email domains carefully; allowing one may make the portal effectively open to a broad audience.

Enter domains without relying on a particular person's address, and test both an allowed and a rejected account. Domain restriction controls who may self-register; it does not change existing accounts or decide which learning content a registered student can access.

### Registration-page content

The registration page can have a custom title, rich-text description, background image, header colour and header border colour. If no custom title is supplied, the portal name is used.

Use the description to tell a new student what the portal is for, who may register and where to get help. Keep essential requirements as text rather than placing them only in the background image.

### Exam voucher login

When the Exam Voucher feature is available, **Exam voucher login** adds a button to the login page. New or existing users can use that route to register or sign in with an exam voucher.

### Related access controls

Registration determines how an account is created; **Authentication** determines how that account signs in. Review both areas together when changing access policy.

After any change, use a private browser session to test registration, confirmation email, first sign-in, required user attributes and the first page the new student sees.


---

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