Guides · Docs — publish, write, share
Docs — publish, write, share
Getting documents in, and getting them safely out.
How does a document get here?
Ask your assistant to publish. For example: "publish this report to Profusia" or "put this dashboard in Profusia under the Client Work folder".
Your assistant writes the file and sends it. You get back a link and the folder it landed in.
You can publish HTML pages, JSX (which Profusia compiles in the browser — no build step), Markdown, code files, images, PDFs, and Office documents. Anything Profusia can render becomes a live page; anything it can't becomes a clean download.
Word, PowerPoint and Excel files are searchable by their contents, so they show up in search and can be asked about like any other document. A PDF is matched by name only, and Profusia tells you so.
Can I write one myself, without an assistant?
You do not need an assistant for everything. On any site, the Add button (and the + beside any space in the navigation) offers "Write a document".
It is a normal rich-text editor, so you never see Markdown syntax. Paste from Word or a web page and supported formatting is kept. You can drop pictures straight in.
The document is stored as Markdown, so your assistant can pick it back up later and revise it.
Occasionally a document opens as Markdown source instead, with a line explaining why. That happens when it contains something the visual editor can't keep intact, such as a table or a nested list. The toolbar has a Markdown / Rich text switch either way.
To edit a document that already exists, open it and use Edit.
What about a file I already have?
If the file already exists (on your computer or phone, exported from another app, or attached to a chat), don't have your assistant retype it. Ask for an upload link.
Your assistant can call get_upload_link, which gives you a private drag-and-drop page. Drop in a file of any type and it lands in your workspace. This is much faster than streaming a large file through a conversation.
You can also drop a whole folder, or choose one with the folder picker. Its folder structure is kept.
Who can see a document?
Every document is private by default. Nobody can see it until you create a share link.
Ask your assistant for a share link (get_share_link) and you get a URL with a secret token in it. Anyone with that link can view the document — treat it like a key. Share links can be set to expire, and they can be revoked and reissued at any time.
A share link can also require a password. It protects against accidents, such as a reply-all or a link sent to the wrong person; it does not stop someone forwarding the link and the password together. Ask for a password when you get the link, and send it separately from the link (in a different message or channel). Passwords are stored hashed and can't be shown again, even to you. If one is lost, create a new link with a new password.
To open your own documents you don't need a share link: sign in and open them from your site.
A sharing review (review_sharing) lists every live link in your workspace, so you can see what is reachable from outside.
What if something gets overwritten?
Every time a document is updated, Profusia keeps the previous version. Nothing is overwritten.
To go back, ask your assistant to roll the file back (rollback_file) to an earlier version, or do it yourself: open the document in Docs, and its panel has a Version history section listing every version with its date, who made it and any note they left. Press Restore — it asks you to confirm with a second press, then makes that version current.
Restoring never deletes anything: the version you were on stays in the list, so a restore can itself be undone. The share link doesn't change, so anyone holding it sees the restored content.
Folders and Projects — what's the difference?
A folder is where a file lives. Each file is in one folder.
A project is what a file is for. (Your workspace can call projects something else, such as Initiatives or Campaigns.) Projects can nest, a file can belong to one, and each project has a description and goals.
Those goals are read back to your assistant whenever it publishes into the project or lists what is in it, so a session next month knows what the project is for without you explaining it again.
In the Projects module (see "Projects — tracking the work behind the documents"), starting a project sets up its description and goals automatically, so its cards and its purpose live together from day one.