> ## Documentation Index
> Fetch the complete documentation index at: https://developer.litprotocol.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Dashboard

## Using the Dashboard

The [Dashboard](https://dashboard.chipotle.litprotocol.com/dapps/dashboard/) is a web management GUI for Lit's Chipotle offering. Open it from your browser at

`https://dashboard.chipotle.litprotocol.com/dapps/dashboard/`

It supports light/dark theme for your convenience and provides simple management tools.

**Dashboard workflow (recommended order):**

1. [Request a new account (or log in)](#1-request-a-new-account-or-log-in)
2. [Add funds](#2-add-funds)
3. [Request usage API keys](#3-request-usage-api-keys)
4. [Request new PKPs (wallets)](#4-request-new-pkps-wallets)
5. [Register IPFS CIDs (actions)](#5-register-ipfs-cids-actions)
6. [Create groups](#6-create-groups)
7. [Run lit-actions](#7-run-lit-actions)

### 1. Request a new account (or log in)

On the login page you have two tabs:

* **Existing User** — Paste your account API key and click **Log in**. The server checks that the account exists and is mutable.
* **New User** — Enter an account name and an optional description, then click **Create account**. The server creates the account and displays your new API key and wallet address in a one-time success message. **Copy and store the API key immediately**; it is shown only once and you'll need it to manage the account.

After login, the dashboard shows Overview, Usage API Keys, Groups, IPFS Actions, Wallets, and Action Runner.\
You'll notice a single wallet in your account - it represents your master account API key, and can be used like a standard EVM wallet, or you can safely skip its web3 properties and use the APIs directly.

### 2. Add funds

Running Lit Actions and metered/write management operations (such as creating, updating, or deleting keys, PKPs, groups, or IPFS actions) requires credits. Read-only dashboard and API operations (for example, viewing keys, balances, or usage) are free. Click **Add Funds** in the top-right corner of the Dashboard to purchase credits with a credit card via Stripe. Select a credit package (minimum \$5.00), enter your card details, and click **Pay**. Credits are applied to your account immediately.

See [Pricing](/management/pricing) for credit packages and cost details.

### 3. Request usage API keys

Usage API keys are scoped keys you can give to clients or dApps to run specific lit-actions or to deploy. They can be rotated or removed without changing the main account.

In the **Usage API Keys** section, click **Add**. Set an optional name and description, then click *Confirm*. The server generates a new usage key and displays it in a one-time success message — **copy and store it immediately**, as it will not be shown again. \
\
Use this key in the `X-Api-Key` (or `Authorization: Bearer`) header when calling the node so that usage is attributed to this key.

### 4. Request new PKPs (wallets)

PKPs (Programmable Key Pairs) are wallets the lit-nodes can use for signing. In the **Wallets** section, click **Add** to create a new wallet to assign to one of your users, or for use in running a lit-action. The server generates a new PKP and returns its address and public key.

You can add existing PKPs to groups (see step 6) via **Add PKP to group** in the Groups section.

### 5. Register IPFS CIDs (actions)

To scope which usage API keys can run which code, you register **IPFS CIDs** as permitted actions. In the **IPFS Actions** section, pick a group from the dropdown, then **Add** an action: enter the IPFS CID of the lit-action and optional name/description. The server hashes the CID and stores it in the group. Only keys that are allowed to use that group can run that action.

### 6. Create groups

Groups logically combine PKPs, IPFS actions, and (indirectly) usage API keys. You can use any combination: e.g., a group with only permitted actions, or only permitted wallets, or both.

In the **Groups** section, click **Add** to create a group (name, description, optional permitted actions and PKPs, and flags for "all wallets permitted" / "all actions permitted"). Then:

* Use **IPFS Actions** to add CIDs to the group.
* Use **Add PKP to group** / **Remove PKP from group** to allow which wallets can be used in that group.

Usage API keys (and the account key) are validated against the account's groups and permitted actions/wallets when you run a lit-action.

### 7. Run lit-actions

In the **Action Runner** section, paste some Lit Action JavaScript code and optional JSON parameters. For example

```js theme={null}
async function main({ pkpId }) {
  const wallet = new ethers.Wallet(await Lit.Actions.getPrivateKey({ pkpId }));
  const sig = await wallet.signMessage("Hello from Lit Action");
  return { sig };
}
```

Choose the API key (account or usage key) to use for the request, then click **Execute**. The node runs the action and returns signatures, response, and logs. The key you use must be allowed to run that action (via the group and IPFS CID configuration).

## Daily Usage

The dashboard is just your human-friendly configuration tool. Once your account and keys are set up to your liking, you can simply call the lit-action endpoint with your usage key each time you, your dApp or cron job needs to execute a lit action. So the only daily use step is

1. Call the API with your usage key, action-code ( or IPFS CID ) and any parameters that you need