How can we help?

Profusia is a place for AI-generated documents to live. You connect your AI assistant (Claude, ChatGPT, or anything else that speaks MCP) to Profusia, and it can publish files straight into your workspace — web pages, dashboards, Markdown, code, images, PDFs, Office documents. Published documents get a private URL you can share, they keep a full version history, and they can be arranged into a site with navigation. Pages can be kept up to date automatically with live data. In short: your AI makes something, and instead of a file in a chat window you get a link that stays current.

This answer as its own page

Profusia connects to Claude as a custom connector. You need a Profusia workspace first and your own account in it, with any role. Each person connects their own Claude, and it acts as you: it can do what your role lets you do and see what you can see, and nothing more. In Claude, go to Customize → Connectors, choose + Add, then Add custom connector, and give it your workspace's MCP URL: your workspace's address followed by /mcp, for example https://yourteam.profusia.ai/mcp. On a Claude Team or Enterprise plan, an owner of your Claude organization adds it under Organization settings → Connectors, and each person then connects it from Customize → Connectors. Claude's free plan allows one custom connector. Claude then opens Profusia's approval page on your workspace's own address. Sign in and choose Allow (Profusia uses standard OAuth). Approve only a connection you started yourself. Once it is connected, ask Claude to publish something: "publish this as a page in Profusia" works. Personal settings › Assistants lists what is connected as you, and disconnects it. If you cannot sign in, the approval page also takes a workspace access key, which a workspace owner can issue. A key connects as the whole workspace rather than as a person, so keep it for automation.

This answer as its own page

ChatGPT speaks the same open standard (MCP), so there is nothing extra to set up on Profusia's side. ChatGPT has not yet been tested end to end with Profusia, though. Claude is the recommended way to connect for now. To try it, follow OpenAI's current steps (read from its developer documentation on 11 November 2026): open chatgpt.com/plugins, press the plus button and choose "Add custom MCP server". Give it a name, enter your workspace's MCP URL (your workspace's address followed by /mcp), and choose OAuth when it asks how to authenticate. ChatGPT cannot use a workspace access key. You approve the connection on your workspace's own address, as with Claude: any member can, and it acts as you, with your role and what you can see. Whether you see that option depends on your ChatGPT plan and, in a company account, on what your administrator allows; OpenAI sets those rules and changes them, so check OpenAI's own help if it is missing. ChatGPT asks you to confirm before your assistant changes anything in Profusia. Claude users on every plan can add a custom connector.

This answer as its own page

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.

This answer as its own page

Profusia ships ready-made page templates your assistant fills in: a client status page, a weekly numbers report, and a quote. Say something like "publish a client status page from Profusia's template" — your assistant asks a few questions (the project, the milestones, what's next) and publishes the finished page. The status page and weekly numbers are live: each has a small dataset behind it, so the weekly update refreshes the data (update_dataset) instead of creating a new document, and every link you've shared shows the new numbers. The quote is a snapshot: its prices never change after you send it. You can preview every template, filled with sample data, at profusia.ai/templates. (list_templates / publish_from_template)

This answer as its own page

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.

This answer as its own page

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.

This answer as its own page

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.

This answer as its own page

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.

This answer as its own page

A site presents your documents to readers as a place they can navigate. A site is made of spaces, which nest up to six levels deep. Each space gets an overview page built from what is in it: counts, recent changes, cards for the spaces inside it, and live previews of the documents. You can build a whole site in one call from a template that mirrors your existing folders, then refine it — either by asking your assistant, or by hand in the visual editor. Sites are live; there is no publish button. Whether anyone outside your workspace can see a site depends only on whether a link to it exists. Your sites are in the site menu at the top left, beside the Docs · Projects · Live · Audience switcher: the site's name is the menu. Choose another site there to move to it, or open the site's own pages or its analytics. If there is only one site and you cannot add another, the name is a link home.

This answer as its own page

There are two separate settings. Navigation belongs to the whole site: Sidebar (every space down the left), Top bar (a menu bar with drop-downs and a second row for wherever you are), or Minimal (just the wordmark, with Contents on demand). It is one choice for every page, so navigation stays the same as you move around. Layout belongs to each space: how that page displays what is inside it. The choices are Showcase, File list, Dashboard, Story, Handbook and Shelf. A space inherits its layout from its parent unless you set one; Showcase is the default at the top of a site and File list inside it. Both are in the same menu on the space itself. You can also ask your assistant to set a layout (set_space_shell). To preview without committing, add ?shell=shelf to the URL for a layout, or ?nav=top for navigation.

This answer as its own page

Every document has a comment thread behind the Comments button on its header, and every space has its own discussion for talking about the place rather than a single file. Type @ and a name in a comment to mention someone; it reaches their Notifications. A comment on a document can be pinned to a passage or image: select the text, and your comment points at it. The highlight is drawn over the document; the document itself is never changed. Comments are for signed-in members of the workspace, any role. Someone holding a share link is anonymous, so they see the document but not the discussion. Your assistant can read the comments (read_comments), revise the document based on them, and post a note saying what it changed. Pinned comments include the passage they point at, so "this number is wrong" is actionable. To find a comment, Chat lists every comment across the workspace, with filters (see "Chat — conversations in the workspace").

This answer as its own page

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.

This answer as its own page

Every document can carry three facts of its own: who owns it, what kind of thing it is in your organization's own words (Policy, Proposal, Contract — whatever your workspace calls these), and when somebody should check it is still true. Ask your assistant to set them (set_document_facts, which doesn't create a new version; publish_file and update_file accept them too), or set them yourself in the document panel in Docs, under "About this document". Each box suggests the values your workspace has already used, so a consistent list builds up as you type. Owner is a label only. It doesn't change who can see or edit the document. A review date is kept as you typed it, so "end of Q3" is fine. Only a value Profusia can read as a date counts toward "overdue" on Needs attention, and that finding says how many review dates it couldn't read. Search matches owner and type too, and tells you which one matched.

