# Setting up your User

By default, when your API service is running locally, it will be accessible on **<http://localhost:9000/api>**. You will also have a Parse dashboard site running at **<http://localhost:9000/parse>**.

The Parse dashboard can be a useful development tool.

### Parse Dashboard Users

In your `API/src/env.json` file, use the `PARSE_DASHBOARD_USERS`env.json variable to configure your parse dashboard.

### PARSE\_DASHBOARD\_USERS var

Object Array container **user**, **pass** key value pairs.&#x20;

```css
...
"PARSE_DASHBOARD_USERS": [
    {
        "user": "admin",
        "pass": "admin"
    }
],
...
```

{% hint style="danger" %}
Don't commit dashboard users to git if you intend to use this file in **production**. Instead, do one of the following:\
\- Supply an environment variable **`PARSE_DASHBOARD_USERS`** containing a JSON string.\
\- Supply an **env.json** file in your production environment by file extension using the environment variable  **ACTINIUM\_ENV\_FILE**
{% endhint %}

### Log In To Parse Dashboard

Visit <http://localhost:9000/parse> to view the Parse Dashboard login:

![Login with username and password specified in PARSE\_DASHBOARD\_USERS](/files/-MdbZrwnZvFl8jng0rER)

{% hint style="danger" %}
The Parse Dashboard provides a very low level "super-user" look at your Parse mongo database! This should only be used by an administrator (or for local development).
{% endhint %}

### Create a Parse User

Once logged into Parse, you should be able to manually create an application user for your API. You can use this to assign a **role** and its associated **capabilities**


---

# Agent Instructions: 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:

```
GET https://docs.reactium.io/actinium/setting-up-your-user.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.