docs: a member's entry, as the rules have it

Review 1.3: access.md said a user who may write _continuum/members may
only remove another member's entry, but the rule lets them write any of
it (addresses, dashboard). Those are operators, who may set an entry
right through the store, so the doc now says what the rule does.

1 files changed, 4 insertions, 3 deletions

diff --git a/docs/access.md b/docs/access.md
index 093ebaf..025f47b 100644
--- a/docs/access.md
+++ b/docs/access.md
@@ -219,9 +219,10 @@ revocation since refuses nothing it allowed then, and every node judges alike. O
 written before the policy (at its dependencies) is judged by none: history from before
 stays as it is, wherever it comes from later (a joining node catching up, say).
 
-* A member's entry (`_continuum/members/<id>`) and its votes are written by that member
-  only; removing an entry, also by a user who may write there, or who forgets the
-  member in the same change (`DELETE /peers/{pk}`, with `_continuum/forgotten`).
+* A member's entry (`_continuum/members/<id>`) is written by that member, and by a user
+  who may write there, all of it (an operator, through the store, setting addresses or
+  the dashboard right); removed also by one who forgets the member in the same change (`DELETE
+  /peers/{pk}`, with `_continuum/forgotten`). Its votes by that member only.
 * Epochs and the swarm ID (`_continuum/epochs`, `_continuum/swarm`) by an epoch's first
   change only (the genesis change, a remake's snapshot).
 * A remake's record and its proposal by whichever member proposes, where there are