> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/interoperability/integrations/mosip-crvs-integration/prerequisites-configurations-and-operations/operational-considerations/create-the-default-officer.md).

# Create the Default Officer

### Overview <a href="#id-3.-create-the-default-officer" id="id-3.-create-the-default-officer"></a>

To process the request coming from CRVS, a default officer is to be registered and assigned to the CRVS. The officer is to be added from keycloak by the admin.

* **Log in to Keycloak**
  * Open the Keycloak admin portal.
  * Log in using your admin credentials.
* **Navigate to the Users Section**
  * In the left-hand menu, click on Users.
* **Add a New User**
  * Click on the Add user button to create a new user.
  * Fill in the required fields under the details tab:
    * **Username**: Enter a unique username for the officer (this will become the Officer ID).
    * **First Name**: Enter the officer's first name.
    * **Last Name**: Enter the officer's last name.
* **Set Temporary Password**
  * Under the **Credentials** tab, set the password for the officer.
  * Toggle **Temporary** to **Off** to disable the "temporary password" feature.
  * Click **Set Password**.
* **Enable the User**
  * Under the **User Enabled** section, ensure that the user is **enabled**.
  * Click **Save** to create the user.
* **Assign Roles to the User**
  * Navigate to the **Role Mappings** tab.
  * Under **Available Roles**, select the role **Registration\_officer**.
  * Click the **Add selected** button to assign the role.
* **Finalize the Officer Creation**
  * After saving, the officer's **username** from step 3 will serve as the **Officer ID**.
  * This **Officer ID** will be used in the subsequent create packet API request. Ensure you pass this ID correctly in the request.


---

# 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.mosip.io/1.2.0/interoperability/integrations/mosip-crvs-integration/prerequisites-configurations-and-operations/operational-considerations/create-the-default-officer.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.