Who can do what

Access to a CTXR site is a matter of keys, not accounts. A key belongs to a person or an agent and carries a small, explicit set of rights. No roles, no groups, no login.

A key and its rights

A key says who it belongs to, what it may do, and the secret that proves it. The “what” is a grid; each cell is granted on its own, none implies another.

  read write remove
content see pages and drafts stage changes drop drafts
templates see the design source change the design drop template drafts
files see images and files upload drop file drafts
the guide see the site’s own notes for the AI write or change a note drop note drafts

Two more rights concern the live site: publish (make drafts live) and take back (return something live to draft). Most keys that publish should never be able to empty the site.

Read-only views are granted separately: the journal, the form inbox, the plan and limits, the list of keys. The inbox holds personal data and is given sparingly.

Changing a template changes what the site does, not only what it says; that right is given rarely — in practice it is the whole site: whoever may write templates can make the site do anything, so it never goes to a key you only half trust. Seeing the design source is a separate, harmless right.

Uploading files looks harmless and mostly is — but a .js or .css file under assets/ that a template loads is code the visitor’s browser runs. A key that may upload files and publish can replace such a file. Give the file right without publish to a key you only half trust, and let someone else publish; or keep script files out of assets/ altogether.

In practice

Key for Rights
Copywriter read and write content, no publish
Intern write content only; cannot see colleagues’ drafts
Design agency read and write templates, no content, no publish
Auditor read everything, write nothing

A request outside a key’s rights is refused and the missing right is named — “this key may write content but not publish it” — so the refusal tells you who to ask.

Handing out keys

The owner’s key may hand out keys, and may allow another key to do the same. Two rules keep this safe:

  • Nobody hands out more than they hold. A key that cannot publish cannot create one that can.
  • Nobody manages beyond their reach. You can only change or revoke keys whose rights fit within your own.

Delegation can go several levels deep without the owner losing the top.

A key is shown once, when it is made; the site keeps only a fingerprint. Lose it and you make a new one. When someone leaves, the owner revokes it; nothing else needs cleaning up.

A person who works in the browser client instead of through an agent needs no key at all. The owner (or anyone who may hand out keys) gives the person an address, and the site mails them a link: it opens the editor for reading, once, within ten minutes. Writing asks a second proof — the code a phone’s authenticator app shows — and the editor sets that up the first time, on the link the owner sent: scan a code, enter the six digits, and from then on it is the code that unlocks writing. A link the person asks for themselves (their address on the door) opens reading only — the first authenticator waits for an invitation, so an address alone never turns into a writer. Reading needs the link (or a key); writing needs the authenticator. A lost phone is the owner’s to reset, on the site itself; a lost link is nothing — ask for a new one. Storing a person’s address is a choice the site makes on their behalf: whoever adds it confirms the person agreed, and the actor file keeps the date of that consent next to the address. Keys stay what they are: for agents.

What a key does not do

It does not identify a person to visitors, create a profile, or expire on its own.

A key is not a Person. Two things that every other CMS folds into “users” are kept apart here. data/person/ is content: who is named on the site — an author, a reviewer, a team member, a speaker — a Schema.org Person, public and crawlable like every entity. .actors/ is access: who may write, a key with rights, never public. The two do not reference each other. A person need not be an actor (a reviewer quoted on a page has no key), and an actor need not be a person (an agent’s key, a role key). When an entity says "author": {"@type": "Person", "identifier": "joey"} it points at data/person/joey.json, not at a key — authorship is a statement about the content, not a permission. Who published it is the journal’s business, and the journal names the actor. Hand keys out with the least rights that do the job, and revoke a key the day someone stops working on the site — or at once if it may have leaked.