summaryrefslogtreecommitdiffstats
path: root/docs/USERGUIDE.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/USERGUIDE.md')
-rw-r--r--docs/USERGUIDE.md14
1 files changed, 9 insertions, 5 deletions
diff --git a/docs/USERGUIDE.md b/docs/USERGUIDE.md
index 1c21c80..09d264e 100644
--- a/docs/USERGUIDE.md
+++ b/docs/USERGUIDE.md
@@ -212,10 +212,14 @@ a browser can open your groups with your passphrase. With it off — the default
an account created in the application — your keys stay on this computer and
nothing of them is left on anybody's node. With it on, the application leaves a
locked copy on each node, as a browser would. The change reaches each group the
-next time it opens. A browser can also be approved from the application for
-itself, group by group: the browser shows a linking code (*Get a linking code*),
-and you enter it in the application under *Your devices on this node*. That gives
-the browser keys of its own without turning browser access on.
+next time it opens. With it off, only the application (and the command-line
+client) opens your groups: a browser keeps no keys between visits, so it cannot be
+linked as a device of its own.
+
+On another computer, the application opens a group with keys of its own once a
+device already linked approves it: the group shows a linking code (*Get a linking
+code*), you enter it on that device under *Your devices on this node*, and the
+group opens by itself.
The application asks in a small window of its own, not in the page, before it
hosts a group on this computer, shares a folder you did not pick in its folder
@@ -1071,7 +1075,7 @@ fresh invitation code.
**"Browser access is off for this account."**
The account keeps its keys in the desktop application. Turn browser access on
-there (Profile), or approve this browser from it.
+there (Profile).
**Video says the codec is not supported.**
The source codec has no decoder in that browser and transcoding is off, or