Agency: client orgs
DIN Agency is the Small Business capacity (90 fields, 30 ops layers) split across up to 5 isolated client orgs, one per client, for $399 a month self-hosted. It is set up with you: Contact us on the pricing page. The org feature it is sold on ships in DIN 1.0.39: the din org commands below.
What an org is
A client org is one client's walled-off part of your install: its own fields, its own reviewers and its own records, apart from every other client's. Each of its fields is a field like any other, with its own store, its own token, its own loopback port and its own console, and a token opens one field and nothing else. One licence manages all of them. main is your own workspace (every field you made before orgs, or with no org current): it is not a client org and does not count against the plan.
The commands (from 1.0.39)
din org new acme # make a client org (Agency: up to 5)
din field new web --org acme # a field in it (or in the current org)
din field new api --org acme
din org use acme # switch: new fields, `din field use` and the default for recall and the console stay inside acme
din org use main # back to your own workspace
din org list # every org, its fields and ops, and your plan's caps (--json for the console)
din org archive acme # stop serving acme's fields; every record is kept
din org restore acme # serve them again
din org ops new site web api --org acme # group 2 or more of one org's fields as an ops
din org ops listWith a client org current, a command never falls back to another client's field or to main, and din field use refuses a field outside the current org. din field route --default never names a client org's field, so a project nobody routed never lands in a client's store. A field never moves between orgs.
The console's Client orgs card shows the same orgs and switches between them.
What the plan allows
The caps come from your signed licence, as the field count does, and din license shows them (client orgs 5 (din org) ops 30 on Agency). Agency includes 5 client orgs; Free includes none.
- Past the org count,
din org newanddin org restoremake nothing, say your plan and how to get more, and exit 3. Orgs that are not archived count; archiving one frees its place, and its records stay. - Past the ops count (fields / 3: 30 on Agency),
din org ops newmakes nothing and exits 3. - Fields are counted over the whole install, every org's together (archived orgs' fields included: their stores are still there). Past the plan's field count
din field newexits 3, as on every plan. - Nothing that exists is ever changed by a cap. An install over its plan (after a downgrade, say) keeps every org, ops and field working and is told so.
- Installs: the licence service refuses a new install past a plan's install count at activation, never an install that already holds the licence. Every paid plan is unlimited today.
An entitlement that does not verify reads as Free, so editing a file unlocks nothing.
Keeping clients apart before 1.0.39
On an older install, keep each client in fields of their own:
din field new acme # a field for one client
din field route acme-site acme # sessions in the project acme-site go to it
din field list # every field, and your plan's allowance
din console --field acme # that client's consoleGive each client's reviewers that field's token only (it is in ~/din/fields/acme/.din/field.token), and they can read and stamp that field and nothing else.