This answer as its own page

Follow a document to be notified when it changes. The Follow button is on the document panel in Docs, next to Pin. Following is for signed-in members; an assistant can't follow a document. You can only follow a document you can already see, and following it doesn't change what you can see. Only you can see what you follow. When a document you follow gets a new version, it shows up under "For you" in your Notifications (it is not emailed; see "Not available yet"), and Docs also lists the documents you follow that changed this week.

This answer as its own page

A document can carry a state — draft, in review, approved, or superseded — so a reader can tell at a glance whether to rely on it. Ask your assistant to set one (set_document_state), or use the State field in the document panel. The four states are the same in every workspace and can't be renamed, because other people rely on them. A state is a label, not a lock: a document marked "draft" is visible to the same people who could already see it. Checking a document out is different: it does block changes. Ask your assistant to check one out (check_out_document) before you start rewriting it, and nobody else can publish a new version while you hold it; they are told who holds it. Reading, renaming, moving and commenting still work. Release it (check_out_document again, or the Release button on the document panel) as soon as you are done. The panel shows how long a check-out has been held. A check-out belongs to a person, so it works only when your assistant is connected as you (an OAuth connection), not with a workspace access key. An admin can release a check-out if its holder is unavailable.

This answer as its own page

Deleting is reversible. When you delete a file, folder, site, project or dataset it goes to the workspace trash — it stops appearing in listings, and its share links stop working immediately, but it is not gone. You can see what is in the trash (list_trash) and restore it (restore_item). If you delete a folder, restoring it brings back what was inside as a group. Erasing something for good is a separate step (purge_trash) that you have to confirm. Nothing in the trash is erased automatically. Renaming and moving work on anything: files, folders, sites, spaces, projects. In Docs you can act on several documents at once. On the Browse list, tick the box at the left of a row (or press X on the row under the cursor), and Shift-click (or Shift X) to select a range; "Select all" on the bar at the bottom selects every row in view. The bar then offers Move to a folder (type a new name to create that folder), Set state, and Move to the trash, for up to 50 documents at once. Anything that couldn't be done stays selected so you can try again, and a move or a trip to the trash can be undone from the message that follows. "Narrow" beside the filter shows one kind of document, or those updated this week. Each row also has its own ⋯ menu.

This answer as its own page

A document can be backed by a small dataset so its numbers stay fresh without republishing the whole page. The flow: your assistant creates a dataset (create_dataset), binds it to the page (bind_file), and from then on updating the data (update_dataset) updates what the page shows. You can put it on a schedule: Claude can set up a Routine, or ChatGPT a scheduled task, that fetches the numbers from their source and calls update_dataset. Your dashboard then updates every morning without anyone opening it. The Live module (in the switcher at the top of every page) lists every table and what it keeps current. Each table has its own page showing its columns, when it last changed and everything that reads it. Its rows are an editable grid, so you can correct a number by hand. Members with a writer role can also see Connections, the wiring between tables, pages and projects.

