Your own connections: read your processes before the team's connection is approved

Sometimes the system your team works in is not connected yet: the request to connect it for the whole team is still waiting for approval. Meanwhile you can connect it with your own account. kanman then reads through it for you: your processes, checklists and runbooks, and suggests what it could take over.

Your own connection is personal and temporary. Use it until your team’s connection is approved, then disconnect it.

What kanman does with it

• It only reads. kanman uses only tools that read, and only the ones you turn on. It never creates, changes or deletes anything in that system.
• Only you see what it reads. What kanman reads appears only in your Personal chat with kanman. Your team sees nothing of it.
• Your team sees only what you start. When kanman suggests a habit from what it read, you get a card in your Personal chat. Only when you tap Start it does the habit appear for the team. Nothing starts on its own.
• Every read is logged. The connection lists everything kanman read and everything it left out, with the reason.

Connect a system

You need the address of the server your company gave you for this (for example https://mcp.example.com/mcp). If it only works inside your company’s network, kanman reaches it through your company’s runner; your sign-in is kept there too, never in a coding run.

1. Open your avatar menu and choose Your settings, then Connections (/account/connections).
2. Click Add connection.
3. Enter a name, for example “Jira and Confluence”, and the server address.
4. Leave Only use what everyone at your company can already see on (recommended, see below) and enter your company’s name.
5. Click Add and sign in. The system’s own sign-in page opens. Sign in with your account and allow access.
6. Back in kanman, the connection opens and shows its tools. Tools that only read are turned on; tools that would change something cannot be turned on at all. Click Use … tools.

The connection now shows Active.

A tool that the system adds later stays off until you turn it on. If a tool you use changes, kanman stops using it and the connection shows Tools changed until you look at it again.

Only what everyone at your company can see

This switch is on by default, and we recommend leaving it on. kanman then uses only content anyone at your company could already open, and leaves out:

• pages that are limited to certain people or groups, also when the limit comes from a page above them;
• spaces that are not open to the whole company;
• tickets with a security level;
• for Jira: tickets from projects that are not on your list of projects everyone can browse.

When kanman cannot tell whether something is open to everyone, it leaves it out. You see each left-out item, with the reason, in the connection’s log.

For Jira and Confluence, open the connection and fill in:

Turn the switch off only if you want kanman to use everything you can see yourself. It still shows it only to you.

Use it in your Personal chat

Ask kanman in your Personal chat, for example:

• “Look at my runbooks in Confluence: what could you take over?”
• “Which of my weekly checklists could run as a habit?”
• “Summarise the open tickets of the support queue.”

kanman searches the connection, opens the items that matter, and answers with what it found and which items it used. If the switch left items out, it says so. When something you do regularly could run on its own, kanman suggests it as a habit; see How habits work.

Disconnect

Open the connection under Your settings › Connections and click Disconnect. kanman signs out at the system where it can, then deletes your sign-in, the connection and its log. Habits you already started stay; change or stop them in the chat.

When you leave a workspace, your connections in it are deleted too.