Pages

Pages are documents you keep in Soma: strategy notes, team agreements, meeting agendas, project briefs, leadership intentions, and other material worth returning to.

They help Soma understand what you are moving toward, the situation you are working in, and what you are designing. You can keep a page private or share it so the people who need it can work from the same material.

What to put in a page

Start with who the page is for:

Private pages hold personal context and work: your intentions, role, reflections, preparation, and projects you are still shaping.
Group pages create shared context for a whole company, department, team, or another group. Use them for information members should understand and work from together.

Within either space, pages commonly cover three kinds of information:

Intention

Describe what you want to move toward and why it matters. A private page might hold a leadership aspiration or a commitment about how you want to show up. A group page might describe a shared direction, desired culture, or outcome.

Context

Record what Soma needs to understand about the situation. Privately, this could include your role, responsibilities, working preferences, or constraints. For a company, department, or team, it could be a strategy, mandate, team charter, operating model, or way of working.

Project

Use a private page for work you are preparing or developing yourself. Use a group page for a shared initiative, such as an organizational change, learning experience, team structure, workshop, or leadership program. Keep the brief, decisions, and related notes together as the work develops.

These are prompts, not page types. A page can combine intention, context, and project details when that is useful.

Create a page

Open Context from the sidebar.
Select New page.
Name the page and choose an icon if useful.
Start writing. Changes save as you work.

Type / in the editor to insert headings, lists, to-do items, quotes, and dividers. Type @ to link to another page.

The details panel shows information about the page, including who created or edited it and who can view it.

Organize pages

Pages live in a tree. You can:

nest a page below another page
drag pages to reorder or move them
bookmark pages you use often
move a page between your private area and an available group
archive a page and restore it later

Use the hierarchy to reflect how readers look for information. A handbook might contain chapters; a project page might contain decisions, meeting notes, and a working brief.

Choose who can access a page

A root page is either:

Private, which means only you can access it; or
assigned to a group, which makes it available according to that group’s membership and page permissions.

Nested pages follow the group of their root page.

Moving a page can change who has access to it. Check the page location and details before moving sensitive material from Private into a group.

Use a page with Soma

There are two direct ways to work with a page:

Mention it in chat

Type @ in the chat composer and select the page. Soma reads the page as part of the request. Mentioning a page is the clearest way to make a specific document relevant to an answer.

Open Soma beside the page

Open the Soma panel from the context editor to discuss the page while you write. You can ask for a critique, develop an outline, or select a passage and ask about that text.

Soma also starts each chat with a short list of the pages you can reach, private and group, with the ones people read most at the top. When a conversation calls for more context, she can find and read other pages you have access to.

Hide a page from Soma

Use Hide from Soma when a page should remain available to you but unavailable to Soma. A hidden page is excluded from page browsing and cannot be read through page tools.

The page remains in its current location and keeps the same human access. This control changes Soma’s access, not the page’s visibility to people.

Current limits

Pages are text-first. Use links for material that lives elsewhere.
Archived pages are removed from the active tree but can be restored.
De-identification and workspace privacy controls also apply to page content.

Chat explains how to mention pages in a message.
Groups controls membership for shared group pages.
Memory provides recalled context rather than a document you maintain.
Privacy explains how sensitive values in pages are stored and shown to Soma.