Leanmote has five access levels. Four are assigned on the Users page; Team Leader is not — it follows team membership.
The first thing to know is that levels add up. A person can hold more than one, and what they can do is the union. The page says so in the hint under the selector: "Everything here adds up. Team Leader is set on the Teams tab."
The five levels
Owner — everything a Manager can do, plus organization settings, and the only level that can grant Owner.
Manager — manage users, teams and integrations, including assigning access levels — a Manager can grant Manager, Collaborator and Bot, but not Owner. The rule is that you can grant your own level or anything less privileged. Access every metric area — delivery, cost and AI — plus Strategic Overview and the Actions Hub. Create and share views.
Team Leader — a collaborator who leads a team. Can access their team's delivery and AI metrics, plus Strategic Overview and the Actions Hub, and create and share views. Assigned automatically from the Teams page, not here.
Collaborator — standard member. Connects their own productivity tools, views dashboards shared with them, and sees their own AI usage.
Bot — service or automation account, not expected to sign in interactively.
What "Manager" is called
If you're looking for Admin, it's Manager. The level is the same one older documentation and some internal code still call admin; the label everyone sees in the product is Manager.
Assigning a level
Open a user on the Users page and edit their access levels. Because levels add up, you add and remove them rather than picking one.
Team Leader is the exception: it's set by making someone a manager of a team, on the Teams page. Adding it by hand on the Users page isn't how it works — the selector's hint points you to the Teams tab.
Downgrading yourself
If you remove your own privileges the product stops you to confirm, and it lists exactly what goes:
Users and Teams management
Every metric area — delivery, cost and AI — plus Strategic Overview and the Actions Hub
Integration configuration
Organization settings and access level management
The warning is worth reading: you'll need another Owner to restore your access, and it takes effect immediately. That's the strongest argument for the policy below.
Recommended access policy
At least two Owners. Not for convenience — because an Owner is the only one who can restore access, and a single Owner who downgrades themselves or leaves the company locks the organization out of its own settings.
Managers for whoever runs the tooling — the people who connect integrations and maintain users and teams.
Engineering managers get Team Leader through the Teams page, not by hand. That way their access follows the team they actually lead, and it stays right when teams change.
Collaborators by default. Everyone still connects their own tools and sees their own AI usage; nobody is blocked from working.
Bot for service accounts. It keeps automation out of the human roster and signals that nobody should expect it to sign in.
Related articles
Users management
Teams management
SSO and SCIM