> ## Documentation Index
> Fetch the complete documentation index at: https://docs.devias.io/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> The docs are served at https://docs.devias.io. Every path in these docs is relative to that root: /llms.txt is https://docs.devias.io/llms.txt.
> Devias is an open-source platform that works as an operating system for a business: a core (records, views, workflows, agents, permissions) with installable modules.
> Pages are typed by folder. concepts/ explains what things are, guides/ gives procedures, reference/ is exhaustive (SDK, CLI, HTTP API), operate/ covers hosting. Use /start/glossary for exact terms.
> Every id in a module (module, object, field, view, action, workflow, step, connection, variable, event, policy) is a uuid. Generate them with `devias id <count>`. Never invent dotted or readable ids.
> Run `devias plan` and read its output before `devias apply`. Apply only what the plan says.
> The OpenAPI document, including the routes of the modules in the reference setup, is at /reference/api/openapi.json.
> Devias is young and changes quickly. If a page and the source repository (github.com/devias-io/devias) disagree, the repository is right.

# Documents

> How to write and discuss documents in the studio. A document is a page of rich text for what does not fit in a field. Covers creating one, the slash menu, @mentions of records, documents and tasks, comments on a passage, the timeline, and where documents show up.

A **document** is a page of rich text for things that do not fit in a field, such as meeting notes, proposals and processes. **Documents** in the sidebar lists them as a gallery, most recently edited first, with a search box at the top.

## Create and write a document

1. Choose **New document**.
2. Type as in any editor. Press `/` to open the slash menu of blocks, such as headings, lists and tables.
3. Type `@` followed by a few letters to mention a record, another document or a task. The mention becomes a link to it.

## Comments

A document has a **Comments** section. A comment can be attached to the whole page or to a passage of text. A comment can be marked resolved when it is dealt with.

## Timeline

A document keeps a timeline of when it was written, who edited it, and the comments added to it.

## Where documents show up

* A task or a record can link to a document.
* A record's page lists the documents and tasks that mention it.
* An agent can read and write documents when its tools allow it.

## Related

* [Tasks](https://docs.devias.io/guides/studio/tasks.md): turn a discussion into work.
* [Use the assistant](https://docs.devias.io/guides/studio/agents.md): ask an agent to draft or summarise.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.