net.wireservice.space.staff
A publication's private newsroom: drafts, editorial comments, staff roles, and stylesheet drafts. Anchored on the publication's DID with space key 'staff'. simplespace config: readPolicy member-list with no members (only the publication account, via the CMS, reads it), appAccess #allowList of the CMS client.
Details · space
| Kind | space |
|---|---|
| Authority | space.wireservice.net |
| Indexed |
Space
space · key literal:staffShown at sign-in
name
stringNewsroom
Collections
collections
array · nsidThe record collections clients of this space type use. A space: scope covers these unless it names its own.
Asking for it
OAuth scopeA client asks for access to spaces of this type with this scope. On its own it covers your own spaces, with any key, and reading, creating, updating and deleting records in the collections above; authority, skey, collection, action and manage narrow or widen that. From the Atproto Spaces proposal (0016).
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
A publication's reader accounts, entitlements, and payments. Contains reader PII. Anchored on the publication's DID with space key 'business'. simplespace config: readPolicy member-list with no members, appAccess #allowList of the CMS client.
-
Gated articles for a publication's paying readers. One space per access tier; the space key names the tier (e.g., 'members'). Each record is a full site.standard.document pointed to by a public net.wireservice.gatedContent stub. simplespace config: readPolicy managing-app with the CMS as managingApp (it answers checkUserAccess from entitlement records), appAccess #open so readers can use any app.
-
The community's management space: feed, label, space, pin, space settings and automod rule records that admins write, and the content warnings written beside the community's labels. Who reads and writes it is the subspace policy's member list, which the community's PDS keeps and publishes as us.off-the-clock.subspace.member records; only the community identity, its admins and the community's services can read it.
-
A staff member's role at the publication, stored in the publication's private staff space. The record key is the staff member's DID, so each person has at most one role.