The rule. Assigning asks for someone's attention and lets the two of you message each other, so it follows who is responsible for the node:
Where
Assign or remove others
Assign or remove yourself
Private graph
its owner, and collaborators with write access
the same
Public node
its owners (Root, if nobody owns it)
anyone who can read it
Anyone you assign must be able to read the node.
Who sees the list. On a private graph, everyone on it, read-only collaborators too. On a public node, its owners and the people they assigned. Someone who assigned themselves sees only their own line, and visitors see nothing.
Examples.
Maya invited Mira to her graph Plan and assigns her to a node in it. Mira gets an action item and hears about that node and everything under it. They can now message each other.
Maya tries to assign Olive, who isn't invited: "@olive can't see this node". She invites Olive first.
Maya assigns herself to Entropy. Her AI assistant, working with her token, reads her assignments through the API and picks it up.
Maya owns the public node Energy and assigns Mira to watch its questions. Both see who is on it.
Olive owns nothing under Energy. She can't assign anyone there, but she can click Assign me to follow its work. Only the owners see that she did.
Handles. You can assign someone by any of their handles; the list and their action item show that one. On a public node you own, you assign under the handle that owns it, so nothing ties your handles together.
When access ends. Someone removed from a private graph is taken off its nodes.
How it is built. The node's policy answers two questions, assigning others and assigning yourself; one service decides what each person sees, for the page and the API alike.
**The rule.** Assigning asks for someone's attention and lets the two of you message each other, so it follows who is responsible for the node:
| Where | Assign or remove others | Assign or remove yourself |
|---|---|---|
| Private graph | its owner, and collaborators with write access | the same |
| Public node | its owners (Root, if nobody owns it) | anyone who can read it |
Anyone you assign must be able to read the node.
**Who sees the list.** On a private graph, everyone on it, read-only collaborators too. On a public node, its owners and the people they assigned. Someone who assigned themselves sees only their own line, and visitors see nothing.
**Examples.**
1. Maya invited Mira to her graph *Plan* and assigns her to a node in it. Mira gets an action item and hears about that node and everything under it. They can now message each other.
2. Maya tries to assign Olive, who isn't invited: "@olive can't see this node". She invites Olive first.
3. Maya assigns herself to *Entropy*. Her AI assistant, working with her token, reads her assignments through the API and picks it up.
4. Maya owns the public node *Energy* and assigns Mira to watch its questions. Both see who is on it.
5. Olive owns nothing under *Energy*. She can't assign anyone there, but she can click **Assign me** to follow its work. Only the owners see that she did.
**Handles.** You can assign someone by any of their handles; the list and their action item show that one. On a public node you own, you assign under the handle that owns it, so nothing ties your handles together.
**When access ends.** Someone removed from a private graph is taken off its nodes.
**How it is built.** The node's policy answers two questions, assigning others and assigning yourself; one service decides what each person sees, for the page and the API alike.