---
title: Projects & project keys | ReplayPilot Docs
description: Organize recordings by site or app, and manage each one’s key.
canonical: https://replaypilot.com/docs/projects
---

# Projects & project keys | ReplayPilot Docs

Search docs…⌘KBrowse docs

Get started
- [Installation](/docs/getting-started)
- [What's new](/docs/whats-new)

Dashboard
- [Replays & the session player](/docs/replays)
- [Errors](/docs/errors)
- [Frustration signals](/docs/frustration)
- [Funnels](/docs/funnels)
- [Releases](/docs/releases)
- [Logs & network requests](/docs/logs)
- [Visitors](/docs/visitors)
- [Heatmaps](/docs/heatmaps)
- [Click map](/docs/click-map)
- [Cohort retention](/docs/cohorts)
- [Projects & project keys](/docs/projects)
- [Alerts](/docs/alerts)
- [Shared links](/docs/shared-links)

Integrations
- [Integrations](/docs/integrations)
- [MCP server](/docs/mcp-server)

Account & data
- [Billing & plans](/docs/billing)
- [Security & masking](/docs/security-masking)
- [Data retention & limits](/docs/retention-limits)
- [Team accounts](/docs/team-accounts)

# Projects & project keys

Organize recordings by site or app, and manage each one’s key.

## What a project is

A project is how you organize recordings by site or app. Run a marketing site and a dashboard app? Give each one its own project. Every list in ReplayPilot (Replays, Errors, Funnels, and the rest) then filters down to one of them.

Creating a project only needs a name. There's no other setup: you get a working project the moment you create it.

The Projects item in the sidebar opens your default project directly, with no separate project-list page in between. Use the searchable selector at the top of the detail page to switch projects.

The **+** button beside the selector opens a create-project modal. Enter the project name and create it, and ReplayPilot routes you straight to the new project's detail page.

## The Overview tab

Open a project and its Overview tab shows you, at a glance:

- Its name.

- How many sessions it's recorded.

- Its error rate.

- When it was last active.

## The Keys tab

Every project has two keys, and both live on its Keys tab.

- **Project key** (pk_live_...): the public key that goes in your recording snippet's data-project attribute. It's safe to put directly in your page's HTML, the same trust model as a Stripe publishable key. See [Install the snippet](/docs/getting-started) for how to use it.

- **Secret key** (sk_live_...): a private key. Never put it in client-side code. It authenticates the [MCP server](/docs/mcp-server) and source map uploads for [Releases](/docs/releases).

You can rotate either key at any time from this tab. The moment you rotate a key, the old one stops working. Key lookups are always live, never cached, so nothing delays the switch.

## The Integrations tab

Connect webhooks, email, and other tools to this specific project. See [Integrations](/docs/integrations) for how each one works.

## The Masking tab

Set per-project mask selectors on their own tab. See [Security & masking](/docs/security-masking) for what masking does. Alert rules live on the separate [Alerts](/docs/alerts) page.

## The Ignored Paths tab

Add exact paths such as /billing or wildcard paths such as /admin/*. For each matching path, choose whether ReplayPilot should exclude sessions, logs, errors, frustration signals, or any combination. Ignoring sessions implies all four exclusions. Query strings and hashes do not affect matching.

Every new project starts with two alert rules already turned on: one for any error, and one for any frustration signal. You don't set these up yourself. See [Alerts](/docs/alerts) to change them or turn them off.

[← Cohort retention](/docs/cohorts)[Alerts →](/docs/alerts)