Skip to main content

​
Using the Dashboard

The Dashboard is a web management GUI for Lit’s Chipotle offering. Open it from your browser at https://dashboard.dev.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)
  2. Request usage API keys
  3. Request new PKPs (wallets)
  4. Register IPFS CIDs (actions)
  5. Create groups
  6. 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. 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.

​
3. 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 5) via Add PKP to group in the Groups section.

​
4. 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.

​
5. 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.

​
6. Run lit-actions

In the Action Runner section, paste some Lit Action JavaScript code and optional JSON parameters. For example 
    const message = "Hello from Lit Action";
    const sig = await LitActions.signEcdsa({ toSign: new TextEncoder().encode(message), publicKey, sigName });
    LitActions.setResponse({ response: { message, 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