What is Playbook?
Playbook is a shared home for an organization's operating knowledge: policies, procedures, reference material, and other published documents. People can browse and search that knowledge in Playbook, and connected AI assistants can retrieve it through the Model Context Protocol (MCP).
Content is organized into Centers and Sections. Documents can be updated directly by authorized editors or proposed as suggestions for human review. Search and AI retrieval use published content that the requesting user is allowed to read.
Getting started
- Ask your organization's Playbook administrator for access, then sign in with the account associated with your invitation.
- If you have access to multiple clients, choose the client you want to work with.
- Browse the content structure, search for a document, or use Ask Playbook to ask a question. Open the cited documents to verify the answer.
- Use the in-app Help content for detailed guidance on writing documents, submitting suggestions, and administering your workspace.
Connect an AI assistant
You need an active Playbook membership and an assistant that supports remote MCP connections with OAuth sign-in. Your assistant provider or organization may limit who can add connections.
- In Playbook, open AI Connections and API Tokens from your account menu and copy the displayed MCP server URL.
- In your assistant's connection settings, add a remote MCP server and paste that URL.
- Follow the sign-in flow and review the Playbook consent screen before approving the connection.
- Ask the assistant to list your available Playbook clients, then name the client you want to use.
A general connection can access your current and future authorized Playbook clients. Each content request selects one client and is checked against your current membership and permissions.
Try a first request
“In our Acme Playbook, find the published employee onboarding procedure and cite the source.”
For a proposed change, try: “Suggest an update to Acme's onboarding procedure to add a first-week check-in. Submit it for review.”
To browse available knowledge, try: “Show the Centers and Sections in Acme's Playbook and the types of documents I can create there.” Replace Acme with the name of a client you can access.
Personal API tokens
For tools that support bearer tokens, you can create a personal API token on the same settings page. Personal tokens are restricted to their original client. Keep tokens private and provide them only through your tool's secure credential settings.
Access and permissions
A connection acts as the signed-in Playbook user. It does not grant administrator access or bypass document access policies. Playbook checks current access when a tool runs.
- Read: search published content, retrieve documents, and browse available structure.
- Suggest: propose documents and changes for human review, and revise your pending proposals.
- Edit: directly create or update and publish documents without the suggestion approval step.
Use suggestion tools when a change should be reviewed. Direct publishing tools require editing permission and should be used only when immediate publication is intended. Ask your administrator to grant only the access appropriate to your work.
Information returned to a connected assistant is also processed by that assistant's provider. Review the Playbook privacy policy and your provider's policies before connecting.
Available tools
list_tenants- List the client names and identifiers available to the authenticated connection.
search_playbook- Search published knowledge within one client and return matching excerpts and document references.
get_document- Read a document by identifier or slug. Assistants should read the full document before giving an authoritative answer.
list_structure- Discover Centers, Sections, and content type guidance before browsing or drafting content.
suggest_new_document·suggest_document_change- Submit a new document or a replacement for an existing document for human review.
suggest_documents- Submit a batch of related document proposals, with individual validation results.
list_my_pending_suggestions·update_suggestion- Find and revise your own pending proposals.
create_document·edit_document- Create or update and publish a document directly when the user has editing permission.
With a general connection, content tools require the intended client's tenant_id from
list_tenants. Searches cover one client at a time. When an answer uses multiple clients,
include the client name with each source citation.
For shorter responses, use top_k to limit search results and include_body=false with
get_document or list_my_pending_suggestions when you only need metadata.
Read the full document before treating it as an authoritative source.
The connector works with Playbook content for the task you request. It does not need your assistant's memory, chat history, conversation summaries, or uploaded files.
For administrators
- Confirm users have active Playbook memberships and the correct content permissions before enabling a connection.
- Review whether users need read, suggest, or direct editing access. Review your assistant platform's approval and tool-execution controls as well as Playbook access policies.
- Use the MCP URL supplied by your Playbook environment. If you need a connection restricted to one client, contact support for the appropriate configuration.
- Review Data & Privacy before enabling optional assistant interaction sharing.
For enterprise-managed authentication or an organization-wide rollout, contact info@gvo.cloud to confirm the supported setup for your assistant platform and identity environment.
Disconnect an assistant
Open AI Connections and API Tokens in Playbook. Under Connected Assistants, revoke the connection you want to remove. Revocation disables that connection's access and refresh credentials. Personal API tokens can be revoked on the same page.
Also remove the connection in your assistant if you no longer want it listed there. Disconnecting does not delete information already returned to the assistant; manage that history with its provider.
Troubleshooting and support
I cannot sign in or see the expected client
Check that you used the invited account and have an active membership. Ask your administrator to verify your access. Older connections or personal tokens may be restricted to one client; a new general connection can discover all your authorized clients.
A document is missing or a tool is denied
Confirm the intended client, that the document is published, and that you have the required access. A connection cannot retrieve restricted content or publish with read-only access.
A connection stops working
Check the MCP URL on your Playbook settings page. A revoked connection must be connected again. Your administrator can also confirm that your membership and workspace remain active.
For help, email info@gvo.cloud with the assistant name, the time of the issue, and the error message. Omit tokens, passwords, and confidential document content.
Use the same address for a security or privacy concern, with “Security report” or “Privacy request” in the subject. Describe the concern without sending credentials or another person's private data.