Documentation sections

Work

Stop keeping the business in your head

Put current pricing, customer policies, vendor instructions, client briefs, and repeatable checklists in Docs. Your team and connected AI can find the same answer without asking you or digging through old chats and files.

Last reviewed July 14, 2026

In the app Work → Docs

Problems this solves

Start with the recurring problem, then use this feature when its boundary matches the outcome you need.

Problem

Eighteen marketing ideas are stranded in six AI chats

A three-person business creates good campaign ideas with AI, but drafts disappear into old conversations and nobody knows which ones are ready to use.

How this helps

Store each campaign as a Doc with its channel, owner, stage, and planned date. Saved Views can show Draft, Needs Review, and Ready while version history keeps rewrites reviewable.

Problem

Your team sent a quote with an outdated price

A cleaning or rental-management company changes its weekend fee and cancellation terms, but staff keep copying an old email or quote template.

How this helps

Keep one clearly titled Pricing and Policies Doc. Staff and connected AI can find it before drafting a quote, and version history shows exactly when a price or promise changed.

Problem

The new client starts Monday, but delivery got no handoff

An agency closes a client, but the scope, contacts, preferences, and promises are split across sales emails and chat. The delivery team discovers the gaps during kickoff.

How this helps

Keep one typed Client Brief per customer with the owner, kickoff date, package, stage, and next item needed. A saved View can show every upcoming kickoff still missing something.

Problem

The owner gets the same Saturday emergency call every week

A home-services team still calls whenever a customer is locked out, a job runs late, or equipment fails because the answer only lives in the owner’s head.

How this helps

Keep short procedures under Customer Problems, Equipment, and After Hours. Staff can search by situation, and the AI can find the right instructions before escalating what truly needs the owner.

Create and organize a doc

  1. Open Work → Docs and create a document in the root or selected folder.
  2. Give it a title that people and AI can identify without opening it.
  3. Write in the live editor or switch to source mode when exact Markdown is easier.
  4. Assign a Doc Type when structured properties will make the document easier to filter.
  5. Move the doc into the right folder and wait for the editor footer to report Saved.

Automatic saving and conflicts

Edits become visible to other workspace members automatically. The editor first saves an internal draft, then publishes it after about eight seconds without typing and when the editor loses focus or the page is hidden. There is no general Publish or Discard draft button, so finish sensitive edits in a separate document if they must not become visible while you work.

If another person or AI client updates the same doc, SolidActions identifies the newer base and lets you review or resolve the difference instead of silently overwriting it.

Version history

  • Versions preserve the document's revision history.
  • Compare shows changes between revisions.
  • Rollback restores earlier content through a new change without erasing the intervening history.

Search and saved Views

Search finds Docs by text and title. Views are saved filters across folders, titles, dates, and typed properties; if you keep one typed Doc per client, job, property, or campaign, a View can show “clients waiting to start,” “jobs needing approval,” or “property instructions due for review.” People without write permission can still use the Views their workspace provides.

Use Doc Types

Types add a schema and typed properties to Docs. Built-in types are locked. Custom types can be created through the Docs API or MCP, then maintained from the Types screen in the app. Keep type names stable once Views and AI routines depend on them.

Upload existing material

The Docs sidebar accepts uploads and bulk ingestion. Review the resulting title, folder, body, and media links before your team or AI relies on an imported document. Uploading does not keep the external source synchronized automatically.

Current content limits

A Doc body is limited to 1 MiB and an uploaded media item to 20 MiB. Larger source material should be split into focused Docs or linked from its source system. Workspace plan limits can also cap the total number of Docs.

Use Docs with an AI client

  1. Connect the hosted MCP service with Work Use; changes require Work Build.
  2. Ask the AI to find or summarize a named Doc before asking it to edit.
  3. For a change, state whether it should update an existing document or create a new one.
  4. Review consequential changes in the app and use version history when the result is not what you intended.

For example:

Before drafting this quote, find the current Services and Pricing Doc.
Tell me which package, price, and turnaround time apply to a three-location client.
Name the Doc you used and do not invent a service that is not listed.

Everyone with access sees the same Doc.

Put pricing, instructions, policies, and client information here—not passwords or raw provider tokens. Store workflow secrets in Variables and dashboard credentials in Data connections.

Recover deleted content

Deleting a Doc moves it to Trash. Restore it when the removal was accidental. Folder and document controls are permission-aware, so ask a workspace owner when a create, move, or delete action is not available.

Docs are shared within the workspace; the current product does not publish a Doc as a public web page.

Next: turn repeatable team conventions into Crews.