Departing members
Because roles carry no access to private files, a workflow or task board only that person could open stops being openable by anyone the moment they leave. Nothing is deleted and nothing changes hands automatically: what they owned stays theirs, waiting for them if you invite them back. What they owned appears under Organization → Unassigned, with a Claim button on each row. Claiming makes you the owner, so you can review, move, or delete it. It is an explicit, logged action rather than a quiet back door, and requires 2FA if your workspace demands it of admins. The page lists the top of each tree rather than every file, so a folder appears as one row. Anything of theirs inside a folder a current member still owns is not listed, because that owner can already reach it. Claiming a folder takes everything inside it that has no owner, recorded as a single audit entry naming the folder. The page lists only what no current member owns, so it is never a way to browse teammates’ work, and it says plainly when nothing is waiting. What differs between leaving and being suspended is the access they were given by other people.
A file that was in Team Library only because of a share held by the person leaving becomes Private
again, and drops out of Team Library along with anything inside it. The original creator is still
recorded on everything throughout. Only ownership and who can open it change.
Reinstating a suspended member restores their membership and role, and everything they owned and
everything shared with them works again exactly as before. Anything an admin claimed while they
were suspended stays with the person who claimed it.
Claim a resource
Select Claim beside the resource and confirm. The item becomes yours and leaves the list. If the claim fails, the list refreshes because another person may have claimed it. Review the updated list before trying again.Related
Organization management
Understand workspace roles and settings.
Plan limits
Compare plan allowances and capacity.