Users and groups
People reach KAMI Tasks through two layers: users — everyone in your organisation who can be assigned work — and groups, the teams they are organised into. Groups are what projects actually grant access to.
Users
The Users page lists everyone, with their groups and status, and a search to find people fast.
The page is read-only, and that is deliberate. Users are not created or removed inside KAMI Tasks — they come from your main KAMI account, and are managed under My Teams › Profile › Access settings. One place decides who is in the company; Tasks inherits it.
So when someone new can't be found here, the fix is in My Teams, not in Tasks. Once their access includes Tasks, they appear.
Groups
Groups organise people into teams — a squad, a department, a working group — and each member is added with a role in that group. Create a group, name it, and add its members.
The reason groups matter is access: projects grant access to groups, not to individuals. Everyone in a granted group can see and work the project. See Projects and access.
That makes group membership the answer to most access questions:
- New joiner can't see the project → add them to the team's group
- Whole team needs a new project → add the group to the project, once
- Contractor finished → remove them from the group, and every project the group carries goes with it
Rules and things to watch
- Keep groups meaning teams. A group per real team stays maintainable; a group per project invert-maps the whole idea and you end up managing the same people twelve times.
- Removing someone from a group removes what the group carried. That's the feature — but check they aren't mid-ticket in one of those projects before you sweep.