> For the complete documentation index, see [llms.txt](https://specs.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://specs.govstack.global/overview/23q4/govstack-ui-ux-guidelines/4-design-patterns/5-user-flows/6.1-register.md).

# 4.2.1 Register

Use this pattern to help users provide their personal and relevant information to create an account or profile in a system, platform or service.

## How it works

Registration is useful when you need to give each user a unique identifier in a system or collect their information in one place. This allows users to access, apply for, or meet the requirements for a particular service.

Once a user has been registered, users can log in to their account using their chosen credentials to:

* continue using the service,
* apply for additional services,
* see the services they have used in one place,
* update their information, or
* modify their account settings

<figure><img src="https://1280346931-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3hE0Uutsp0Izues1Vdfb%2Fuploads%2Fgit-blob-7d12970b578da9028b4de2f9af4713419cfe9fb0%2Fimage%20(6).png?alt=media" alt=""><figcaption><p>Patterns to register users to create an account</p></figcaption></figure>

<table data-header-hidden><thead><tr><th width="128"></th><th></th></tr></thead><tbody><tr><td><strong>Steps</strong></td><td><p><strong>Register to a create an account in a system</strong></p><p>Service page > register > get notified of status</p><p><strong>Registered user sign-in to access service</strong></p><p>Sign-in > access service</p><p><strong>Registered user sign-in to apply for service</strong></p><p>Sign-in > eligibility check (if needed) > apply for service > feedback</p></td></tr><tr><td><strong>Patterns</strong></td><td><p><a href="/overview/23q4/govstack-ui-ux-guidelines/4-design-patterns/6-page-templates/7.9-service-sheet.md">Service sheet</a></p><p><a href="/overview/23q4/govstack-ui-ux-guidelines/4-design-patterns/5-user-flows/6.2-authenticate.md">Authentication</a></p><p><a href="/overview/23q4/govstack-ui-ux-guidelines/4-design-patterns/6-page-templates/7.10-asking-users-for-consent.md">Ask users for consent</a></p><p><a href="/overview/23q4/govstack-ui-ux-guidelines/4-design-patterns/6-page-templates/7.12-asking-users-for-information.md">Ask users for information</a></p><p>Uploading documents</p><p><a href="/overview/23q4/govstack-ui-ux-guidelines/4-design-patterns/5-user-flows/6.5-check-a-users-eligibility.md">Eligibility</a></p><p><a href="/overview/23q4/govstack-ui-ux-guidelines/4-design-patterns/6-page-templates/7.14-check-answers.md">Check answers</a></p><p>Pay</p><p><a href="/overview/23q4/govstack-ui-ux-guidelines/4-design-patterns/6-page-templates/7.15-outcome.md">Outcome</a><br>Sending Notifications</p></td></tr><tr><td>Use case example</td><td><a href="https://govstack.gitbook.io/use-cases/readme/inst-1-unconditional-social-cash-transfer#2-registration">Registration for Unconditional Social Cash Transfer</a></td></tr></tbody></table>


---

# 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://specs.govstack.global/overview/23q4/govstack-ui-ux-guidelines/4-design-patterns/5-user-flows/6.1-register.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.