Skip to content
The Library

Unsharing & Leaving

When a collaboration no longer works for a project, the underlying access paths need to be reconciled before rows or files are cleaned up. This guide explains the distinct access and roster effects of owner removal and a receiver leaving a completed share.

Understanding the Options

Section titled “Understanding the Options”

There are two distinct access changes:

  1. Remove a collaborator — the track owner removes the collaborator from a specific track group.
  2. Leave a received share — the recipient’s file-share access is removed without automatically changing credits, roster presence, or allocation.

Removing a Collaborator from Your Project

Section titled “Removing a Collaborator from Your Project”

Only the track owner can remove a collaborator from a track group.

Use the owner-controlled collaborator-removal workflow for the applicable track group. Before the collaborator row is deleted, The Library reconciles direct, member, and bucket access paths. For an email-only collaborator with a shared Dropbox folder, it removes the relevant Dropbox membership; for a registered recipient, it emits a revocation notification.

Removing a Collaborator from One Track

Section titled “Removing a Collaborator from One Track”

Removing a collaborator from one track group does not itself remove their separate assignments on other track groups. The access-path service first checks every remaining direct, member, and bucket route for the affected receiver before scheduling any cleanup.

Leaving a Collaboration

Section titled “Leaving a Collaboration”

Leaving a received share removes the recipient’s file-share access. It does not automatically remove the collaborator’s credit or roster presence, and it does not make an allocation decision for the remaining people. Cleanup is not treated as an immediate destructive local-file deletion.

Access Cleanup

Section titled “Access Cleanup”

The access-path reconciler waits until there is no active direct, member, or bucket path before cleaning up received files. Depending on the local state, it can quarantine local files rather than treating cleanup as an immediate destructive delete.

Section titled “Related”