> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/end-user-guide-for-selfservice/signing-in/self-registration.md).

# Registering yourself

Register yourself for an account when your organization offers self-registration.

Most people never need this page: your account is created for you when you join, and you simply sign in. Some organizations, though, let certain people — contractors, partners, students, visitors — register themselves and wait for approval.

If your organization does not offer this, there is no registration link on the sign-in page. That is normal.

## Registering

{% stepper %}
{% step %}
**Choose the registration link on the sign-in page.**

The wording is set by your organization — commonly *Register*, *Sign up*, or *Request an account*.
{% endstep %}

{% step %}
**Fill in the form.**

You are asked for your details — typically name, email address, and whatever else your organization needs to identify you. Required fields are marked; the form will not submit until they are complete.

Some organizations split this across several steps, and may ask you to set a password or answer security questions as part of it.
{% endstep %}

{% step %}
**Submit, and note your request number.**

You see a confirmation like:

> *"Credentials saved. Your account awaits approval after which your username and password will be sent to you. Your request ID is …"*

Keep that request number. It identifies your registration if you need to chase it up.
{% endstep %}

{% step %}
**Wait for approval.**

Registering does not create an account immediately — it creates a **request** that a person has to approve. Until someone approves it, you cannot sign in.
{% endstep %}

{% step %}
**Receive your sign-in details.**

Once approved, your user name and password are sent to the email address you registered with. From then on you sign in normally.
{% endstep %}
{% endstepper %}

## What to expect

* **Approval takes as long as it takes.** It depends on who has to approve it and how quickly they work. There is no way to speed it up from this page.
* **Check your spam folder** when you are expecting the credentials email.
* **Nothing arrives at all?** The registration may have been rejected, or the email address may have been mistyped. Contact whoever sponsored your access — your manager, your client contact, or the help desk.

{% hint style="info" %}
If you already have an account and simply cannot get in, don't register a second time — that creates a duplicate that has to be cleaned up. Use [If you forgot your password](/end-user-guide-for-selfservice/signing-in/forgot-password.md) or [If you forgot your user name](/end-user-guide-for-selfservice/signing-in/forgot-username.md) instead.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openiam.com/end-user-guide-for-selfservice/signing-in/self-registration.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.