> For the complete documentation index, see [llms.txt](https://documentation.opencrvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencrvs.org/v1.6/setup/2.-gather-requirements/3.2-mapping-offices-and-user-types.md). # 3.2 Mapping offices and user types Now that you have defined your business processes you will need to carefully map the standard office types and users within OpenCRVS to support them. It is important to realise that OpenCRVS supports offices and users in a specific and limited way, as described below. There may be some constraints that you will have to work around or will require some creativity. The best way to map your offices and users is to use the [office / user configuration template](https://docs.google.com/presentation/d/1yni_VJHSqvw0qTIiFjHG3Lnd0fLBKQxKkI8zb8G9cJ0/edit?usp=sharing). The following video show how it can be used. {% embed url="" %} **Key rules for mapping offices and users:** * The civil registration office is the primary administrative unit of civil registration in OpenCRVS. All users will need to be assigned to a civil registration office, whether they work at a local or National level. * Civil registration offices are always mapped to the lowest level of the administrative structure. Again, this is always the case, whether a local office or operating at a regional or national level. * All staff members that play a role in the local civil registration process will need to be assigned to the local civil registration office. It is important to note that a Health Administrator may formally work within a hospital, but if that user acts as a Field Agent within OpenCRVS then they need to be assigned to the relevant civil registration office. This may apply to other offices submitting notifications or declarations into the civil registration process also (e.g. courts, health facilities, local government offices etc.). * Note that some offices may only have an oversight function i.e. they supervise the activities of offices focused on service delivery. * The OpenCRVS standard users have fixed privileges as described in the product specifications section on [users](/v1.6/product-specifications/users.md). You will also get a good feel for what these users are able to do from the [demo of the Farajaland configuration](/v1.6/default-configuration/opencrvs-configuration-in-farajaland.md). For each of the users that you have identified in your business process they need to be assigned to one of the OpenCRVS system roles and assigned to a specific office. --- # 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://documentation.opencrvs.org/v1.6/setup/2.-gather-requirements/3.2-mapping-offices-and-user-types.md?ask=&goal= ``` `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.