This answer as its own page

You can embed a Profusia document into SharePoint, Confluence, Notion, Teams, or an intranet page. Ask your assistant for embed code (get_embed_code). It asks where you are putting it and gives you code to paste. The embedded view shows the document plus a small strip saying what it is, how current it is, and how to get back to the full version. Pasting a plain link into Slack, Teams or Notion also produces a proper preview automatically. Embed access is a separate permission from a share link: forwarding a share link does not let someone embed the document. You can revoke an embed at any time (revoke_embed).

This answer as its own page

Every document you open carries the AI orb — the round button at the bottom right. Where your workspace has in-app AI on, opening it shows an "or take it to" row with everything that takes the document somewhere else. Talk about it: opens Claude or ChatGPT with a prompt about the document already written. The app the document was originally published from is listed first, and if that app has a connector to your workspace the prompt carries the document's id, so your assistant can open the document itself. Work on it in code: opens Claude Code or ChatGPT Codex, with the GitHub repository the document was written in already selected. This shows only for signed-in members of the workspace, and only when your assistant recorded a repository when it published — useful for design notes, runbooks and knowledge-base articles that sit alongside a codebase. You can pick a different repository before you go. An admin can switch these options off for the whole workspace, and anyone can hide them just for themselves from the same drawer. Any assistant: a Copy button that gives you the same prompt to paste into any other AI tool. On a card in Projects, the same orb hands off the card instead — its own prompt, naming that card, once you have it open. Where there is no orb (for someone reading through a share link, or in a workspace with in-app AI switched off), these options are in a menu at the top right of the document. Beside it, an open-in-new-tab icon opens the document on its own, outside the site, ready to copy or print.

This answer as its own page

Profusia can record the moments a project's direction moved — a branch, a pivot, something abandoned — with the reason and links to what it replaced or revised. Your assistant records these as they happen (record_turn), because it is in the conversation where the decision gets made. Publishing a document is not one of these moments; a real change of direction is. Later, get_course reads it all back: what the project is doing now, what was tried and dropped, and drift (documents last written before the direction changed, which may still assume the old plan). If a project has no recorded history, Profusia says so.

This answer as its own page

In the workspace settings (the /console address) there is a Brand screen, for owners and admins. You can set your company name, upload a logo, choose an accent color, write the line people read when they land on your address signed out, and add a footer line for documents you share. Once branding is on, your logo replaces the plain outline mark in your accent color across your sites, on documents shared by link, and on your own sign-in page. The screen shows a preview. Each site can still choose its own color palette on top of this — the brand is the company, the palette is the site.

This answer as its own page

A workspace has four roles: owner, admin, member and viewer. Owners and admins can invite people and manage the workspace; members can create and edit; viewers can read and comment. On a team or business plan a viewer does not take a paid seat: each seat you hold carries five viewers. Making a viewer a member needs a free seat. To invite someone, ask your assistant (invite_member) or use Workspace settings › People. Owners and admins open Workspace settings from their account menu (your picture or initials, top right); see "Workspace settings — where the workspace is run". Registration is invitation-only — you cannot sign yourself up to somebody else's workspace. Where Profusia can send email, an invitation for a named address is emailed to that address, with the workspace and the role. The person who made the invitation also sees the link, in case the email doesn't arrive. An invitation with no address (a link anyone can use once) is never emailed; you pass it on yourself. An invitation your assistant makes is never emailed either: it gives you the link to send, or you can invite the person from People. This stops an assistant from being tricked into inviting a stranger. You can also create groups and use them to narrow who can see a particular document (set_file_audience), which is useful when most of a site is for everyone but a few documents are not. The same narrowing works on a whole space (set_space_audience) — "this whole area is HR-only" — and everything inside it inherits the restriction. Narrowing a space hides the space and its navigation, not the documents in it: a document someone already has a direct link to still opens unless you narrow that document too.

This answer as its own page

