# Overview

Spree Studio is the partner-facing console for managing your branded loyalty program on Spree. From Studio you deploy your branded SP token, configure who can mint and hold it, run pSP campaigns, and manage on-chain authority.

Studio is **self-serve.** You deploy and operate your program without Spree intervention in the standard flow. The only inputs Spree provides are the supported chains and the executor service that auto-grants your wallet the operational roles when your deployment completes.

## Where to Access

Production: [studio.spree.finance](https://studio.spree.finance).

Studio supports any RainbowKit-compatible wallet — MetaMask, Rainbow, WalletConnect, and the major hardware wallet integrations.

## Studio vs Dashboard

Studio is the **partner console** — for your team to manage campaigns, treasury, whitelists, and roles.

Dashboard ([dashboard.spree.finance](https://dashboard.spree.finance)) is the **end-user-facing leaderboard view** — for your customers to track their loyalty status and rewards. Different audience, different auth, separate URL. The rest of these docs cover Studio.

## What's in This Section

| Page                                                                             | Purpose                                                              |
| -------------------------------------------------------------------------------- | -------------------------------------------------------------------- |
| [Prerequisites](/spreefinance/spree-studio/prerequisites.md)                     | What you need before signing in                                      |
| [Roles & Access](/spreefinance/spree-studio/roles-and-access.md)                 | Studio account access and the on-chain role model                    |
| [Page Reference](/spreefinance/spree-studio/page-reference.md)                   | One-paragraph description of each Studio page                        |
| [Deploy a Branded Point](/spreefinance/spree-studio/deploy-branded-point.md)     | First-time deploy walkthrough                                        |
| [Whitelist Management](/spreefinance/spree-studio/whitelist-management.md)       | Mint, transfer, redeem allowlists; partner delegation worked example |
| [Authority & Roles](/spreefinance/spree-studio/authority-and-roles.md)           | Granting and revoking on-chain roles                                 |
| [Campaigns & Pending SP](/spreefinance/spree-studio/campaigns-and-pending-sp.md) | Run a campaign end to end                                            |

## Same Operation, Three Ways

Every operational guide in this section ends each procedure with a small table showing the same operation via the Studio UI, the published TypeScript SDK (`@spree-finance/spree-evm-sdk`), and the HTTP API. The three paths produce the same on-chain transaction. Partners can drive operations from the dashboard, from a backend, or from automation infrastructure depending on what suits the team.

## Related

For SDK-level deep dives (full code samples, ABI references, role hex constants), see [Developer Guides → Stable Points (SP)](/spreefinance/developer-guides/stable-points-sp.md). The Studio guides in this section walk through the same operations at the partner-operator level with SDK code as a parallel; the Developer Guides cover the SDK surface in depth.


---

# 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://spree-finance.gitbook.io/spreefinance/spree-studio/studio.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.