Company

Company Info

The Company Info page is the central hub for managing your organisation's profile inside TeamTrackin. From here, admins can update the company name, address, contact details, leave allowances, and website URL.

Brand Assets

The Brand Assets section lets you upload your company logo and stamp. These images are used automatically on invoices, payslips, reports, and official documents generated by TeamTrackin.

Basic Information

The Basic Information section stores your company's official registration details. These fields are used on all legally generated documents.

HR & Web Settings

Controls the annual leave entitlement for all employees and your company's public website URL.

Company Timeoffs

The Company Timeoffs page is where admins manage company-wide public holidays and office closures. TeamTrackin supports four holiday categories — National, Optional, Company, and Regional.

User Overtime

The User Overtime page is where admins review and manage all overtime requests. Each request includes the employee, the day worked, hours, amount, type, and description. Use the Pending / Approved / Rejected / All tabs, the employee and day-worked filters, and search to narrow the list.

Approving and rejecting

Approving fixes the hourly rate, multiplier and amount, so later changes to pay or multipliers never change approved overtime. It is then added to the employee's next timesheet. Rejecting needs a reason, which the employee sees on their overtime page and gets by email. You can't review your own overtime, and overtime that is already on a submitted timesheet is locked.

Overtime pay multipliers

Click Pay settings and switch on Pay overtime at a premiumto have TeamTrackin price every request as hours × the employee's hourly rate × the multiplier for the day worked — for example 3h × £12.00 × 2.0 (Saturday) = £72.00. Defaults are 1.5× on weekdays, 2.0× at weekends (Saturday and Sunday — you choose the days) and 2.0× on GOV.UK bank holidays for England and Wales, Scotland or Northern Ireland. Any multiplier from 1× to 10× works, and you can give individual people their own multiplier or no premium (1.0×). Weekly wages are divided by weekly hours and monthly salaries by weekly hours × 52 ÷ 12 to get the hourly rate. With premium pay off, employees enter the amount themselves as before.

Exporting overtime

Click Export and choose CSV or JSON. The file uses the filters on the page (status, employee, day-worked range and search) and lists every matching request with hours, day type, multiplier, hourly rate, amount and currency, the reviewer, the rejection reason and the timesheet it was paid on. Approved totals are given once per currency, never added across currencies. A single month is saved as, for example, overtime-2026-09.csv.

User Timeoffs

The User Timeoffs page lets admins review all employee leave requests. It supports three views — Table, Cards, and Calendar.

Timesheets

Company → Timesheetis where admins review the monthly timesheets employees submit. Tabs split them into Pending, Approved, Paid and Rejected, and the tiles show last month's pending, approved and paid timesheets and the pending amount in each currency.

Company Benefits

Company → Benefits has two views: Claims and Benefits catalogue. In the catalogue, click + New benefit to add an allowance or perk employees can claim.

Benefits can be edited, archived and restored, or deleted. Deleting stops new claims but keeps existing ones.

Benefit Claims

The Claims view has tabs for Pending, Approved, Rejected, Paid and Withdrawn, with filters for employee, benefit and pay month. Approve a claim, or reject it with a reason the employee receives by email. Nobody can review their own claim.

• Approved claims are paid with the employee's timesheet for that pay month and appear as their own lines in its pay breakdown.
• When the timesheet is paid, its claims become Paid. If the timesheet is rejected, the claims move to the next one.
• Each claim is in the employee's pay currency; a timesheet only includes claims in its own currency.

See the Benefits guide for the full employee and admin walkthrough.

API keys

Company Info → Developers lets another system use TeamTrackin through its API: read and change tickets, move them across columns, add comments and checklists, and read boards, sprints and people. Click New key and choose:

• A name, so you know where the key is used.
• Acts as: the person the key works as. Every call runs with their boards, permissions and Space roles, so a key can never do more than they can. A key acts as you; owners and admins can choose someone else who can't do more than them (a shared "API bot" user works well).
• Start from a preset: Read everything, Project manager, HR, Full access (account owner only) or one of your company's own presets. It ticks only what you may give, within your plan, and says how many it left out; you can then change the boxes. Save as preset saves the ticked boxes under a name.
• Permissions: Read, Write and Delete for each area (tickets, comments, files, boards, Docs, time, people and more; some areas also have Approve or Budget). The Read / Write / Delete header stays at the top while you scroll. A call needs the permission and the person's own permission. A lock means only owners and admins can give it (hover it, or tap it on a phone); greyed-out boxes aren't in your plan or are things you can't do yourself (hover for why).
• An expiry date, the addresses calls may come from, and a lower requests-per-minute limit, if you want them. Each key in the list shows the calls a minute it really gets: your plan's limit, or the key's own when lower.

