Skip to content

Setting up your team (for the administrator) ​

The first account to register automatically becomes the Administrator — this tutorial is for you. Everything below lives in one place: the user menu (the person icon top right) → Organization settings. We'll go in the order a new company actually needs: purpose → branding → people → roles → AI → look; at the end there is an overview of all the page's tabs and the sections in them. The page has a tab list on the left (a strip at the top on a phone) and shows one tab at a time.

Organization settings — the tab list on the left, the People tab open.

0. Say what it is for ​

On the first login the first admin is asked once: “What will you use killBottleneck for?” — Company or team · Family and friends · Just for myself. The answer shapes the starter map (the tour of the tool): a solo user is not told to “assign roles”, a family is not told to “invite colleagues”. Everyone you invite inherits the choice, and you can change it any time in Organization settings → Organization and look → Instance purpose (existing maps stay as they are). Skip means “company or team”.

The purpose question shows once, to the first admin; the starter map is built from it.

Starter-map items carry a plan (“I want to do this”), not a deadline — they light up in My day for the first days but never turn red; whatever you skip stays in the map. Right after this question a Connect your AI agent dialog may follow (one line for Claude Code, Cursor or Codex) — feel free to skip it; it is always available in the menu under Connect AI agent.

The Organization and look tab: the Organization name and the Logo (PNG/JPG/WebP) show for every member once saved — in the app header, in the map toolbar and in the browser window title, replacing the default name. Two fields and a Save button; done in a minute.

SVG is not accepted

We removed SVG from the allowed logo formats: it can carry a script and is served from the same origin as the app, so it could be turned against you. Export the logo as a PNG.

2. Invite people ​