Workspace settings is where a workspace is run: who is in it, how it looks, who outside can reach it and what it is allowed to use. Owners and admins open it from their account menu — your picture or initials at the top right — where the row reads "Workspace settings". Members and viewers do not get that row. Writers still reach the parts they use from where they work: Trash from the foot of the Docs side list, and "Place on a site…" from a document. Settings that are only about you (your name, photo, timezone, password, appearance and notifications) are in Personal settings, which everyone has (see "Personal settings — name, photo, timezone, email"). Down the left, the settings are grouped. Content: the Map (where your files sit on your sites), the Library (every file, as a list) and Trash. Administration: People (members, roles, invitations); Usage (what the workspace's AI features have cost); Sharing (what is visible inside the workspace and everything reachable from outside it, with revoke); Brand; AI access; Notifications (the two switches for everyone in the workspace — in the app, and email on a mention); Plan & billing (for everyone: what the plan includes, and this month's usage against each allowance — storage, database space, live-table updates, assistant calls and, where the plan has it, in-app AI — with when each monthly one starts again; only an owner can change the plan there); your projects' settings — statuses, card shapes and what your workspace calls a project; and Google sync where it is available. Sites: each site's own settings, including its share links. Some rows show only for owners and admins. The round "Ask about Profusia" button at the bottom right of this page answers questions about how Profusia works, from this help. It does not read your documents.

This answer as its own page

The main points: Documents are private by default and only reachable with a link you created. Every workspace is served from its own subdomain, so one workspace's content cannot be loaded from another's address even with a valid link. Hosted pages run under a strict security policy: a page can only fetch its own dataset, and Profusia never executes anything from a document on the server. Profusia has no access to your email, your Jira or the rest of your Google Drive, and never asks for it. The one outside credential it can hold is a Google authorization, and only if an owner switches on Google Docs/Sheets sync: it is encrypted, never shown back, and limited by Google to the files Profusia itself creates in your Drive. All tokens and keys are stored hashed, expire where appropriate, and can be revoked. There is a fuller public write-up at /trust, which is the page to send to a security reviewer.

This answer as its own page

Where AI is switched on, two extra things appear. "Ask" on a document answers questions about that one document. "Discuss" on a space answers questions about the work there. It reads the documents, the description of what the space is for, the project's goals and the record of how its direction changed, and tells you which documents it read so you can check the answer. Neither can change anything. They read and answer; they cannot publish, edit, delete or share. Your conversations are kept for 90 days, and only you can see them. You can delete any of them. If you don't see these, your plan doesn't include in-app AI (the Free plan doesn't; a free trial does), or an owner or admin has turned the models off in AI access. Everything else works the same without it.

This answer as its own page

An owner or admin decides which of the AI models available in Profusia the workspace may use, under AI access in the workspace settings. Tick the models you approve; the rest are struck out for everyone. The list can only narrow what Profusia offers; it can't add a model. The same list can be narrowed again for a group, and again for one person. Select any number of groups and people at once and add or remove models for all of them in one move. A person's list can only be a subset of their groups', which can only be a subset of the workspace's. A person given no models gets none. Some models can be asked to think harder. For those, you can hold the workspace, a group or a person to a range of effort — say, medium at most for everyday work — and the range narrows down the same three levels. Each model shows its published price per million tokens, a modelled cost for one everyday answer, and what it has actually cost this workspace this month. You decide whether members see the cost of their own answers, for the whole workspace, a group or a person. When it is shown, every answer in the conversation drawer carries a line saying which model answered and roughly what it cost. When a person has more than one approved model, the drawer lets them pick one, and an effort where the model allows it. A pick outside what they are allowed is refused, not swapped for another model. A model too small to read what the question needs, or one on a provider tier that may train on what it is sent where the workspace has not accepted that, is refused too. The page also offers short, computed recommendations — the cheapest approved model that can read a whole document, where spend is concentrating, where an effort ceiling would save the most — and a market view drawn from OpenRouter's public model list, with links to independent comparisons. These are not benchmarks or quotes.

This answer as its own page

There is a short guide at /skill written for your AI rather than for you. Saving it into Claude or ChatGPT (as a skill, project instruction, or custom instruction) helps your assistant use Profusia well: it asks you less about where things go and records project history properly. It is a public page, so you can hand the link to a colleague without giving them access to anything.

This answer as its own page

