> For the complete documentation index, see [llms.txt](https://docs.kaana.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaana.com/product/planning-and-resources/playbooks.md).

# Playbooks

## Playbooks

Playbooks are step-by-step guides and procedures for common processes and workflows.

### What are Playbooks?

Playbooks provide:

* Documented procedures
* Step-by-step instructions
* Best practice guides
* Standard operating procedures

Unlike blueprints (which are project templates), playbooks are instructional guides.

### Types of Playbooks

#### System Playbooks

Pre-built guides provided by Kaana:

* Common business processes
* Best practice procedures
* Getting started guides

#### My Playbooks

Playbooks you create:

* Custom procedures for your team
* Organization-specific guides
* Lessons learned documentation

### Viewing Playbooks

#### Playbook Library

Navigate to **Playbooks** to browse available guides.

Filter by:

* **System Playbooks** — Provided by Kaana
* **My Playbooks** — Created by you

#### Playbook Content

Open a playbook to see:

* Title and description
* Step-by-step instructions
* Related resources
* Version information

### Using Playbooks

#### Follow a Playbook

{% stepper %}
{% step %}

### Open the playbook

{% endstep %}

{% step %}

### Read through the steps

{% endstep %}

{% step %}

### Follow instructions in order

{% endstep %}

{% step %}

### Reference as needed

{% endstep %}
{% endstepper %}

#### Reference During Work

Keep playbooks handy while working:

* Open in a separate tab
* Print for reference
* Share with team members

### Creating Playbooks

#### New Playbook

{% stepper %}
{% step %}

### Navigate to Playbooks

{% endstep %}

{% step %}

### Click **+ New Playbook**

{% endstep %}

{% step %}

### Enter details

* **Title** — Playbook name
* **Description** — What this covers
* **Content** — Step-by-step instructions
  {% endstep %}

{% step %}

### Click **Create**

{% endstep %}
{% endstepper %}

#### Content Structure

Organize playbook content with:

* Numbered steps
* Section headings
* Bullet points
* Notes and tips

#### Rich Formatting

Playbooks support:

* Bold and italic text
* Headings and subheadings
* Lists (numbered and bulleted)
* Links to resources

### Managing Playbooks

#### Edit Playbooks

{% stepper %}
{% step %}

### Open the playbook

{% endstep %}

{% step %}

### Click **Edit**

{% endstep %}

{% step %}

### Update content

{% endstep %}

{% step %}

### Save changes

{% endstep %}
{% endstepper %}

#### Playbook Versions

Track changes over time:

* View version history
* See who made changes
* Restore previous versions

#### Delete Playbooks

{% stepper %}
{% step %}

### Open the playbook

{% endstep %}

{% step %}

### Click **Delete**

{% endstep %}

{% step %}

### Confirm deletion

{% endstep %}
{% endstepper %}

{% hint style="warning" %}
System playbooks cannot be deleted.
{% endhint %}

### Sharing Playbooks

Playbooks are visible to your organization:

* Team members can view
* Admins can edit
* Share links to specific playbooks

### Best Practices

#### Writing Playbooks

* Use clear, simple language
* Number all steps
* Include all necessary details
* Add screenshots if helpful

#### Organizing Content

* Start with an overview
* Group related steps
* Use consistent formatting
* End with next steps or cleanup

#### Maintaining Playbooks

* Review regularly for accuracy
* Update when processes change
* Archive obsolete playbooks
* Gather feedback from users

#### Playbook Naming

* Use action-oriented titles
* Be specific about the process
* Include scope or context
* Example: "New Client Onboarding Process"


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kaana.com/product/planning-and-resources/playbooks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.