Connecting your organisation's tools

Add GitLab, Jira, code search and other tools, test them, and understand when people's own accounts are used instead.

What you’ll learn

How to add, test and choose the default connector of each kind.
How secrets are kept.
Why people's own GitLab and Jira accounts come first.
Which addresses your tools need.

Where it lives

Settings › Connectors holds your organisation's tools: GitLab, Jira, Sourcebot (code search), Confluence, Hoppscotch, Postman, Figma, npm and MCP servers. Owners and admins change them; members see which are connected, never their values.

Add and test a connector

Example: Acme Logistics connects its GitLab.

In Settings › Connectors, click Add next to GitLab.
Give it a Name (Acme GitLab), the address and a token.
Click Save, then Test the connection. The result stays next to it: Works, Failed with the reason, or Not tested.

Repeat for Jira, and for Sourcebot if you have it.

You can have several of one kind — two GitLab servers, for instance. The first is the default: runs use it. Make it the default changes that; Delete removes one.

Tip: test after every change. A failed test tells you why in plain words — a wrong address, an expired token — before a developer's run finds out.

Secrets

Tokens and passwords are stored encrypted. After saving, the page shows only that a value is set and its last 4 characters. Replace changes it; Remove clears it. Values go only to Claude's tools during a run.

People's own accounts come first

For GitLab and Jira, each person can connect their own account in Connected accounts. When they have, Claude and the app work as them, with their own rights — so GitLab and Jira show who did what. Without it, the organisation's default connector is used and the run says so. Merging, closing and deleting merge requests from the app always need the person's own GitLab account.

Ask everyone to connect their accounts in their first week.

Code search

With a working Sourcebot connector, Claude searches your code with it during Set up. Without one, Claude searches the repositories read-only through GitLab instead.

Addresses your tools need

Livra reaches your tools over the internet, so connectors use public https addresses — not localhost or private networks. A GitLab or Jira that is only on your office network needs a public (or allow-listed) address first.

Tip: if a connector fails with a message about a private address, the fix is a public (or VPN-reachable) address for the tool — not a different token.

Check yourself

1. A developer connected their own GitLab account. Whose rights does Claude use when pushing their feature?

The developer's own, through their personal account.

2. You added two Jira connectors. Which one do runs use?

The default one — the first added, unless you chose another with Make it the default.

3. A connector points at http://10.0.0.5. What happens?

It's refused: connectors use public https addresses only.