Glossary

For members, managers and admins

ChronoTab uses a small vocabulary. This page defines each term in one line and links to the page that explains it, so a word you meet on a page or on a client’s screen always has the same meaning. It is for every role.

Term	What it means
Activity type	How the time was spent, for example Development, QA or Meetings. Each organisation has its own list, managed by its org admins. Each type has a label and a short key used in /spend. See Activity types.
Adjustment	A correction to time already on a submitted timesheet. ChronoTab does not offer adjustment entries: to correct submitted time you void the timesheet and log the entry again.
Admin recovery	When an organisation’s only admin has left its GitHub organisation, a GitHub owner who is still a member can take over as admin from a banner. The previous admin’s access ends when they do. See Organisation settings.
API key	A credential a tool uses to act for one person in one organisation. The browser extension uses one. See Your API keys.
Approval	A client’s acceptance of a timesheet. An approved timesheet is final and can only be voided. See Submit, approve, reject or void a timesheet.
Billable	Whether an entry’s time is chargeable and so appears on client-facing timesheets. Non-billable time is still recorded and still shows in Reports. See Generate a timesheet.
Client	The customer the work is for. Repositories are tagged to a client, and a client can approve a shared timesheet without a ChronoTab account. See Clients.
Danger zone	The last section of Settings, where an org admin deletes the organisation. See Delete your organisation.
Deletion grace period	The 30 days after an organisation is scheduled for deletion, before its data is permanently purged. Any admin can cancel during it. See Organisation settings.
Disabled by plan	A member whose seat the plan took back because the team was over its seat limit when the 14 days ended. They can sign in to view their own time but cannot log any. Their entries, reports and timesheets stay, and they return automatically or with Resume or Swap… (the member a Swap disables is disabled by plan too). Not the same as a member an admin disabled. See Seats over the limit.
Draft	A timesheet that has been generated but not sent. Nothing about a draft is fixed and none of its entries are locked. See How timesheets work.
Entry	One record of time against one GitHub issue, with a duration, a work date, an activity type and a billable flag. See My week.
GitHub App	The ChronoTab application you install on a GitHub organisation or personal account so ChronoTab can read its repositories, issues and members. ChronoTab only reads; it never changes your repositories. See Repositories.
History window	The last 60 days of entries that the Free plan shows. Older entries are hidden, not deleted, and come back on any paid plan. See Plans and billing.
Kept repository	A repository an admin has pinned during a plan’s 14-day window, so it stays active when the window ends. See When a repository is paused.
Lock screen	The screen every member of an organisation sees when it is scheduled for deletion. It names the deletion date, and an admin can cancel from it. See Organisation settings.
Manage billing	The link on the Billing page that opens Paddle’s billing page in a new tab, for invoices, receipts and card details. See Payments, invoices and refunds.
Organisation	Your company’s workspace in ChronoTab, with its own members, roles, repositories and settings. Called a team when you belong to more than one. See Switch between teams.
Over the limit	More repositories or seats in use than your plan allows. Nothing is deleted. You have 14 days to choose which repositories and members stay active; after that, the rest are paused or disabled by plan. See Plans and billing.
Past due	A paid plan whose last payment failed. Paddle retries the card, and an admin sees a banner with the date to update it by. See Payments, invoices and refunds.
Paused repository	A repository your plan has no room for. Its history, reports and timesheets stay, but no new time can be logged on it until there is room. See When a repository is paused.
Plan	The package an organisation is on: Free, Starter, Growth, Scale or Contact us. It sets how many repositories and seats the organisation can use, and how much history it sees. See Plans and billing.
Plan grace period	The 14 days an organisation has to choose which repositories and members stay active after it goes over a plan’s limit. Nothing is deleted. See When a repository is paused.
ChronoTab branding	The ChronoTab mark and links that a Free timesheet carries in place of the organisation’s logo and accent colour. See Branding on the Free plan.
Repository	A GitHub repository your organisation tracks. Time is logged against an issue in one. See Repositories.
Rejection	A client sending a submitted timesheet back. Fix the work, then submit again. See How timesheets work.
Role	What a person may see and do: Member, Manager or Org admin. See Roles and permissions.
Scheduled change	A switch to a lower plan, a move to Free or a cancellation that takes effect at the end of your billing period (a switch to a lower plan, within about two hours of it). It can be undone until then. See Upgrade, switch or cancel your plan.
Seat	An active member of an organisation, in any role. Seats count towards the plan’s seat limit. See Plans and billing.
Submission	Sending a timesheet to a client. Submitting locks every entry on it and freezes the document. See Submit, approve, reject or void a timesheet.
Timesheet	The document you send a client to approve: the time for a client, across every repository tagged to it, over one period. See How timesheets work.
Void	Cancelling a timesheet. Voiding releases its entries so they can go on a new timesheet, and keeps the old document as history. See How timesheets work.
Work date	The calendar date the work was done, in your timezone — not the moment the entry was saved. See Duration and date rules.