Connect your accounts

What you’ll learn

• Why Claude should use your own GitLab and Jira accounts.
• How to create and save the tokens.
• How to turn on two-step verification and keep your recovery codes.

Why your own accounts

Claude works as you. When you connect your own accounts, commits, merge requests and Jira comments are made with them, so your team sees who did what. Tokens are stored encrypted and never shown to Claude.

If you don't connect, Claude falls back to your organisation's connection, if an admin set one up — and the run says so. Some actions always need your own account: merging, closing or deleting a merge request in the app is never done with the organisation's account.

Open Connected accounts from the account menu: click your name at the bottom of the sidebar.

Connect GitLab

1. In GitLab, create a Personal access token with the scopes api, read_repository and write_repository.
2. In Connected accounts, paste it under GitLab. The server is your organisation's GitLab.
3. Click Check and save. The app tests the token before saving it, then shows Connected with your GitLab name.

Connect Jira

1. Create an API token at id.atlassian.com › Security › API tokens.
2. Enter your Jira Email and the token.
3. Click Check and save.

Disconnect removes a token at any time.

Example: Amina joins the product team on Monday. Before creating her first feature, she creates a GitLab token and a Jira token, saves both, and sees Connected twice. When Claude later pushes a branch for her team-invites feature, the commits show her name in GitLab.

Tip: tokens expire. When GitLab or Jira refuse an old token, runs say the connection failed. Create a new token and save it again in the same place.

Two-step verification

Your Livra account can open your code and your tickets, so protect it.

1. In Connected accounts, under Sign-in and security, click Turn on two-step verification.
2. Scan the QR code with an authenticator app (Google Authenticator, Microsoft Authenticator, 1Password…).
3. Enter the code it shows.
4. Save your recovery codes somewhere safe. They are shown only once, and each one signs you in once if you lose your phone.

From then on, every sign-in asks for a code — also when you sign in with Google or GitLab.

Tip: a password reset link does not turn two-step verification off. If you lose both your phone and your recovery codes, ask your organisation's owner or an admin: they can reset it for you, and you set it up again after signing in.

Other sign-in options

In the same section you can Link or Unlink Google or GitLab sign-in, when your platform has them turned on, and change your password. New passwords need at least 12 characters and must not appear in known breaches.

Install it as an app

Livra installs like an app, straight from the browser: it then opens from its own icon, in its own window, without tabs or an address bar. In Chrome or Edge, use Install as an app in the account menu (or the install icon in the address bar). On iPhone and iPad, Share › Add to Home Screen; in Safari on a Mac, File › Add to Dock. There is nothing to update: the app always shows the latest version.

Check yourself

1. Which GitLab token scopes does Livra need?

api, read_repository and write_repository.

2. You never connected GitLab. Can you merge a merge request from the app?

No. Merging, closing and deleting always use your own GitLab account.

3. You lost your phone but kept your recovery codes. How do you sign in?

Enter one of the recovery codes when asked for a code. Each works once; then set two-step verification up again.