Team and roles
One instance is one team. No tenant juggling: the people on your instance are your organization, with a shared name and logo — in the app header, in the map bar and in the browser window title. This page is about people and who sees what; the company settings section by section are in Organization settings.
Where to find it
- People and roles: the user menu → Organization settings (administrator).
- An invitation: the Invite user button there, or the Invite to team item in the menu (administrator and manager).
- Sharing a map: the Share button in the map bar (under ⋮ on a narrower display), or the share icon on the project card.
The name and logo show in three places: the app header, the map bar (until you upload a logo the killBottleneck brand stands there) and the browser window title. A publicly shared map is the exception — a visitor sees the killBottleneck brand, not your logo.
Three roles and two flags
| Role | What it means |
|---|---|
| Administrator | Manages the instance: users, roles, the organization, AI, the default look. The first registered account becomes one automatically. |
| Manager | May invite new people into the organization (as members only) and sees the Organization overview. Sees projects like a member. |
| Member | Their own projects and those someone invites them to. They can create projects and share them with colleagues too — the role plays no part in that. |
Beyond the role a person can carry up to two flags, independent of the role:
- AI manager — receives the “I would like this automated” requests and maintains the AI agent registry. Until you appoint someone, the administrator covers it.
- Structure manager — typically an HR person. Draws the org structure, appoints people to positions, sets deputies on people, invites new people (as members only) and resets their passwords. In Organization settings they see only the people table and the structure; they cannot change roles or flags and may not delete the structure.
Getting people in
- By invitation — Invite user / Invite to team: e-mail and role. With SMTP configured the colleague gets a link to set a password and carries the Invitation sent — waiting tag in the table; without SMTP the dialog shows you a temporary password once, with a Copy credentials button. When the invitee signs in for the first time, you get a New member signed in notification.
- By self-registration — whoever registers on the instance's address is in your organization. An instance reachable from the internet therefore wants a registration key.
- From the Share dialog — see below (Invite to the organization and share).
- On top you can add Google sign-in — see Configuration.
Sharing maps
- In the map click Share (the Share map dialog: Access is tied to the e-mail.).
- Pick an organization member… (it offers only those who don't have the map yet), or type an e-mail.
- Choose the level View, Collaborate or Edit and confirm.
What you see: a row in the Shared with (N) list with the level, which can be changed or removed any time; an address without an account gets the no account yet tag — the share is pending and they see the project once they come through the invitation link (see below). Pending addresses are visible only to whoever manages the sharing, not to readers of the map. Below the list is the Have work here via team access block — people who see the map thanks to the whole organization and own a step on it.
The dialog has two wider circles that only the owner turns on: Whole organization (All team members will see the map — view or edit) and Public link — see Public maps.
When the recipient has no account yet
A share with an address without an account waits for the invitation to be confirmed. Access goes only to whoever signs up or signs in through the invitation link — the link works once, is valid for 30 days and confirms exactly that one project. Signing up with the same address without the link gives no access (the e-mail is not verified at sign-up, so anybody could otherwise pick the share up).
- Open registration (your own server without a key): with a mail gateway an e-mail invitation with the link goes out. Without a gateway — and whenever the e-mail does not go out (today's invitation limit is used up, an invitation was already sent earlier) — the dialog shows the link and offers Copy sign-up link; hand it over yourself.
- Send again: a pending address has an envelope button — it issues a new link (the old one stops working) and sends it by e-mail, or shows it for copying.
- Has an account, invitation not confirmed: the recipient signed up without the link. Send the invitation again, or click Share on the row — that confirms the share for the account with this address.
- Closed registration (a registration key, the cloud): the dialog asks “… is not in the organization and cannot sign up here on their own. What do you want to do?”
- If you may invite (administrator, manager, structure manager): Invite to the organization and share — the account is created as a Member, the invitation goes out (without a gateway you see a temporary password) and they see the project right after signing in. An invited member of the organization also sees projects shared with the whole organization and the people list, and takes up one seat. If they only need a look, there is Just a look: turn on the public link.
- If you may not invite (a member): the share stays pending, the recipient gets an e-mail that an admin has to create the account, and the admins find a request (Organization) in the bell with a link to the invitation with the address pre-filled — one per address no matter how many projects. Once the account exists, the address shows has an account, invitation not confirmed and you confirm the share with the Share button (an invitation to the organization does not activate pending shares by itself).
What each level may do on a map
| View | Collaborate | Edit | Owner | |
|---|---|---|---|---|
| See the map, comment | ✓ | ✓ | ✓ | ✓ |
| Change the status of own goals (I am the assignee) | ✓ | ✓ | ✓ | ✓ |
| Open the detail of every step | — | ✓ | ✓ | ✓ |
| Add and edit goals, assign work | — | — | ✓ | ✓ |
| Change an existing deadline | propose | propose | only as the assigner | ✓ |
| Remove a goal with an assigned task | — | — | only as the assigner | ✓ |
| Share the map with more people | — | — | ✓ (co-manager) | ✓ |
| Whole organization, public link, archiving, deletion | — | — | — | ✓ |
The “change the status of own goals” row applies to View too: whoever got the work must be able to finish it — they can check off their own step even with view-only access. The difference on deadlines: with View you can ask for a different due date only on your own work, with Collaborate on others' too; the deadline is always changed by the assigner (who approves or declines). The same goes for people with team access.
Sharing also happens as a side effect: assigning a goal to someone without access asks “… doesn't have access to this map. Share it with them as a collaborator (view map, work on own tasks) and assign them?” (for a view-only person it offers an upgrade to collaborator), and a project created from a template with tasks is shared with the assignees automatically, with Edit access.
Where shared maps show up
The home page sorts projects by their relation to you: My projects (you created them), Where I'm involved (other people's projects shared with you or with your task or goal) and Organization projects (shared with the whole organization). A project card carries a badge — Private map — only you can see it, Shared with the whole organization (read / edit), or Public map. Below the project name sits the main goal — when it matches the name, the line is not shown.
Limits
- Whole organization and the public link are turned on by the owner only; a co-manager (Edit) shares with specific people only.
- Invite to team in the menu is seen by administrators and managers only; a structure manager invites from the table in Organization settings.
- Invitations from the Share dialog have a daily limit; an invitation to one project goes to an address only once.
- An administrator does not see other people's private maps — not even in the Organization overview.
- When an administrator deletes the owner's account, a shared map does not go with it — and neither does a map with a public link (the link keeps working): it passes to a co-manager (a person with the Edit share who has already signed in to the app; with several, the one shared with the longest), and when there is none, to the administrator who deletes the account. The new owner is notified and the handover is in the map's change log. A private map (nobody else sees it and it is not public) goes with the account.
Related
- Organization settings — people, roles and flags section by section
- Team setup (admin) — the step-by-step guide for the administrator
- Public maps — the widest circle
- External contacts — people without an account you can assign work to
- Configuration — the registration key, Google, SMTP

