# Notion

> Use a Notion database as the ticket tracker where the Business Analyst delivers backlogs and the delivery agents pick up their work.

_CommerceCopilot documentation · Integrations_

CommerceCopilot does not replace your ticket tracker; it fills it. Connect Notion and every backlog the Business Analyst produces lands in a Notion database of your choice, formatted the way your team already works. The delivery agents (Project Manager, Tech Lead, Developer, QA) then read and update those same tickets as they progress.

## What CommerceCopilot uses Notion for

- **Ticket delivery.** Confirmed backlogs from [brief-to-ticket runs](/docs/your-first-brief-to-ticket-project) and discovery proposals are created as pages in your chosen database, dependencies included.
- **Ongoing sync.** A webhook watches the connected pages. Edit a ticket in Notion and the change flows back into the project's knowledge base, so agents always work from the current version, not a stale import.

## Connect Notion

1. Go to **Settings** in the sidebar.
2. Find the **Notion** card and click **Connect**.

![The Notion integration card on the Settings page with a Connect button](/docs/integration-notion.png)

3. Notion's authorization screen opens. This step matters: Notion asks you **which pages and databases to share** with CommerceCopilot. Select the database (or the parent page containing it) that you want to use for tickets.
4. Approve, and you are redirected back to Settings.

> **Tip:** if the database you need is not listed later, the most common cause is that it was not shared during this consent step. Reconnect and add it; Notion only exposes what you explicitly share.

## Bind a database to a project

Each project delivers tickets to its own database:

1. Open the project and go to **Settings**, then the **Integrations** section.
2. Under **Project management tool**, choose **Notion**. A project uses either Notion or Jira, not both.
3. In the **Notion Database** card, pick the database from the list.

![A project's integration settings showing the project management tool choice and the Notion database picker](/docs/project-tracker-settings.png)

From now on, everything the Business Analyst proposes or delivers for this project is created in that database. Until a database is connected, the project waits: tickets are held rather than delivered.

## How tickets look in Notion

Each ticket is a full Notion page: title, business requirements, user stories, and dependency references, with status tracked as a property. Your team can edit, comment, and move tickets exactly as they do today. The agents treat Notion as the source of truth and pick up your edits through the webhook sync.

## Troubleshooting

- **The database picker is empty.** The database was not shared with CommerceCopilot during authorization. Reconnect from the Notion card and share it, or share it from inside Notion via the connection's page access settings.
- **Edits in Notion are not reflected.** Sync is webhook-driven and usually lands within seconds. If a specific page seems stuck, a small edit to it re-triggers ingestion.
- **The card shows an error state.** Reconnecting from the Settings card re-authorizes the workspace without losing your per-project database bindings.

## Next steps

- [From brief to tickets](/docs/your-first-brief-to-ticket-project)
- Prefer Jira? See [Jira](/docs/jira)

---
Canonical page: https://www.commercecopilot.ai/fr/docs/notion