Built for a team shipping with agents every day
Share a repository, give each person the role they need, and let Tick-it route every decision to the right one.
Owners, admins, members and viewers
Everyone in a repository can read it and see their own costs. A refusal always names who can.
| Can | Owner | Admin | Member | Viewer |
|---|---|---|---|---|
| Plan epics and create tickets | Yes | Yes | Yes | No |
| Comment, suggest changes on plans and note acceptance checks | Yes | Yes | Yes | Yes |
| Accept a plan | Yes | Yes | Yes | No |
| Start agent sessions | Yes | Yes | Yes | No |
| Change repository settings | Yes | Yes | No | No |
| See everyone's costs | Yes | Yes | No | No |
| Set budgets and caps | Yes | Yes | No | No |
| Manage members | Yes | No | No | No |
One list, the right person, told once
Every ticket waiting on a person lands in one list across your repositories: a question from a session, a plan to review, a review that won't come clean, a deploy to sign off. Whoever needs to act is told when it begins, and not again while it stays.
Shared across every repository
Members and caps
Each member's role, monthly cap and the repositories they can reach, in one place.
Shared memory
Every repository in an organisation shares one pool of memories, so a lesson learned in one helps the rest.
Costs by week
What the organisation's repositories cost each week, split by repository, person or model.
An audit log
Who changed a role, a budget or a setting, and when.
Epic owners
Every epic has an owner, and every change of owner is kept.