Nobody can give a key more than they can do themselves: permissions you can't use are greyed out, and a key never does more than whoever made or last changed it could do at that moment. Only the account owner can change a key that acts as the owner or someone with more rights, or that someone with more rights set up. Everything a key changes shows via API key: <name> in ticket history, comments, Docs page history and the Change log, and the account owner gets an e-mail and a notification whenever a key is made, changed or revoked.

The key is shown once, with a Copy button: store it in the other system straight away; it can't be shown again. Change opens a key: the top shows Created by, Acts as, Last changed by, Started from preset and Last used, and Activity lists every change to the key. Below you edit its name, permissions, expiry, addresses or limit. Revoke stops it at once and moves it to the Revokedtab, where it stays greyed and read only with who revoked it and when; a revoked key never works again and doesn't count toward your plan. Anyone with "Manage API keys" can revoke any key. If the person a key acts as leaves, the key stops working and the people who manage keys get a notification, so they can give it to someone else or revoke it.

Presets (at the top of API keys) lists your company's own presets: New preset, Edit (name and permissions) and Delete. Permissions you can't give yourself are greyed out and can't be saved in a preset. Deleting a preset doesn't change the keys made from it.

Webhooks

A webhook tells another system the moment something happens: a ticket is created, moved or assigned, someone comments, a sprint starts or a release goes out. Click New webhook in the Developers tab, enter the https address to send to, tick the events and, if you like, choose boards. The signing secret is shown once: the other system uses it to check each delivery really came from TeamTrackin.

• Send test sends a test event; Delivery log shows every delivery with its answer, how long it took and when the next try is.
• A delivery that fails is tried again after 1 minute, 5 minutes, 30 minutes, 2, 6, 12, 24 and 48 hours.
• A webhook that keeps failing (50 failed deliveries in a row, or 7 days) is turned off, and the person who added it is told. Fix the receiving side, then click Turn back on.
• New secret makes a new signing secret; for 24 hours deliveries are signed with both, so nothing is lost while you switch.
• Events from a private board are only sent while the person who added the webhook can still open that board.

AI tools

Company Info → Developers → AI tools lets the AI tools your team already uses (chat apps, code editors and any other AI tool that supports MCP, the open standard for connecting AI tools) find, create and update your tickets, boards, sprints, time and more, as one person and only within the permissions you give it. Click Make link the first time: your company gets its own connector link. Copy link copies it; Made and Last used show under it.

• Code editors and other tools with an API key: make a key on the API keys tab with the permissions the tool should have, add a remote server in the tool (it may be called a connector or an MCP server), paste the connector link as its address and add a header named Authorization with the value Bearer followed by the key. Tools set up with a settings file can copy the example shown.
• Chat apps with Sign in with TeamTrackin: add a custom connector in the chat app with the connector link and click Connect. Each person signs in to TeamTrackin, checks the permissions (Read, Write and Delete columns, as on the key page), unticks anything they don't want and clicks Approve. Permissions with a lock can only be approved by owners and admins (hover the lock, or tap it on a phone). Approving needs the "Connect AI tools" permission (owner and Admins by default), and nobody approves more than they can do themselves.
• Connected AI tools: everyone sees the chat apps they approved in Profile menu → Settings → Connected AI tools, with their permissions and last use, and can click Disconnect. People with "Connect AI tools" also find the company's link there under Connect an AI tool, with Copy and two short steps; everyone else is told to ask an owner or admin for that permission. People with "Manage AI tools" see the whole company's list here.
• Company AI policy: click Change to choose which actions AI tools may use (untick Every tool, then tick the ones to allow) and which addresses they may call from. It applies to every AI tool, with an API key or signed in.
• New link replaces the link if it was shared too widely. The old link stops at once; API keys keep working, and chat apps that signed in must connect again.