People, roles and agents
Invite a finance operator or an accountant, and let an agent prepare work that a person approves.
Roles
| Role | Can |
|---|---|
| Owner | Everything, and the only one who changes the business, the tax policy, access, credentials and a move-in cutover |
| Finance operator | Keep records, import usage, prepare and approve bill runs, record payments and work receivables |
| Accountant | Read and export |
Every page, form, API call and download checks the role itself.
Give someone access
Open More → Access → Give someone access with their name, email and role, and press Invite. They sign in with their email. End access ends their access and every session they hold.
Agent credentials
Under Agent credentials, the owner issues a credential with a name and scopes:
- prepare: read records and propose work for approval.
- usage: submit usage events.
The key is shown once; Nectar keeps only its fingerprint. Send it as
Authorization: Bearer … to /api/nectar/. Revoke ends it immediately.
A credential never approves, finalises, issues a credit, changes a record directly or manages access.
Proposals
With prepare, an agent proposes:
- Contract terms from a signed agreement, quoting each clause and flagging anything ambiguous.
- A price change for selected subscriptions from an exact date.
- A usage correction to a draft bill run, with its sources.
- A collections reminder.
Nectar computes each proposal's effect on invoices itself. Open More → Proposals to read it, then Approve or Reject. A proposal whose records changed after it was prepared cannot be approved; ask for a new one. Approving a usage correction prepares the draft run again; its invoices still need their own approval.