Glossary
Agreement — the commercial terms for a customer: currency, timezone, term, and optional monthly allowance.
Allowance — a number of hours a retainer agreement covers per month. Hours within it are not billed; the rest is overage.
Audit trail — the append-only log of attributable changes, visible to admins.
Billing period — a customer's month of billable time, priced into segments.
open until closed.
Billing segment — one priced line of a billing period: the covered portion, overage portion, applied rate, and amount for an approved entry.
Billability — whether an entry counts: billable, nonbillable, or
excluded.
Customer — the top of the hierarchy. Owns projects and carries the billing currency and timezone.
Duplicate — a submitted entry flagged as a likely copy of another; advisory only.
Effective date — the date a rate starts applying. Rates are time-versioned.
Excluded — a billability value for time deliberately kept out of billing.
Overage — billable hours in a month beyond the customer's allowance. Billed at the resolved rate.
Personal API token — a bearer token acting as a user, with optional scopes.
Project — a unit of work under a customer. Engineers are assigned to projects and log against them.
Project assignment — the link that lets a specific engineer log against a project.
Rate schedule — an hourly rate for an engineer, optionally overridden per customer or project, effective from a date.
Role — engineer, reviewer, finance, or admin. Enforced server-side.
Scope — a resource:action permission on a token or service client.
Service client — a machine identity that exchanges client credentials for a short-lived access token.
Staging — a non-production instance with synthetic data and an access allowlist.
Reviewer — the role that approves or rejects submitted time.
Submitted — an entry handed to review; appears in the queue.
Voided — a retired time entry, kept but no longer live.