# Transfer organization ownership

{% hint style="success" icon="user-key" %}
Action available only for Organization Owner 
{% endhint %}

One common example of when organization ownership transfer is needed happens when a user signs up for Coupler.io from their personal email and later wants to transfer it to a work email address.

### Steps to transfer organization ownership <a href="#steps-to-transfer-organization-ownership-7ljai" id="steps-to-transfer-organization-ownership-7ljai"></a>

#### 1. Add the new owner to your organization <a href="#id-1-add-the-new-owner-to-your-organization-lhus5" id="id-1-add-the-new-owner-to-your-organization-lhus5"></a>

As the current organization owner:

{% stepper %}
{% step %}
Go to Settings (gear icon in the left sidebar)
{% endstep %}

{% step %}
Navigate to "Organization" settings
{% endstep %}

{% step %}
Click on the "Organization owners" tab
{% endstep %}

{% step %}
Click the "Invite new user" button
{% endstep %}

{% step %}
Enter the email address of the person who will become the new owner
{% endstep %}

{% step %}
Click "Send invite"
{% endstep %}
{% endstepper %}

The new user will have full organization owner access, including billing and all workspaces.

#### 2. Remove the previous owner <a href="#id-3-remove-the-previous-owner-optional-83srz" id="id-3-remove-the-previous-owner-optional-83srz"></a>

{% @arcade/embed flowId="8Vs1yNwSEsRYeNwQPWnn" url="<https://app.arcade.software/share/8Vs1yNwSEsRYeNwQPWnn>" %}

The new owner must do this:

{% stepper %}
{% step %}
Go to Settings → Organization → Organization owners tab
{% endstep %}

{% step %}
Find the previous owner in the list
{% endstep %}

{% step %}
Click the "Remove" icon next to their name
{% endstep %}

{% step %}
Select a new owner for all resources of the previous owner (data flows, source and destination connections, dashboards).
{% endstep %}

{% step %}
Confirm the removal
{% endstep %}
{% endstepper %}

The removed organization owner will lose access to the organization, workspaces, and billing management.

***

### What happens to resources owned by the removed organization owner? <a href="#what-happens-to-resources-owned-by-the-removed-organization-owner-8qtzo" id="what-happens-to-resources-owned-by-the-removed-organization-owner-8qtzo"></a>

When removing an organization owner who has created data flows, dashboards, or connections in workspaces, you must reassign their resources to prevent disruption.

#### If the organization owner has no role in some or all workspaces <a href="#if-the-organization-owner-has-active-resources-iao_a" id="if-the-organization-owner-has-active-resources-iao_a"></a>

When you attempt to remove an organization owner who has no workspace-level role in one or more workspaces, you'll see a confirmation popup with a required action to select a new owner for their resources:

<div align="left"><figure><img src="https://2487187314-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCgnmco7kCnvytNIN8YdT%2Fuploads%2FddXmBUlvErTygOobkgDy%2Fimage.png?alt=media&#x26;token=c9c353ba-903c-4c8f-8078-91cbcbe33995" alt="" width="375"><figcaption></figcaption></figure></div>

**What you need to do:**

{% stepper %}
{% step %}
Select a new owner from the list of users with organization owner role.
{% endstep %}

{% step %}
Click "Delete owner."
{% endstep %}
{% endstepper %}

All resources (data flows, dashboards, connections) will be transferred to the selected user. The removed user will lose organization owner access but keep any workspace roles they have.

**What gets reassigned:**

* <i class="fa-square-check">:square-check:</i> Data flows created by the removed owner
* <i class="fa-square-check">:square-check:</i> Dashboards created by the removed owner
* <i class="fa-square-check">:square-check:</i> Source connections (e.g., Google Ads, Facebook Ads accounts)
* <i class="fa-square-check">:square-check:</i> Destination connections (e.g., Google Sheets, BigQuery)
* <i class="fa-square-check">:square-check:</i> Both private and shared connections

**What is not reassigned:**

* <i class="fa-square-xmark">:square-xmark:</i> Chats with AI agent

{% hint style="warning" %}
This reassignment happens across all workspaces where the removed organization owner had no workspace-level role.
{% endhint %}

#### If the organization owner has role in all workspaces <a href="#if-the-organization-owner-has-no-role-in-workspaces-7cmi1" id="if-the-organization-owner-has-no-role-in-workspaces-7cmi1"></a>

You will still see a popup to reassign resources - this is more of a safety checkpoint, in case the owner you are removing creates something during the deletion process in a workspace where they have no workspace-level role (for example, creating a new workspace and adding a data flow there).

***

### Alternative: Change role instead of removing organization owner <a href="#alternative-change-role-instead-of-removing-9lbzl" id="alternative-change-role-instead-of-removing-9lbzl"></a>

If you want the person to keep working in specific workspaces without organization-level access:

Before removing them as organization owner:

* Invite them to specific workspaces as Admin, User, or Guest.
* They'll have both an organization role and workspace role(s).

Then remove their organization owner role - they'll retain access to workspaces where they were invited, and their resources will remain under their ownership in those workspaces.

**Steps:**

{% stepper %}
{% step %}
Go to workspace settings for each workspace where you want them to keep access.
{% endstep %}

{% step %}
Click "Invite new user."
{% endstep %}

{% step %}
Enter their email (the same email as their organization owner account).
{% endstep %}

{% step %}
Select a role: Admin, User, or Guest.
{% endstep %}

{% step %}
Send the invitation.
{% endstep %}

{% step %}
Go back to Settings → Organization → Organization owners.
{% endstep %}

{% step %}
Remove them as organization owner.&#x20;

*you will still see reassign resources pop-up to cover any race conditions during removal - select yourself and confirm deletion*
{% endstep %}
{% endstepper %}

**Result:**

* They keep access to specific workspaces
* They keep ownership of their data flows and connections in those workspaces
* They lose access to billing and organization settings
* They lose access to other workspaces where they weren't invited