Projects is Profusia's work-tracking module, alongside Docs, Live and Audience in the switcher at the top of every page. A project breaks a piece of work into cards — and each project picks its own word for them: steps, features, phases, whatever your team says. A card carries a status from your workspace's own vocabulary (rename them in the workspace settings), can hold documents, a checklist, comments, and fields like Owner, Due, and Priority. The status shows on the documents themselves, everywhere they appear, so a reader knows a page is still exploratory before treating it as decided. Each project also has a description and goals (see "Folders versus Projects"), which are read back to your assistant whenever it publishes into the project. Write them with your assistant, or by hand in the console. With two or more projects, Projects opens on All projects: one row per project, with its status, a progress bar and anything that needs a look (blocked, overdue, due soon, aging). Click a row to look inside that project without leaving the list; right-click for more options. From inside any project, All projects (the first item in the side list) brings you back. With a single project, Projects opens straight into it. A project opens as a live canvas with views including List, Board, Timeline, Map, Flow (what waits on what), Tree (the project as a mind map, folded until you open a branch) and Abacus (each card as a bead on a wire per branch, placed by its status). Nothing reloads as you work. The four-squares button at the end of the row of views ("Choose your views") lets you pick which views appear and in what order, and a project opens on the first one. The first nine also answer to the number keys 1 to 9. On a phone the row of views folds into one button naming the current view; it opens the same list, with hidden views under "Off your bar" and "Choose your views…" at the end. "My work" gathers every card across the workspace whose Owner names you. In Docs, a document attached to a card shows its project and card under its name, with a link to that card. The Documents view inside a project selects documents the same way Docs does: tick the box at the left of a row (or press X), Shift-click (or Shift X) to select a range, and "Select all" to select every row in view. The bar at the bottom then offers Attach to a card, Pull in as cards (one card per document, at the top of the project, named after the document) and Remove from a card, for up to 25 documents at once. Anything that couldn't be done stays selected, and Undo on the message that follows reverses the change. "Narrow" beside the filter shows one kind of document, or those updated this week. Each row also has its own ⋯ menu. A card can repeat on a rhythm (weekly, monthly, quarterly…), a project can be drafted from a plain-language brief and accepted card by card, and any card can be handed to your AI assistant with its documents attached. A project can be exported as Markdown or a spreadsheet, and a read-only link shows an outsider the work's state without the documents. Ask your assistant to "create a project" to start one, or use the New project button on the Projects page. Your workspace can also rename the word itself — see "Folders versus Projects".

This answer as its own page

Every conversation in Profusia is a channel. Some point at a subject — the comments on a document, a space or a card — and some are free-standing rooms your team opens by name. Chat is the page that lists every conversation you can open, with a way to narrow it to channels, comments on documents, comments on cards or comments on spaces. You reach it from "Chat" at the foot of the side list on any screen that has one, or from "Open Chat" at the bottom of your Notifications. Members can talk in any conversation they can open; new channels are opened from the + beside Channels. Type @ and a name to mention someone. It works in channels and in the comments on documents, spaces and cards, and the person sees it under "For you" in their Notifications. If two people in a workspace answer to the same @name, mentioning it reaches neither of them, so use a fuller name. Nothing here is pushed to your phone or computer; the bell shows a count when you look (see "Notifications — the bell and what its number means"). The only thing that reaches you outside Profusia is an email when you are mentioned or named a card's owner, where email is switched on and you haven't turned it off.

This answer as its own page

The bell in the top bar of every screen is your Notifications. Its number counts what is new for you, once each: the things waiting under "For you", plus each conversation under "Messages" that has anything unread. A conversation with five new messages counts once. It shows up to 9+, it goes down as you look, and it leaves out conversations you are not part of and anything you cannot open. It has two tabs, and opens on "For you" when something is waiting there and on "Messages" otherwise. "For you" holds what is addressed to you: an @mention (in a channel, or in the comments on a document, a space or a card), being named a card's Owner, and a new version of a document you follow. Click a row and you land on the thing itself, with the message marked, and the row is marked read. "Messages" holds the conversations you are part of that have something unread: every open channel, plus the comment threads you have written in and the threads on documents you follow. "Open Chat" at the bottom goes to every conversation you can open, including the ones you are not part of. "Mark all read" clears the tab you are on, and it is stored, so the number stays down on your phone and your laptop. What was said before you joined a workspace never shows as unread. If you lose the right to open something, its row says "Something you can no longer open" and shows nothing else. The switches are in Personal settings › Notifications: whether you are notified in the app, and whether you want an email when you are mentioned. Owners and admins also have the same two for everyone in the workspace, under Workspace settings › Notifications; they are a ceiling, so you can turn your own down but never above it. Email goes out only for a mention or for being named a card's owner, and only where email is switched on. A new version of a followed document shows in the bell and is not emailed, and nothing is pushed to a device.

