Skip to main content
Managing Playbook sources requires the organization Admin role. Sellers can read approved sources; they cannot add, change, approve, or delete them.

​
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 under Team in the left sidebar. Click Add Artifacts → Upload Files to add a file, or Add Artifacts → Notion Page to link Notion content. Use this surface for files. The page has Summary 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. Most 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, PowerPoint, text, HTML, Markdown, spreadsheet, and common image formats.

​
Manage sources in the web app

The Summary tab shows Tempo’s generated summary of your playbook by domain. The Artifacts tab is the searchable source inventory. Each row shows the source’s title, 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.
Admins can edit the source’s domains and subject from the inventory, replace the uploaded file from the preview, or Remove it. Replacing a file restarts processing. The web app shows each source’s approval state. Approval itself is an MCP action today.

​
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 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. Linking is the approval: Notion-linked sources are approved at link time and used as soon as processing completes. If Waiting for first sync stays visible, reconnect Notion or share the selected page with the integration. To remove a linked source, click its unlink control and confirm Unlink. Tempo retires the Playbook documents from that source. Your Notion pages are not changed. Over MCP, the same link and unlink actions are available.

​
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 set a specific perspective as part of the source definition. Set the subject when a source is about a specific entity, such as a named competitor or a product line. It is how Tempo tells two competitor sources apart.

​
Approve it

Processing runs first, then you approve:
Approval is accepted only after processing completes. Until then, the source is not used. Notion-linked sources skip this step.

​
Update a source

This clears approval and restarts processing. The source stops being used until you approve it again. Changing perspective, domains, subject, or title does the same. 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; sellers cannot. If your team says a process question is not answering, check for failed sources first.

​
Delete

This is a soft delete. The source 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. List again to get the current state and reapply.

​
What good coverage looks like

You do not 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. Grounds how Tempo describes your company.