---
title: "Linked applications"
slug: "linked-applications"
updated: 2026-07-22T12:33:25Z
published: 2026-07-22T12:33:25Z
canonical: "docs.connect.visma.com/linked-applications"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.connect.visma.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Linked applications

The **Linked applications** page gives you a complete overview of the applications that have access to your Visma account, and lets you control what they can do.

## Your application list

Every linked application is listed with its logo, name, and when you last signed in to it. The list is grouped so you can tell at a glance how each application got its access:

- **Provided by your organization**: applications your organization's administrator connected on your behalf.
- **Third-party apps**: applications not made by Visma, clearly marked with a badge.
- Applications you connected yourself by signing in and giving consent.

## Managing consent

When an application asked for your consent, a **Manage consent** button appears on its row:

1. Click **Manage consent** to see exactly which permissions you granted (for example access to your profile or email address) and when you gave them.
2. Click **Withdraw consent** and confirm if you no longer want to share that data.

Withdrawing consent does not block you from the application: you can still sign in to it afterwards. Only the data-sharing consent is withdrawn, and the application will ask for consent again if it still needs the data.

## Managing offline access

Some applications can access your account while you are not actively signed in, for example to sync data in the background. These grants appear behind a **Manage offline access** button:

1. Click **Manage offline access** to see each grant, including when it started and when it was last used. There can be several, one for each device or browser where you allowed it.
2. Click **Revoke** next to any grant you no longer want, and confirm.

Revoking offline access signs that background connection out. The application can request it again the next time you sign in to it.