This answer as its own page

Personal settings is yours, whatever your role. Open your account menu (your picture or initials, top right) and choose "Personal settings". It opens where you are, as a window, and each choice saves as you make it. Its sections are Profile, Appearance, Notifications, Password and Assistants. Workspace settings, for owners and admins, is a different room (see "Workspace settings — where the workspace is run"). Profile comes first. Your name, photo and timezone are shown in every workspace you belong to. Name: what other people see beside your comments and messages. Leave it empty and your email address is shown instead. It saves when you leave the box. It can't contain an @ or take over someone else's @mention; if it would, you're asked for another. Photo: choose a picture and Profusia crops it to a square and shrinks it to 256 pixels in your browser, so a large photo is fine. PNG, JPEG and WebP work. Only signed-in people in your workspaces see it (not visitors through a share link, a portal or a read-only project link), and removing it deletes every stored copy. Without one, your initials are shown. Timezone: "Automatic" (your device's own) until you choose one. Times in Profusia are then shown in that zone. It changes only what you see. Email: your email is how you sign in, so changing it needs confirmation. Choose Change, type the new address and your current password, and Profusia sends a confirmation link to the new address. The link works once, lasts 24 hours, and nothing changes until you open it. The old address is told when you ask and again when it is done, with a link that undoes the change for seven days. When it completes, every other browser you were signed in on is signed out, and the old address cannot be claimed by anyone else for 30 days. The reply is the same for every address, so nobody can use it to find out who has an account. This needs email. Where Profusia can't send email, the Change button is replaced by a note saying so. If you sign in through your organisation's provider, your email and your password are managed there. Appearance is the light, dark or automatic choice for this device. Notifications holds your own switches (see "Notifications — the bell and what its number means"). Password changes it and signs out your other browsers. Assistants lists the assistants connected as you in this workspace, each with Disconnect, holds your "Take to AI" choice, and points to where your other choices live. Changing your password also disconnects them.

This answer as its own page

On the sign-in page at your workspace's own address, choose "Forgot your password?", type the address you sign in with, and Profusia emails it a link to choose a new password. The link works once, for an hour, and only at the address you asked from. Asking again sends a new link and the older one stops working. The reply on the page is the same whatever address you type ("If that address signs in here with a password, we're sending it a link"), so nobody can use the page to find out who has an account. It also means the page can't tell you why nothing arrived. If nothing comes within a few minutes, check your spam folder and that you typed the address you sign in with at this workspace. You can ask three times a day for one address; after that, or if nothing arrives, ask an owner or admin of your workspace for a reset link from People. Choosing the new password signs out every browser signed in to your account, in every workspace, and disconnects every assistant you connected (reconnect the ones you use). It signs you in on this browser if this address is still one of your workspaces. Profusia then emails you to say the password was changed. If you didn't change it, reset it again straight away and write to support@profusia.ai. Don't forward the reset email: whoever opens its link can choose a new password. It works only for an account with a Profusia password. If you sign in through your organisation's provider, reset your password there. It also needs email: where Profusia can't send email, the sign-in page doesn't offer it, and an owner or admin issues a reset link from People instead (if you are the only owner, write to support@profusia.ai). The same applies to a workspace opened at profusia.ai/signup until it is on a paid plan: a reset link comes from another owner or from support@profusia.ai. If such a workspace is the only one your account belongs to, the email saying your password was changed goes only to the address confirmed at sign-up (the person who opened the workspace), at most once a day, and asks you to write to support@profusia.ai if it wasn't you. Reset links from an owner or admin are available in every workspace.

This answer as its own page

"Needs attention" catches what falls between Profusia's modules: a project with no documents behind it, a live table nobody reads, a page showing eight-week-old numbers, a document that isn't on any site. It is at the foot of the side list (beside Chat) on every screen that has one; on screens without a side list (Find and the Depth map) it is in the site menu at the top left, under "This site". It lists the items themselves, grouped under your work, your live data and your documents, each a link. A panel on the left lists every finding so you can jump between them. Every member sees the same list; it is not an admin screen. At the foot of the page, under "Analysis", is the Depth Map: your whole library in one picture, showing which areas hold the most and what is aging. Everything here is computed from real activity. A new workspace is told when there isn't enough to show yet.

