> For the complete documentation index, see [llms.txt](https://invomagic.gitbook.io/ticketsdocs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://invomagic.gitbook.io/ticketsdocs/tools/documents.md).

# Tickets Documents

## What are Tickets Documents

<figure><img src="/files/RBZFmjSfdVWfonnyborC" alt="" width="563"><figcaption><p>Shared Ticket Document</p></figcaption></figure>

Tickets Documents are small document-like embeds you can edit and store at any time, they're also extremely easy to edit by saving that last information you submitted as the default value

### How to create a Tickets Document

{% hint style="info" %}
The Maximum amount of documents you may have at any given time is 22, we're working on expanding this
{% endhint %}

Simply run the `/document create` command and fill out the following options\
\
Name: The name of the document, this is how you'll reference it and it can only contain alpha-numeric characters and is limited to 30 total characters\
Description: This shows up in `/document list` it is used to tell what your document is for at a first glance, it can only contain alpha-numeric characters, periods, spaces, and commas and is limited to 150 characters

### Using a Document

You use documents with the `/document open` command, it will ask for the document name, simply input your document name and it'll open the document like this:

<figure><img src="/files/uY9kfVtNSDxOKgBepTfQ" alt="" width="563"><figcaption></figcaption></figure>

This document may be edited with the two grey buttons\
Edit Title: Edits the Title of the Embed \
Edit Content: Edits the description (content) of the embed.\
\
Markdown is permitted\
Additionally, clicking on the editing buttons will load your current content/title as the default value so you can edit it with ease

<figure><img src="/files/rbWguDH2yKtvyNNu6bAK" alt="" width="375"><figcaption></figcaption></figure>

And if you want to share your document with the world you can click the "Share Document" and it'll post a regular public message of your document!

### List Documents

Documents can be all listed using the `/document list` command, this will list all your documents and their descriptions oldest to newest and in the footer the total Documents you've created

<figure><img src="/files/61eYRPXxLfMZmjv3yoJ7" alt="" width="375"><figcaption></figcaption></figure>

### Delete a Document

{% hint style="danger" %}
This action cannot be undone, proceed with caution
{% endhint %}

Whether you no longer want that document or want to make room for more you can delete it quickly by running the `/document delete` command and providing the name\
When you do so you'll get this

<figure><img src="/files/V9Pjw1YS1rapvXkNyluC" alt="" width="375"><figcaption></figcaption></figure>

Simply Click "Delete Document" after doing so you'll get a popup asking for you to type "Delete my Document" do this exactly, and submit it, it will then delete your document&#x20;

<figure><img src="/files/t26ZOqbWWFn1WWov9jNh" alt=""><figcaption></figcaption></figure>


---

# 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://invomagic.gitbook.io/ticketsdocs/tools/documents.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.
