> For the complete documentation index, see [llms.txt](https://docs.keycloakify.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keycloakify.dev/page-specific-guides/registration-page.md).
# Registration Page
Angular
The register page can be customized in Angular. As soon as you run `npx keycloakify eject-page` and pick the register page all its sub components are also ejected into your project:\
.png?alt=media)
In this video, I explain how to customize the register page of Keycloak, both at the Keycloak configuration level and at the theme level.
{% embed url="" %}
## Timestamps
* [01:28](https://www.youtube.com/watch?v=lMOLrdqilqE\&t=88s) - User Profile Attributes Configuration
* [11:05](https://www.youtube.com/watch?v=lMOLrdqilqE\&t=665s) - Password Policies Configuration
* [13:27](https://www.youtube.com/watch?v=lMOLrdqilqE\&t=807s) - Email Domain Accept List
* [15:10](https://www.youtube.com/watch?v=lMOLrdqilqE\&t=910s) - Adding Custom User Attributes to the JWT of the ID and Access Token
* [16:31](https://www.youtube.com/watch?v=lMOLrdqilqE\&t=991s) - Exporting the Realm Configuration
* [19:14](https://www.youtube.com/watch?v=lMOLrdqilqE\&t=1154s) - Creating Storybook Stories for the Register Page
* [23:53](https://www.youtube.com/watch?v=lMOLrdqilqE\&t=1433s) Customizing the Register Page with CSS
* [26:35](https://www.youtube.com/watch?v=lMOLrdqilqE\&t=1595s) - Customizing the Register Page with React
---
# 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://docs.keycloakify.dev/page-specific-guides/registration-page.md?ask=&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.