team-files-vs-confluence-1
Confluence Smart Links Explained
See how they work, where they fail with external files, and more secure, consistent management alternatives.
Read more: Confluence Smart Links Explained
untitled_Flux 2 Pro_2026-03-26_21-41-00
Jira SharePoint Integration
Discover how to sync files, automate folders, and enhance collaboration in Jira Cloud and Data Center.
Read more: Jira SharePoint Integration
Porto-pic
About us
From the start, our goal has been to remove the hidden friction that prevents teammates from collaborating easily on the files that matter most. We believe productivity is not about adding more tools but making the ones you already use work together seamlessly. Based in Porto, ikuTeam builds the invisible layer for the Atlassian ecosystem to dissolve file silos and help over a million users stay focused and move faster.
Read more: About us
team-files-vs-confluence-1

Confluence Smart Links Explained

See how they work, where they fail with external files, and more secure, consistent management alternatives.
Read more: Confluence Smart Links Explained
untitled_Flux 2 Pro_2026-03-26_21-41-00

Jira SharePoint Integration

Discover how to sync files, automate folders, and enhance collaboration in Jira Cloud and Data Center.
Read more: Jira SharePoint Integration

About us

From the start, our goal has been to remove the hidden friction that prevents teammates from collaborating easily on the files that matter most. We believe productivity is not about adding more tools but making the ones you already use work together seamlessly. Based in Porto, ikuTeam builds the invisible layer for the Atlassian ecosystem to dissolve file silos and help over a million users stay focused and move faster.
Read more: About us
Porto-pic
Product Documentation

Nov 19, 2026

5.4 What happens to attachments when a user leaves?

It depends on your Mirror Storage Permissions setting. With Mirror Storage Permissions ON, nothing breaks for the rest of the team, because everyone signs in with their own Google account. With Mirror Storage Permissions OFF, folders connected with the leaver's Google account stop working once that account is removed, and a space admin can fix it with Transfer ownership.

With Mirror Storage Permissions ON

Each user authenticates to connected folders with their own Google account, and your Google Drive permissions decide what they can see and edit. When someone leaves, only their own access ends. As long as the files and folders still exist in Google Drive, the macros on your pages keep working for everyone else.

The folders the leaver connected still list them as owner. To keep someone on the team able to manage those folders, transfer ownership (see below).

With Mirror Storage Permissions OFF

Google Drive Connector uses the folder owner's Google account to show the folder to everyone in the space. If the owner's Google account is deleted or loses access, the folder and every Google Drive Connector macro that shows content from it stop working.

To fix it, a space admin or Confluence admin takes over the folder:

  1. Open Google Drive Connector under Space apps in the space sidebar.

  2. Open the actions menu of the connected folder and click Transfer ownership.

  3. Confirm with Transfer ownership. You're now the owner.

  4. If you haven't authenticated the folder yet, click Authenticate and sign in with a Google account that has access to the folder.

That's it. The macros on your pages work again for everyone.

With Mirror Storage Permissions OFF, we recommend connecting folders with a service account instead of a personal account. That way, your audit trail stays clear and folders keep working when people leave.

A transfer is logged

Every transfer appears in Connected folder logs (Space settings > Google Drive Connector Settings > Support > View Logs), so your team can always see who took over a folder and when.