> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/remote-configs/create-remote-config-parameter.md).

# Create Remote Config Parameter

{% hint style="info" %}
Note

**Remote Config parameters can be created separately for the Production Environment and Development Environment.**
{% endhint %}

## Remote Config List

![Remote Config list in use](https://143363954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyAVlNQhS253reum0Ce94%2Fuploads%2Fgit-blob-22dc1968999b34b0a934bad84ec22ba048353c88%2F3656e1f-Remote_Config___List_page_-__c7bc0ad9880421c1.png?alt=media)

The Remote Config list is as follows:

1. Lists for the Production Environment and Development Environment are managed separately.
2. By default, you can view the list of active parameters.
3. Clicking an individual parameter key navigates to the detail screen for that parameter.

## Remote Config List Details

![](https://143363954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyAVlNQhS253reum0Ce94%2Fuploads%2Fgit-blob-b7e4df1a6f67dc0db47972645e22124838723583%2F3d376de-Screen_Shot_2022-11-22_at_7.05.4_10b6332d6e303528.png?alt=media)

1. Active Parameters: Click the dropdown menu at the top of the list to switch between the **`Active Parameters`** and **`Archived Parameters`** lists.
2. Type: View the type of the parameter key.
3. Created Date: The date on which the parameter key was created.

Up to 10 active parameters can be used simultaneously. Archive parameters that are no longer in use.

## Creating a New Parameter

Click the **`+ Create New Parameter`** button in the upper right to create a parameter and start using Remote Config.

![Create Parameter button](https://143363954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyAVlNQhS253reum0Ce94%2Fuploads%2Fgit-blob-82e5ccef00a84e7a9292f6312e5f60b671b696ac%2F6d1dd32-Screen_Shot_2022-11-22_at_7.09.5_d9b946e380411afd.png?alt=media)

### Entering Information

![Create Parameter](https://143363954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyAVlNQhS253reum0Ce94%2Fuploads%2Fgit-blob-5e2b09328c8b3af3e9d4b1f3f2ccd68ceede4023%2F707de75-Screen_Shot_2022-11-22_at_7.15.4_5fc6d159a1cd66cb.png?alt=media)

<table><thead><tr><th width="125.12109375">Field</th><th width="249.6328125">Condition</th><th>Description</th></tr></thead><tbody><tr><td><strong>Parameter Key</strong></td><td>Required</td><td>Only letters, numbers, <code>_</code>, <code>-</code>, and <code>.</code> are allowed<br>Length limit: 1–128 characters<br>Must be unique within the same Remote Config</td></tr><tr><td><strong>Parameter Description</strong></td><td>Optional</td><td>If the name alone does not convey enough information, it is a good idea to add a description.</td></tr><tr><td><strong>Parameter Type</strong></td><td><code>String</code> <code>Number</code> <code>Boolean</code> <code>JSON</code></td><td>Select a parameter type to configure its value.</td></tr></tbody></table>


---

# 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.hackle.io/en/remote-configs/create-remote-config-parameter.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.
