Feature
Service accounts and PATs
Non-human principals for automation. A PAT carries exactly its service account’s role, in its own organization only.
A service account belongs to one organization and authenticates with a personal access token sent as a bearer token. Chorus stores only a hash of the token and honors its expiry.
With a writer role, a service account can create and change records the way a member can. Records it creates have no record owner.
There is no API route that creates a service account: an operator creates one deliberately.
More features
All features →- 01
Records and domains
A, CNAME, TXT and SRV records under the domains an organization registers, managed in the dashboard or through the API.
- 02
chmod-style permissions
A 9-bit mode on every record and domain: view, edit and delete for the record owner, the organization and everyone else.
- 03
Public directory
An anonymous, searchable listing of published records and domains, through a strict field allowlist.