This answer as its own page

Pin anything you keep coming back to. Your pins are under the pin icon in the top bar of every screen. (On a phone it is the second row of your account menu.) You can pin a document, a project, a single card inside a project, or a live table. They all land in the same short list, grouped by which part of the product they come from, each showing its current name and, where it has one, its current status. To pin something: right-click it in any list — or open the ⋯ menu on its row — and choose Pin. A project has a Pin button on its own header, a document or a card has one in its detail panel, and a document also carries its own pin icon on its own page, beside the pop-out and comments buttons. Unpin from the same places, or from the ✕ on the row in the list. Only you can see your pins; there is no way to pin something for the team. A pin points at the thing itself, so a renamed document shows its new name, and if something is deleted the list says it is gone. Restoring it from the trash brings the pin back.

This answer as its own page

Audience is the fourth module in the switcher: everything reachable from outside the workspace, in one place, each with its own Revoke. Pages lists every outside link (share links, embeds, portals, read-only project links), sorted by how much each one reaches. People shows named portal visitors and recipients. Reach shows whether anyone is looking: opens are counted, but visitors are never identified. You can ask to be told the first time a share link is opened: say so when your assistant makes the link ("tell me when it's opened"). The notice appears once, in Notifications, not by email. Opens are counted and never identified, so it tells you the link was used, not who used it. A portal shares a living part of your site with a customer: one space (or the whole site), read-only and always current. It can be an open link, or a named door where each visitor enters their name — named visitors can be revoked one at a time. On a named door an owner or admin can also let visitors comment: plain-text comments on the documents in the portal, with no account. Each one lands in that document's discussion marked as from a visitor whose name isn't verified, visitors see only their own, and it is off until you switch it on from the portal's row in Audience. Ask your assistant to create one (create_portal), or review and revoke from the Audience module. "See it as…" lets you browse your own site as a visitor, or as one portal's audience, to check what is reachable before you send the link. Nothing can be changed in this view.

This answer as its own page

Find is the compass in the top bar of every screen (on a phone it is the first row of your account menu). It opens one place that can find anything, teach you the product, and answer questions. It used to be called the Navigator. A module's own field — "Search documents", "Search projects", "Search tables" — looks only inside that module. Find looks across all of them at once. Type, and it matches as you type — pages, spaces, documents (including the text inside them), projects, cards, live tables, and the product's own features. Press Enter and you are taken straight there; where it matched text inside a document, the passage is highlighted when you arrive. Guides are short click-through walks — what each module is for, how sharing works, what the AI can do — built from this help, with a "Show me" that takes you to the real page. Where AI is switched on, you can also ask a question in your own words, about the product or about your workspace ("which projects mention the pricing work?"). It reads only what you can already see, tells you which documents it read, and suggests where to go next. Nothing you ask is stored. Without AI, everything else still works.

This answer as its own page

You can export everything. In the workspace settings (the console), the export takes your whole account: every document (every one you can see), each project's work as Markdown, datasets as JSON, site structures, the list of what your projects are for, and the audit log as a spreadsheet — zipped in your browser, so the archive never sits on a server. One project can also be exported on its own — Markdown or CSV — from the Share control on its canvas. Every document can also be downloaded from its own page.

This answer as its own page

What Profusia doesn't do today: There is no published pricing and no self-serve signup — Profusia is in development and workspaces are set up by hand. Single sign-on is built but switched off, pending configuration. Profusia doesn't read your other systems, such as Jira, Salesforce or Google Drive. Your AI assistant already has those connections, so it reads them and publishes the result into Profusia. Email is limited, and only sent where it is switched on. Profusia emails you when someone @mentions you or names you a card's owner (unless you turned that off, or your workspace's owner or admin did for everyone). It also sends the two messages that changing your sign-in email needs: a confirmation link to the new address and a notice to the old one. Those can't be switched off, because they protect your account. It also emails an invitation once to the address it was made for, a password reset link when you ask with "Forgot your password?", and a notice when your password is changed through one. Nothing else is emailed: a new version of a document you follow shows in your Notifications and not in your inbox. There are no push notifications and no digests yet.

This answer as its own page