Skip to main content

Ownership transfer

Ownership transfer rebadges a project from one organisation to another in a single database transaction. The project, all its work orders, all form submissions, all files, all dashboards, and all feature classes used by the project move to the new owner. The prior owner can stay involved via an automatic reciprocal share-back at a role they choose, or hand over cleanly with no share-back.

Use ownership transfer when:

  • A contractor finishes a build-out project and hands it over to the asset owner.
  • A managed-service customer takes a project back in-house.
  • Two business units within the same parent organisation reorganise their tenancy.

For ongoing collaboration without changing ownership, use project sharing instead.

Request a transfer​

You can request a transfer when you are the project's OWNER and the target organisation already exists in Stratumly.

  1. Open the project.
  2. Click Transfer ownership in the page header.
  3. In the dialog:
    • Target organisation: enter the recipient's share handle OR an OWNER's email address.
    • Share back as: pick CONTRACTOR, VIEWER, or NONE.
      • CONTRACTOR keeps you working on the project after transfer with edit rights.
      • VIEWER keeps you with read-only visibility.
      • NONE is a full handoff. After execute, you lose all access.
    • Message (optional): a note the recipient will see when they approve. Max 2000 characters.
  4. Click Request transfer.

The recipient organisation's OWNERs receive an email and an in-app notification with the approval link.

Approve a transfer (recipient side)​

When you receive a transfer request:

  1. Click the email link, or open My account → Transfers → Received.
  2. The pending row shows the project name, the requesting organisation, the proposed share-back role, and the requester's message.
  3. Click Approve. A confirmation modal warns that this is irreversible.
  4. Confirm.

The project rebadges to your organisation immediately. The prior owner gets a share-back at the role they selected (unless NONE).

If you do not want to take the project on, click Decline. You can optionally include a reason. The requesting organisation is notified and the project stays where it was.

Cancel a request you sent​

  1. Open My account → Transfers → Sent.
  2. Find the row.
  3. Click Cancel.
  4. Confirm.

You can cancel any PENDING request. APPROVED or DECLINED requests are final.

What happens during execute​

When the recipient approves, the system executes the transfer:

  1. The project row's organisation_id rebadges to the new owner.
  2. All work orders, form submissions, dashboards, and files on the project rebadge.
  3. Feature classes used by the project either rebadge in-place (if no other source-org project uses them) or get cloned into the destination org with their features re-pointed at the clone (if shared across multiple source-org projects).
  4. The reciprocal share-back row is inserted (unless NONE).
  5. Any pre-existing shares from the prior owner to the new owner on this project are soft-revoked (no longer needed).

Everything happens in one database transaction. If anything fails, the whole transfer rolls back and you can retry.

Concurrent approvals​

If two OWNERs on the receiving side click Approve at the same time, one succeeds and the other gets a 409 "Another OWNER already actioned this transfer" message. Refresh the inbox to see the current state.

What recipients without a Stratumly account see​

The approval landing page at stratumly.com/transfers/{token} shows project + requesting org + expiry context, but the approve / decline actions redirect to the authenticated app. If the recipient does not have a Stratumly account yet, they will need to sign up before they can complete the transfer.

For ongoing read-only updates to a customer without an account, use a client portal instead.

What next?​