Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Transfer folders, sites, and datasets between Organizations and resources

Organization management enables the centralization of information and the management of access rights to PIX4Dcloud datasets (projects) and sites, which are generated by users according to their roles within the Organization. This article explains how to transfer resources (folders, sites, and datasets) between Organizations with any active Pix4D license with access to PIX4Dcloud.

IN THIS ARTICLE

Requirements
How to transfer a resource
Resource transfer with Team Access Control (Enterprise)
Use cases and conditions

Requirements

To transfer folders, sites, or datasets between Organizations, the following conditions must be met:

  1. Organization membership
    1. The user must belong to both the source and target Organizations.
    2. The user must accept the invitation to the target Organization before initiating the transfer.
  2. Roles
    The user must be at least:
    1. Manager in the source Organization
    2. Editor in the target Organization
  3. License requirements
    1. Both Organizations must have an active Pix4D license with access to PIX4Dcloud.
  4. Dataset status

    1. Only Processed datasets can be transferred.

    2. Multiple projects can be transferred simultaneously only if all are Processed.

    3. If one selected project is not processed, the transfer will fail for all selected items.

Information:

  • Existing shared links will no longer work after the transfer.

  • The AWS cluster location where the project is stored does not change.

  • License allowances or credit balances may be affected depending on the license model (see Use Cases below).

How to transfer a resource

  1. Log in with the Pix4D credentials on cloud.pix4d.com/login.

  2. In Drive, select the source Organization using the Organization switcher.

  3. Select the folders, sites, or datasets to transfer.

  4. Click on Move to.
    Organization source. Select. Move.png
    Source organization in the organization switcher. Select and Move.
  5. Switch to the target Organization using the Organization switcher.
    Organization target. Move here.png
    Select Target organization in the organization switcher.

  6. Click Move here:

    • Either inside an existing folder, or

    • At the root level (top-left corner).

  7. Confirm the transfer when prompted.Notification Common

Resource Transfer with Team Access Control (Enterprise)

This section applies to the PIX4Dcloud Enterprise license.

In Enterprise Organizations using Team Access Control, additional role requirements apply.

Organization-level roles

The user must be:

  • At least Manager in the source Organization

  • At least Editor in the target Organization

Member-level permissions (within the same Organization)

When transferring resources (datasets, sites, folders) within the same Organization, the user must be:

  • At least Member_Manager on the source resource

  • At least Member_Editor on the target location

Transfer steps

The transfer procedure is identical to the steps described above.
transfer_resources_Member

Warning: When moving resources within an Organization:

  • Access permissions inherited from the original location may change.

  • Users who previously had access may lose access depending on the permissions of the new destination folder or site.

Carefully review access settings after performing internal transfers.

Uses cases and conditions

The impact of a transfer depends on whether the Organizations use:

  • Images & Projects allowance model

  • Credits model

  Destination organization using images and projects Destination organization using credits
Source organization using images and projects

Use case 1. Destination org will be paying for the projects as the allowance will be decreased by the new projects.

Source org will see its allowance to be increased with the projects gone.

Use case 2. Neither destination org’s credits nor Source org’s allowance change.
Source organization using credits Use case 3. Not allowed

Use case 4. Credits are not modified, both org’s credits balance is unaffected by the transfer.

Source org was the payer as the credits were consumed there at the time of the processing.

Use case 1 - Organization with images/projects transferring to an Organization with credits

We allow the transfer of projects between a source Organization using images/projects to a target Organization using credits under the following conditions.

  • All projects are older than 1 month, or
  • The license in the source organization has expired.

Important: There is no impact on the target Organization on credits or on the source destination for their allowance.

Example A: Simon belongs to
  • Organization A, where there are 1000 images and 20 projects left.
  • Organization B, where there are 100 credits remaining.

Simon moved project 1 (which was processed in the cloud, including 250 images) from A to B, which was processed 2 months ago.

After the move, the allowances of the two Organizations will be (nothing changed):

  • Organization A: 1000 images and 20 projects left.
  • Organization B: 100 credits.

Use case 2 - Organization with images/projects transferring to an Organization with images/project

Information: The images/projects will be discounted from the source Organization and added to the target Organization.
Example B: Anna belongs to
  • Organization A, where there are 1000 images and 20 projects left.
  • Organization B, where there are 2000 images and 10 projects left.

Anna moved project 1 (which was processed in the cloud, including 250 images) from A to B.

After the move, the allowances of the two Organizations will be:

  • Organization A: 1250 images and 21 projects left.
  • Organization B: 1750 images and 9 projects left.

Use case 3 - Organization with credits transferring to an Organization with image and projects 

Warning: No folders, sites or projects can be moved from a source organization using credits to an organization using images/projects.

Use case 4 - Organization with credits transferring to an Organization with credits

Starting on June 1st, 2023, there will be users who will use credits instead of images and projects.

Information: In this case, when a project is moved from one Organization to another, nothing will change in terms of credits in any of the Organizations when both are on credits.

Example C: Jane belongs to

  • Organization A, where there are 200 credits remaining.
  • Organization B, where there are 100 credits remaining.

Jane moved project 1 (which was processed in the cloud, consuming 45 credits) from A to B.

After the move, the allowances of the two Organizations will be:

  • Organization A: 200 credits.
  • Organization B: 100 credits.