> 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.4/setup/4.-functional-configuration.md). # 5. Functional configuration ### Before you start * You must have first completed all the required steps in [Installation](/v1.4/setup/3.-installation.md), particularly: [4.2 Set-up your own, local, country configuration](/v1.4/setup/3.-installation/3.2-set-up-your-own-country-configuration.md) [4.3 Set-up a server-hosted environment](/v1.4/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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://documentation.opencrvs.org/v1.4/setup/4.-functional-configuration.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.