> 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.3/setup/4.-functional-configuration.md).

# 4. Functional configuration

### Before you start

* You must have first completed all the required steps in [Installation](/v1.3/setup/3.-installation.md), particularly: 

[3.2 Set-up your own country configuration](/v1.3/setup/3.-installation/3.2-set-up-your-own-country-configuration.md)

[3.3 Set-up a server-hosted environment](/v1.3/setup/3.-installation/3.3-set-up-a-server-hosted-environment.md)

* Only a National System Admin can configure these settings
* They are provisioned independently for every environment you are hosting: Staging, QA & Production.  You may want to make a new factory reset backup when you are finished to make it easier to deploy to new environments. 

This section introduces the configuration steps that your National System Admin will be required to do:  

1. Configure the application settings
2. Configure registration time periods and fees
3. Create system users


---

# 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.3/setup/4.-functional-configuration.md?ask=<question>&goal=<endgoal>
```

`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.