Limits and rules
The limits that hold for every team, whatever the model says: which repositories and branches kanman may write, how changes merge, what helpers can reach, and one daily budget.
kanman’s important limits are not instructions to a model. They are enforced where the action happens: on the machine that pushes and merges, in the sandbox, on the network and on your code host. A model that misunderstands or is misled by text in a ticket still cannot cross them.
What holds for every team
| Limit | How it holds |
|---|---|
| Repositories | kanman works only on the repositories you connected to the team. |
| Branches | kanman pushes only branches that start with kanman/. Protected branches and your code host’s own rules apply to it like to any colleague. |
| Merging | A change merges only when CI is green and a reviewer that did not write it approved its latest commit. See How kanman checks its work. |
| Credentials | Code host tokens and model keys stay outside the helpers’ sandboxes. Every change is scanned for credentials before it is pushed. |
| Sandbox | Each helper works in its own sandbox with its own copy of the repository. |
| Network | Helpers reach only what the work needs, plus the hosts your team allows. See Internet access while the coding tool works. |
| Text from outside your team | Ticket text, merge request comments and CI logs are read as information, never as instructions. See Text from outside your team. |
| Budget | One daily budget per team. When it is used up, kanman stops and says so. See Budgets and cost. |
What you choose
- The team’s repositories, under Team > Repositories.
- Internet access for the helpers, under Team > Environment > Internet access.
- The model provider, under Team > Models > Model access.
- Who must approve merges. If a person should approve every merge, or every merge to certain branches, require approvals on your code host. kanman waits for those approvals like any other teammate.
- Pausing. Admins can pause a team at any time; kanman then starts nothing new. See Teams.
Everything is logged
Every plan, launch, review, question, answer and merge is written to the team’s activity log with its time and reason, so you can answer “why did kanman do this?” and “who approved this?” months later. Every settings change is recorded in the audit log with who made it.
Related
Last updated: January 1, 0001
Open kanman