The Graph · Mana docs

The Graph shows who in your organization wrote what, only over what you may read. It has two views: the team map shows it by person and agent, and the topic map shows it by the topics of your organization's list.

See who wrote what

Open Graph and choose By team. People sit on a circle, you first, each with the agents that wrote for them.
Choose an agent or a source to open it in place. A source is what came in with no agent, such as a vault import, whose notes belong to the person who imported it. Beside it, a panel lists its 10 newest elements, and each title opens that element.
Choose a person to open their elements by Library folder, 50 at a time, newest first. Written by filters them by agent.
Open one element to see it with at most 30 neighbours: its earlier versions, the other elements of its Library folder, and its author's other elements.

Graph opens on the view you used last in this browser. The browser keeps it in a cookie, and Mana stores nothing for it.

A solid line between two people counts the elements that both revised. A dotted line beside it counts what one of the two wrote and shared with a team, when the other may read it: the other holds every team of its audience, and their clearance reaches its level. Both count only what you may read.

Under the map, Who knows what gives the counts of every person by Library folder. An element that two people revised counts for both. A ring marks the person who holds the most of a folder, and a tie has no ring. Then a list gives the 12 pairs of people who revised the most elements together, and a second list gives the 12 pairs with the most shared through a team.

What a dotted line tells you, and the limits of the map

A dotted line tells you a little about a teammate, and only through a team that you also hold: that they are in it, that their clearance reaches a level at or below yours, and that their access ended. You never learn that a teammate is in a team that you are not in. A team here is a named team or a branch of your organization's tree, never the whole organization or one person's private space.

A vault note belongs to the person who imported it. What the local command line writes, project records included, sits under the founding admin as the agent Command line. The founding admin is the first person who held the admin role and still holds it. When nobody holds it, these elements sit under you.

The map shows at most 20 people and 6 agents a person. Each person keeps at most 3 dotted lines, and a very large team gets none. The first names come from the sign-in provider, in your browser: Mana stores no name.

Find what the team knows on a topic

Choose By topic. Each topic is a disc sized by its count, with a ring of its writers. Beside each disc sit its families: its largest Library families and vaults, at most 6.
Choose a topic to open it in place: the topic shows its writers, its families, and each of its elements. A large topic draws smaller dots, and past 1,000 elements the map draws the 1,000 nearest (Not yet sorted: the 1,000 newest) and says so. A panel gives its 10 nearest elements (Not yet sorted: its 10 newest).
Choose Open the list to see every element of the topic, 50 at a time, the nearest first. Written by filters it by writer, and the families beside it are counts. What you selected in this topic comes with it.

Each element that you may read goes to its nearest topic when the map opens: the map compares the meaning of the topic's name and sentence with the element. It reads no tag, and Mana stores no label on an element. An element with no vector yet waits in Not yet sorted.

Until an admin saves a list, the map uses the default list of 5 topics: Strategy and decisions, Product and engineering, Customers and market, Operations and tools, and People and organization. A card says whether the list is the default list or a saved one, and how many topics the plan allows: 5 topics on Free, 20 on Pro.

Writers, empty topics, and a part of the set

A writer is the author of the current version of an element. A vault's notes count for its owner, and what the command line writes counts for the founding admin. Topics, under the map, counts each topic for the 6 largest writers. A ring marks the largest writer of a topic, and a tie has no ring.

A topic that holds nothing you may read shows at 0 and opens nothing. With no embedding model ready, every element waits in Not yet sorted, and the map says so. When the Library shows part of the set, the topic map shows the same part.

Summarize what you select

On the list of a person or of a topic, choose from 2 to 20 elements, then Make the summary. On a map:

Select up to 20 nodes. A node is a person, an agent or a source, a topic, Not yet sorted, an element, or a family inside an open agent or topic. There is no mode to enter: a long press on a node puts it in the selection or takes it out.
Read the tray at the foot of the map. It shows each node you selected and what the selection gives.
Choose Summarize. A number on each sentence points at the element it came from.

You cannot select a line between two people. Clear empties the selection. The switch to the other view drops the selection. A list that you open from the map keeps the nodes of its own topic or person, as its elements that Summarize would read.

A selection uses no model call. Only Summarize asks for the summary, at the cost of a summary of the list of a person. As on Search, each summary that reaches the model counts one model call against your plan, and a Graph summary counts toward the same daily limit of summaries.

With a mouse or a pen, a drag on the background of the map draws a rectangle, and the nodes inside it replace the selection; with Shift held, they join it.
On a touch screen, a drag on the background scrolls the page, so use a long press.
Shift-click or Cmd-click (Ctrl-click) puts one node in or takes it out. A plain click still opens the node.
With a keyboard, Space on a node puts it in or takes it out, and Enter opens it.

What a selection reads

A family inside an open topic, and the open agent or topic itself, open nothing, so a plain click or Enter on them puts them in the selection or takes them out. A choice loads no page, and the address keeps the selection, so a reload or a shared link keeps it too.

An element counts as itself. A person or an agent gives its newest elements, a topic its nearest, Not yet sorted its newest, and a family the same, only from that family.

Summarize reads the elements you selected one by one first, then one element from each selected node in turn, up to 20. A node gives only elements you may read, and an element in two nodes counts once.

A summary starts only from a link inside Mana. An address that another site opens, or one that you type, spends no model call. Selecting or summarizing does not play the entrance of the page again.

Change the topic list

In Settings, an admin also sees Topics, which keeps the topic list of the topic map: 5 topics on Free, 20 on Pro. Every member sees the list on the topic map, and only an admin changes it.

Open Settings, and choose Edit the topics on the Topics card. The page shows the count of each topic on your own topic map.
Change a name or a description, change the order, Add a topic, or remove one.
Choose Save the list.

Suggest better topics asks the model for a better list from the current list and the titles that every member may read, never a title that only some members may read. It uses one model call of the plan, and one suggestion a minute for your organization. Use these saves the suggested list at once, and Discard closes it.

Undo the last change brings back the list before the last change. A second undo goes one more change back. Reset to the default list brings back the 5 default topics.

After a change of plan to Free

The map uses the first 5 topics of a longer list and keeps the rest. An undo that would bring back more topics than the plan holds is refused, and the page says why.