Skip to main content

What happens to Claude artifacts when a user is removed from the organization? We tested it

By Asaf Yoshpe, CEO, CloudX

Published: Last tested:

The short answer

On the Claude Team plan, artifacts shared inside the organization are not deleted when an employee is removed. In our test on November 10, 2026, all five test artifacts stayed available with their stored data, but without an owner. No one in the organization can change their general access from inside the artifact, not even the organization's Primary Owner. The Primary Owner can delete them from the admin console, but only the artifacts listed there. When we re-added the same user with the same email, the artifacts were linked to that user again.

We tested this ourselves on CloudX's Claude Team plan, because Anthropic's official documentation does not fully answer this question.

How we tested what happens to Claude artifacts

  1. We created a test user on the company domain.
  2. In that account, we built five artifacts with dummy content, each with a different sharing setting:
    • A page shared with the whole organization
    • A page shared with one person as Editor
    • A page inside a folder shared with the whole organization
    • A task tracker that stores data
    • A Claude Docs document shared with the whole organization
  3. We removed the user from the organization.
  4. From the organization's Primary Owner account, and from the account of the person given edit access, we checked what still opened, what we could change, and what appeared in the organization's admin console.

What stays and what disappears when an employee is removed from Claude Team

  • Chats disappear for the team. According to Anthropic's documentation, after removal other members can no longer access the employee's chats, including chats shared with the organization.
  • Artifacts stay. All five artifacts opened after removal with their content intact. The tracker kept every task, including edits made to them.
  • Ownership does not pass to anyone. The sharing dialog shows the owner as "Owner" with no name, and the admin console lists the owner as "Former member". Unlike Google Workspace, which asks who should receive a user's files before you delete the user, we found no way to transfer ownership of a Claude artifact as of November 10, 2026.
  • Re-adding the same user restores ownership. In a follow-up check, we added the removed user back to the organization with the same email. The artifacts that had shown an owner with no name were linked to that user again.

Who can manage a Claude artifact after its owner leaves

Control over an orphaned artifact depends on the permission the employee granted before leaving, not on your role in the organization. Even the Primary Owner, as a Viewer, can do less than a colleague who was given edit access.

ActionViewer (even the Primary Owner)EditorPrimary Owner, from the admin console
Open and viewYesYesOnly if shared with the organization
Edit contentNoYesNo
Add or remove peopleNoYesNo
Change general accessNoNoNo
DeleteNoNoYes, if listed
DuplicateYesYesOnly if they can open it
  • Only the artifact's Owner can change general access. The product says so directly: "Only Owners can change general access". An artifact shared with the whole organization stays open to the whole organization, and the only way to close it is to delete it.
  • The admin console does not show everything. In our test, the list under Organization settings > Artifacts > Published artifacts showed only artifacts shared with the whole organization, publicly, or by email outside it. The page shared with one specific person did not appear there, so the Primary Owner could not delete it either.
  • An Editor can remove other Editors. A single Editor can end up in sole control, and when they leave too, no one can manage the artifact.

Duplicating an orphaned Claude artifact: the workaround and its limits

Anyone who can open an artifact can duplicate it, and that is the practical way to rescue an orphaned one.

  • Whoever duplicates becomes the owner of the copy.
  • Stored data carries over. We tested this on the tracker, and every task was copied.
  • The copy is independent. A task we added to the copy did not appear in the original. Anyone still using the old link is working on a different version.
  • The copy starts private. You have to share it again and send the team a new link.
  • The original is not closed. It stays open as it was until the Primary Owner deletes it, if it appears in the admin console.

How to keep control of Claude artifacts when employees leave

  • Tools the team relies on belong to someone who stays. A shared tracker, dashboard or catalog is owned by the person responsible for it over time, such as the team or operations lead, and the employee who builds it gets edit access.
  • Do not share sensitive information with the whole organization or publicly from a personal account. Once the employee leaves, sharing with the whole organization can only be undone by deleting the artifact. Public links can only be closed with the organization-wide external sharing setting, which closes all of them at once.
  • Add Claude artifacts to your employee offboarding process. Before removal, the employee and their manager review what the employee built. What needs to continue is duplicated to an account that stays and shared again, and what is no longer needed is deleted. After removal, the options are to duplicate, to delete, or to re-add the user, which links the artifacts back to them.
  • Review the Published artifacts list regularly. It shows what is open to the whole organization, what is public, and who owns each item.

FAQ

How do I delete a Claude artifact?

Open Artifacts in the Claude sidebar, click the "⋯" menu next to the artifact and choose "Delete". Only the artifact's owner can delete it: according to Anthropic, people with "Can edit" access can't. When an artifact is deleted, everyone who was invited to it loses access. If the owner has already left the organization, see the next question.

Are an employee's Claude artifacts deleted when they are removed from Claude Team?

No. In CloudX's test on November 10, 2026, every Claude artifact the removed employee had shared stayed available, including its stored data, but without an owner.

Can you transfer ownership of a Claude artifact to another employee?

As of November 10, 2026, we found no way to transfer ownership of a Claude artifact, either in the artifact or in the admin console. The practical workaround is to duplicate the artifact, which makes the person who duplicates it the owner of the copy. Re-adding the removed user with the same email links the artifacts back to that user.

What happens to Claude artifacts if you re-add a removed user?

In CloudX's follow-up check, re-adding the removed user to the organization with the same email linked the orphaned Claude artifacts back to that user, so they were no longer ownerless.

Who can delete a Claude artifact owned by a former employee?

Only the organization's Primary Owner, from the admin console, and only if the artifact appears in its Published artifacts list. In our test, that list showed artifacts shared with the whole organization, publicly, or outside the organization, but not an artifact shared with one specific person.

Can the Primary Owner change the sharing of a former employee's Claude artifact?

No. Only the Owner of a Claude artifact can change its general access, so an artifact a former employee shared with the whole organization stays open to the organization until the Primary Owner deletes it.

Does duplicating a Claude artifact copy its stored data?

Yes. In our test, duplicating a Claude task tracker copied every stored task. The copy is independent and starts private, so it has to be shared again with a new link.

What happens to a former employee's Claude chats?

According to Anthropic's documentation, the rest of the organization loses access to a removed employee's Claude chats. Removal does not delete the data, and the organization's Primary Owner can still include it in an organization data export.

Limits of this test

We ran this test once, on November 10, 2026, on Claude Team, from the organization's Primary Owner account, and checked re-adding the user in a follow-up check. We did not test the Owner or Admin roles, or Claude Enterprise. The product changes quickly, and we will update this article when the behavior changes. Test it in your own organization before building a policy on it.

Sources