DNA: started from private-graphs.md

Root ·

Started from docs/dna/private-graphs.md in the Knowen repository: How Knowen works is kept with the code.

Changes to the content

# Private graphs
⏎
**What they are.** A private graph is a node of yours and everything under it. It belongs to you, and to collaborators you invite: give each **Read & write** (the default) or **Read only** access, from **Collaborators** on any of its nodes. Collaborators with write access edit freely: in a private graph nobody needs approval. Read-only collaborators read and comment, in the app and through the API alike.
⏎
**Where to find them.** **New private graph** on the **Private graphs** page starts one: its first node goes under your private root. **Graph view** there shows your graphs and the public graph's top level as one graph. The page lists the graphs you own or work on, with what each one is: a fork of public nodes, attached to the public graph, attached to another private graph, or read-only because someone attached it to a graph you read. Each row shows its owners: who started it and who can change it, the first two by name and then "+2".
⏎
**Sharing.** A **shared link** lets anyone read one node without an account, until you turn it off in Settings › Shared links. Attaching a graph to another private graph lets that graph's readers read it, read-only (see [Attach](dna:attach)).
⏎
**How it is built.** Each node records the private graph it belongs to; permissions are kept on the graph's top node and apply to the whole graph. Every page, search and API call checks them.
⏎
**Limits.** Access is for a whole graph, not for single nodes in it. Your plan sets how many private nodes you can have (during the beta, 500).
⏎
# Parents
⏎
* Private and public⏎

Feedback00

No feedback yet. Say whether this change improves the node.

Sign in to add a new comment.