Skip to main content
Managing sources requires the configure_playbook permission.

​
Two ways to manage sources

You can manage Playbook artifacts in the Tempo web app or over MCP from a connected AI platform. Both reach the same sources.
  • Web app — click Playbook in the left sidebar to open /app/dashboard/playbook. Click Add Artifacts → Upload Files to add a source. Use this surface for files — MCP accepts pasted text only. The page has Overview and Artifacts tabs.
  • MCP — describe what you want in plain language. Use this for content you can paste as text, and when an agent is doing the configuring. The rest of this page follows this path, because every step is one prompt.
Each uploaded file can be up to 100 MB. The web app accepts PDF, Word, text, HTML, Markdown, spreadsheet, and common image formats. See Add an uploaded artifact for the exact extensions.

​
Manage sources in the web app

The Overview tab organizes Playbook knowledge by topic. Open a topic to move to Artifacts with that topic applied. The Artifacts tab is the searchable source inventory. Use its topic filters to narrow the list. Each row shows available metadata such as title, source type, domains, subject, summary, and last update.
1

Upload a file

Click Add Artifacts → Upload Files, then select the source file.
2

Wait for processing

Tempo infers a title, summary, and Playbook domains while it processes the file.
3

Review the source

Open the source from Artifacts to preview its content and metadata.
Managers can edit the source’s domains and subject from the inventory. Use the row actions to View or Remove a source. The preview also lets you replace the uploaded file. Replacing a file restarts processing so Tempo can update its extracted content and metadata. To remove a source, choose Remove and confirm Delete artifact?

​
Add a source

Content can be up to 500,000 characters, so full methodology documents are fine. Over MCP you paste content as text. To add a source from a file, use Add Artifacts → Upload Files in the web app instead. Organization admins can link a top-level Notion page or database to Playbook. Tempo imports the accessible pages beneath it as Playbook knowledge and keeps them in sync.
1

Open the Notion source panel

In Playbook, click Add Artifacts → Notion Page. This option appears after an organization admin connects Notion.
2

Choose a page or database

Use Search pages, or paste a Notion URL and click Add.
3

Link the source

Review your selection, then click Link source.
Tempo syncs up to 500 accessible pages beneath one linked source. If Waiting for first sync remains visible, reconnect Notion or share the selected page with the integration. To remove a linked source, click its unlink control and confirm Unlink. Tempo removes the Playbook documents and generated content from that source. Your Notion pages are not changed.

​
Tag it well

Perspective and domains determine when Tempo reaches for a source. Getting them right matters more than the content being perfectly written. The web app infers source metadata during upload. Use MCP when you need to provide a specific perspective as part of the source definition. Set the subject when a source is about a specific entity — a named competitor, a particular product line. It’s how Tempo tells two competitor sources apart.

​
Approve it

Processing runs first, then you approve:
Approve only after processing completes. Until then, the source isn’t used.

​
Update a source

This clears approval and restarts processing. The source stops being used until you approve it again — which is the point. It stops approved content being silently replaced. Same applies to changing perspective, domains, subject, or title. In the web app, open the source preview to replace its file or remove it. Edit domains and subject from the Artifacts inventory.

​
Reprocess

If processing failed, or you think extraction missed something:
Admins can see failed sources; members can’t. If your team says a process question isn’t answering, check for failed sources first.

​
Delete

Soft delete. It stops being used immediately.

​
Concurrent edits

Sources carry a revision. If someone else edits a source between your reading it and writing it, your change is rejected. Re-list to get current state and reapply.

​
What good coverage looks like

You don’t need everything on day one. In rough priority order:
  1. One sales_process source. Unlocks the synthesized process overview and answers the most common questions.
  2. A seller_playbook source. How your team is expected to run deals.
  3. product_reference. Stops Tempo guessing at your capabilities.
  4. Competitor sources, as they come up in real deals.
  5. company_reference with the voice domain. Improves drafts noticeably.