The Invite user button above the user table (the Invite to team item in the user menu opens the same dialog, so you don't have to visit the settings). The dialog asks for the Colleague's e-mail and the Role right away — Member / Manager / Administrator:

An invitation — the e-mail and the new member's role in one step.

What happens next depends on the instance's e-mail:

  • Cloud (and self-host with SMTP configured): the colleague receives an e-mail with a link to set their password. Until the first sign-in, the table shows the Invitation sent — waiting tag.
  • Without SMTP: the app shows you a Temporary password exactly once (The password is shown only now — you won't see it again after closing) and a Copy credentials button — hand them over; they change the password on first sign-in.

You can also invite straight from the Share dialog: when you share a project with an address that has no account, it offers Invite to the organization and share — the account is created as a Member and the invitation goes out in one step. When a member who may not invite shares a project with such an address, you get a request in the bell (“shares the project … with …, who has no account yet”); clicking it opens this dialog with the address pre-filled and the account exists once you confirm the invitation. More in Team and roles.

The second way in is self-registration: whoever registers on the instance's address is in your organization. An instance reachable from the internet therefore wants a registration key — without it, registrations are refused. (Cloud instances have this handled for you.)

3. Hand out the roles ​

The table on the People tab has the columns User · Role · AI manager · Structure manager · Deputy · Last seen and a ⋯ menu at the end of the row (Reset password, Delete account); the map count and the account date are in grey under the name. On a phone each person gets a card instead of the table. The role changes right on the row:

Roles, flags and the deputy change right on the user's row.
RoleWhat it's for
AdministratorManages the instance: users, roles, the organization, AI, the default look.
ManagerMay invite new people into the organization (as members only) — hiring without access to settings. Sees projects like a member, plus the Organization overview.
MemberTheir own tasks and the maps shared with them. The default for every newcomer.

Independently of the role, two switches sit on the same row:

  • AI manager — receives the “I would like this automated” requests and maintains the AI agent registry. Until you appoint someone, the administrator covers it automatically (the switch says automatic).
  • Structure manager — may draw the org structure and appoint people to positions, typically an HR person. Gets a narrowed view of Organization settings; only an administrator can still delete the structure.

The Deputy column is the member's personal stand-in for automation rules. A deputy of a specific position in the org structure is more precise; the personal deputy acts as the fallback when the person holds no position with a deputy.

The ⋯ menu at the end of each person's row has Reset password and Delete account:

  • Reset password — with SMTP a link to set a new password goes out; without SMTP the app shows the new password once (Hand the new one over in person — it will not be shown again). The current password stops working and the person is signed out everywhere. Users change their own password in My account → Change password.
  • Delete account — the dialog first lists the numbers: what passes to a new owner, what goes with the account (private projects and pages nobody else sees, personal settings, private events and personal templates) and what stays — everything the person put into other people's and team projects: attachments, time entries, comments, invoices, team templates, events in shared calendars and shared pages (the author shows as former member). Shared projects do not go with the account: a project shared with at least one other person, with the team or by a public link passes to its 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 it has none, to you — the public link keeps working. It happens inside the delete itself — either everything happens or nothing does. The new owner is notified and the handover is in the project's change log. An administrator neither sees nor takes over another person's private projects — they go with the account unless the owner hands them over or shares them first. The open steps assigned to the person can be reassigned to another member right in the dialog — they pass only in the projects that member can see, and the dialog says beforehand how many that is. What you do not reassign stays marked with a red former member badge (in the map, in Tasks and in the assignee picker) and anyone who edits the project can reassign it. Finished steps do not change. The last administrator can be neither deleted nor demoted. Members cannot delete their own account, the administrator does it here.

4. Turn the AI on (or off) ​

It depends on where killBottleneck runs:

Your own server: the AI features section decides where the whole instance gets its AI — it applies to all members immediately:

Five AI modes — from fully off to your own endpoint. The section exists on your own server only.
ModeWhen to pick it
DisabledNo AI at all — maps, tasks and sharing work fully; the AI buttons disappear.
Your own OllamaYour own hardware: free AI, quality set by your model. killBottleneck runs in Docker, so localhost won't work — use http://172.17.0.1:11434 (Linux) or http://host.docker.internal:11434.
OpenAI-compatibleYou have a key from OpenAI, OpenRouter, Groq, Mistral… or run your own vLLM / LM Studio. Enter the address, the key and the model name — Test connection tells you right away whether it works. Dictation goes through the same service.
AI service via APIA remote AI service compatible with the killBottleneck API — enter an address and a token.
Custom endpointFor the advanced: your own service speaking the same API contract.

The section also has The assistant reads images (photos of notes, screenshots) with its own image model and a Test an image button, and an optional voice transcription endpoint. The note The .env configuration on the server is currently active — saving will override it means the settings in this form take precedence over the environment variables.

Cloud: the operator configures the AI and the AI features section is not shown. You watch the usage.

Wherever the assistant runs there is an AI credits section: usage for the organization and per person in turns (1 turn ≈ one ordinary message to the assistant) for this week and the previous weeks. Below it the Weekly quota: Turns per week and Administrators' reserve (%) — the quota runs from Monday and does not carry over; administrators may use the whole quota, and their reserve cannot be used up by others. On a hosted instance the plan's cap is set by the operator and your own value can only lower it.

5. Unify the look (optional) ​

The Instance default appearance section sets a skin for everyone who hasn't picked their own — it colors the login screen too. A user's own choice always wins.

A company default look — gentle branding without restricting anyone.

All tabs of Organization settings ​

The tabs come in this order; Invite is always in the page header:

TabSections and what they are forWhere
PeopleThe user table: roles, AI manager, Structure manager, Deputy; Reset password and removal in the ⋯ menu.everywhere
Organization and lookOrganization — name, logo, Instance purpose; Instance default appearance — a skin for everyone without their own choice; Custom domain — the app on tasks.company.com (KB Cloud Pro and AI Agent only), see Custom domain.everywhere
Structure and deputiesA table of positions and functions, holder, deputy, Open the structure map. See Org structure.everywhere
Shared calendarsCalendars that are not a person: Company, Meeting room (bookings never overlap), Time off (with approval). Who adds entries, who sees it. See Tasks and My day.everywhere
Subscription and invoices (self-hosted Invoices)Plan & payment — plan, period, card or bank transfer (cloud only), see The trial and plans; Billing details — your details on our invoices (cloud only); Issuing invoices — your company's supplier details on the invoices the assistant issues to your clients, see Invoices.everywhere
AIAI features — where the instance gets its AI, five modes (self-hosted only); Own model or API key (cloud only); AI credits — usage in turns, the weekly quota and the administrators' reserve (wherever the assistant runs).everywhere

Limits

  • Organization settings are visible to the administrator only (a Structure manager sees just the People and Structure and deputies tabs).
  • Members cannot delete their own account and the account e-mail cannot be changed — both are handled by the administrator.
  • Without SMTP, passwords are handed over in person: the temporary and the reset password are shown only once.
  • Invitations from the Share dialog have a daily limit; once it is used up, invite the colleague from here.
  • The operator can turn off the purpose question and the AI agent dialog with KB_PURPOSE_ASK=0 (KB_AGENT_SETUP_ASK=0 turns off only the agent one).

Where to go next as the admin ​

Open source under the MIT license · © Tengo s.r.o.