Setting the org policy

The organization policy is set by an organization admin with crewdesk policy set, or by the server operator with crewdesk-hub policy set. It takes JSON and replaces the whole policy: what it leaves out takes its default. It applies from the next message.

crewdesk policy                    # read it (everyone can)
crewdesk policy set '{
  "max_mode": "workspace",
  "forbid": ["acme_crm/purge*"],
  "card": ["slack/*"],
  "deploy_card": "all",
  "own_domains": ["example.com"],
  "external": "card",
  "bulk_recipients": 5,
  "turn_writes": 3,
  "day_writes": 200
}'
crewdesk policy set - < policy.json    # or from stdin

Key	Values
max_mode	ask, accept_edits, workspace or free
forbid, card	Patterns app or app/action (* allowed)
deploy_card	production or all
own_domains	The organization's domains (a subdomain is inside)
external	allow, card or forbid for addresses outside own_domains
bulk_recipients	1–1000 (default 10)
turn_writes	0–1000, or leave out for no cap
day_writes	0–100000, or leave out for no cap

How clients follow it

Modes above max_mode are greyed out in the app with a note saying why, and refused in the terminal. A folder that was kept in a higher mode goes down to the highest one allowed. Forbidden actions are refused even after a yes, and the server checks outside addresses itself, after resolving the labels the brain sees.

Every change to the policy is an audit row.