Writing Documents

Documents in Saltare are markdown-powered collaborative files where humans and AI agents work side-by-side. They support version history, discussion threads, embeddable cross-references to any workspace object, and agent-powered content creation.

Creating Documents

From the Sidebar

1. Navigate to a document group in the sidebar
2. Click New Document
3. Enter a title and start writing

From Chat

Ask an agent to create a document:

@Assistant create a document titled "API Integration Guide" 
with sections for authentication, endpoints, and error handling

The agent will create the document, write the initial content, and share a link in the thread.

The Editor

The document editor uses Markdown — a simple formatting syntax that lets you write structured content without a complex toolbar.

Basic Formatting

• **bold** for bold text
• *italic* for italic text
• ~~strikethrough~~ for strikethrough
• `code` for inline code

Structure

• # Heading 1 through ###### Heading 6 for headings
• - or * for bullet lists
• 1. for numbered lists
• > for blockquotes
• --- for horizontal rules

Code Blocks

Wrap code in triple backticks for syntax-highlighted code blocks:

```python
def hello():
    print("Hello, world!")
```

Tables

Use pipes and dashes for tables:

| Column 1 | Column 2 |
|----------|----------|
| Data     | Data     |

Live Preview

Toggle between edit and preview modes to see your rendered markdown in real-time. The preview matches exactly what other users will see.

Embeds — Link Anything in Your Workspace

Use double-bracket syntax to embed references to any workspace object:

See [[doc:project-overview]] for background context.
Check [[task:deploy-api-v2]] for the current status.
Discuss in [[channel:engineering]].

Supported Types

Syntax	What it links
[[doc:slug]]	Document
[[task:slug]]	Task
[[channel:slug]]	Channel
[[project:slug]]	Project
[[db:slug]]	Database
[[agent:slug]]	Agent

Inline embeds render as compact chips showing the object's title, state, and status.

Block Embeds

Prefix with ! to render a rich card instead of an inline chip:

![[task:deploy-api-v2]]

Block embeds show full details — task state, priority, assignee, labels, due date — as a visual card within your document.

Embed Picker

Type [[ in the editor to open the embed picker in the preview panel. Search across all workspace objects, then select to insert the correct syntax. No need to remember slugs.

Backlinks

Embeds are tracked automatically. Every embedded object knows which documents, messages, and tasks reference it — visible in the "Referenced by" section on document pages.

Version History

Every save creates a version snapshot. You can:

• View the full history of changes
• Compare versions to see what changed
• Restore any previous version with one click

Version history is automatic — no manual saving required.

Organizing Documents

Documents live in the unified Data tree alongside projects, databases, and channels:

• Organize documents into folders with drag-and-drop
• Each folder can have a context annotation describing its purpose
• Documents appear in the sidebar under the Data section
• Navigate via breadcrumbs or the command palette (Cmd+K)

Collaboration

Discussion Threads

Every document has an auto-created discussion channel. Use it to:
- Discuss changes with your team
- Ask agents to review or update content
- Leave feedback without modifying the document itself

Collaborator Tracking

Saltare tracks who has edited each document, so you always know who contributed.

Agent Co-Authoring

AI agents can create, read, update, and search documents. Common workflows:

Agent-Written Research

@Researcher analyze our top 5 competitors and write a 
comparison document with pricing, features, and market position

Agent Editing

@Writer review the "Q2 Report" document and improve 
the executive summary section. Make it more concise.

Agent Document Search

@Assistant find all documents that mention "API migration" 
and summarize the key decisions

Publishing

Documents can be published to make them more prominently visible within the workspace. Published documents signal that the content is finalized and ready for reference.

Tips

• Start with structure — Write headings first, then fill in content. This makes it easy for agents to update specific sections.
• Embed liberally — Use [[doc:slug]] and [[task:slug]] to cross-reference related items. This builds a navigable knowledge graph across your workspace.
• Use block embeds for context — Drop ![[task:launch-checklist]] into a document to show a live task card so readers see current status without leaving the page.
• Leverage agents for first drafts — Let an agent write the initial structure, then refine it yourself. Agents can use embed syntax in their output too.
• Keep discussions in the thread — Use the document's discussion channel for feedback rather than editing comments directly into the body.