Skip to Content

Docs

Docs is your business knowledge base in Rebased — folders and Markdown documents for SOPs, policies, briefs, meeting notes, client context, and other operating knowledge.

Docs is separate from day-to-day execution and client delivery:

DocsToDo ListJobs
PurposeWhat the business knowsWhat you need to get doneClient work you are delivering
ContentFolders and Markdown pagesFlat lists, tasks, due datesPhases, processes, time, money
Best forSOPs, decisions, briefs, reusable contextInbox, Today, personal checklistsProfitability, invoicing, assigned processes

Use Docs when the content should stay useful over time. Use ToDo when something needs an owner, a due date, or a checkbox. Use Jobs when the work is client delivery with phases, time, and financial links.

Open Docs

  1. In the left navigation, open Docs.
  2. Use the file tree on the left to browse folders and documents.
  3. Select a document to open it in the editor.

On smaller screens, Intelligence can sit as a floating composer at the bottom; on wide screens it can dock beside the Docs editor — same panel behaviour as the rest of Rebased.

Folders and documents

Create a folder

  1. In the Docs tree, choose New Folder.
  2. Name the folder (for example Company Wiki, Client Onboarding, or LinkedIn Strategy).
  3. Optionally nest it under another folder.

Folder visibility controls who can see the documents inside:

VisibilityWho can access
PrivateOnly you
SharedSelected team members (view or edit)
BusinessEveryone in the business

Create a document

  1. Choose New Doc (or create inside a folder).
  2. Open the untitled document and set a clear title.
  3. Write in the document editor — it autosaves as you type.

The Docs editor works like the expanded notes editor on a ToDo task: type directly in a formatted view, select text for headings, bold/italic, bullet and numbered lists, quotes, and links. Content is still stored as Markdown under the hood.

Autosave keeps your working copy up to date without creating a new revision on every keystroke. Meaningful checkpoints still appear in version history. Export a document as Markdown when you need a portable copy.

Version history

Open version history on a document to preview earlier revisions and restore one when you need it. Restoring makes that revision current; it does not silently replace a different document.

Archive and restore

Archive a document from the tree when you no longer want it in the active list. Archived Docs stay available to open and restore — archive is the normal reversible lifecycle, not a permanent delete.

If someone else edited the same Doc

If a save detects that the document changed elsewhere, Rebased protects your local draft and asks you how to resolve the conflict (for example reload the server version or keep your draft). Your unsaved work is not discarded silently.

Organise and maintain

  • Rename folders and documents from the tree.
  • Move documents between folders as your knowledge structure grows.
  • Keep one topic per document so Intelligence can retrieve the right page later.

Uploading into Docs

Use Upload in Docs, or drag files onto the file tree (onto a folder or the tree background for root), when you want a file to become company knowledge.

File typeWhat happens
Markdown (.md)Imports as a new Doc with the content kept verbatim. The original file is kept for provenance.
PDF, Word (DOCX), or imagesOpens an explicit Document Intake review draft so you can check the Markdown before it becomes a Doc.

Imports do not silently overwrite an existing Doc. Replacing or merging into a Doc requires an explicit choice when you confirm the upload.

You can also attach Markdown via the Intelligence paperclip; Document Intake can create a new Doc from it in Autopilot. CSV/PDF chat attachments for bills and row imports remain on the File Uploads path — those are temporary working files unless you deliberately publish through Docs.

If Docs upload is unavailable in your workspace, ask your admin to confirm the latest Docs migrations are applied, or create Docs in the editor / ask Intelligence (Autopilot) to draft Markdown you can paste and save.

Intelligence and Docs

Docs is built so Intelligence can use your business knowledge — not just so humans can store files. Intelligence works as one assistant with specialised skills; Docs work uses the same Intelligence panel, not a separate AI product.

Attach a doc or folder

  • Hover a folder or document in the tree and use the attach control to add it to the Intelligence chat.
  • The panel shows that the folder or document is in context before you send a message.

Ask grounded questions

Once Docs are available to the business, ask questions such as:

  • “What does our client onboarding SOP say about deposits?”
  • “Summarise the setup notes for Bonnetti”
  • “Draft a LinkedIn post using our LinkedIn Strategy folder”

Intelligence should search authorised company Docs (and other permitted sources) rather than guessing. If nothing relevant is found, it should say so.

Product help vs company knowledge

  • Questions about how Rebased works use Rebased’s product documentation.
  • Questions about how your business works use your company Docs, live records, and approved context.

Intelligence also builds a compact automatic Curated Business Context for you (a short per-user summary from Docs and private memories you can already access) on relevant work turns. Attach Docs or ask Intelligence to search when you need specific pages — curated context does not replace full Docs.

Good uses for Docs

  • Company wiki and operating procedures
  • Onboarding guides and handover notes
  • Client or project briefs that Intelligence should reuse
  • Content strategies, brand voice, and campaign notes
  • Decision logs and meeting outcomes you want to keep

For day-to-day checklists and due work, keep using the ToDo List. For client delivery with phases, time, and profitability, use Jobs.

Visibility and privacy

  • Private Docs stay personal within the current business.
  • Shared and Business Docs are available to authorised team members and can contribute to Intelligence context for those users.
  • Other businesses never see your Docs.

Tips

  • Prefer short, specific document titles — they become the headings Intelligence cites.
  • Put reusable knowledge in Docs; leave one-off reminders in ToDo.
  • Attach the relevant folder or document before asking Intelligence for a draft or rewrite.
  • Keep source material (contracts, PDFs) organised; company Docs is the Markdown working copy Intelligence reads.
  • Use version history when you need an earlier wording; use archive when a Doc should leave the active tree but stay recoverable.

Last updated: July 19, 2026

Last updated on