Part of Stem. This page defines the rpc/type/access-report message type used by the sync RPC specification. Access returns it.

The formal schema is attached as the schemaDefinition of this page.

An explanation of why a principal has, or lacks, access to a scope.

Fields

field	type	required	meaning
`principal`	principal	yes	Who the report is about.
`scope`	data/scope	yes	What it is about.
`level`	data/access-level or null	yes	The live access level, or null for none.
`via`	list of cid	yes	The chain of Grant CIDs, from the owner's grant to the one naming the principal, that gives the level. Empty when the principal is the owner or has no access.
`public`	boolean	yes	Whether the scope's node is readable by everyone.

Rules

via is ordered from the grant signed by the space owner to the grant naming the principal or a group containing it. When several chains give the same level the lexicographically smallest chain of CIDs is reported.

level is null when no live chain exists. A revoked or expired chain gives null even though its grants are held.

public is true when the node's readers include everyone.

Today (HM24)

No equivalent.

Example

{"principal": {"/": {"bytes": "7QEC44…"}}, "scope": {"space": {"/": {"bytes": "7QEA…"}}, "node": "bafyrein6a6wfhym6l3vfz5zfkkibj5j6wjibagi3mnbqnspuq2idw52ijb", "depth": "subtree"}, "level": "read", "via": [{"/": "bafy…g0"}], "public": false}

Fields

Rules

Today (HM24)

Example

See also