For the complete documentation index, see llms.txt. This page is also available as Markdown.
How to remove a user
Revoke a person's access to your account or a workspace, and see what stays behind when they go.
Remove a person at the account level or workspace level to revoke their access. The remove control sits on their row in the user list, behind a confirmation dialog. Most of their work stays in place, and re-inviting them later restores nearly all of it.
Prerequisites
You need Admin permissions at the level you're removing from. Editors can't manage users.
Warning: Removing a user revokes their access until you re-invite them
A removed person loses all access to the level you removed them from. They keep their own Smaply login, but they can't open your content again until you send a new invitation.
How to remove a user
The steps are the same whether you're removing someone from the whole account or from a single workspace. Only the starting list differs.
1
Open the user list
For account-level access, open Account settings from the account name at the top of the left sidebar and go to the Users tab. For a single workspace, open Workspace settings and go to Manage users.
2
Click the X on the person's row
Find the person in the list. Each row has an X at the far right, after their role. Click it to open the confirmation dialog.
3
Confirm the removal
In the Revoke access dialog, click Yes, revoke access. To back out without removing anyone, click No, go back.
The Revoke access confirmation dialog
What happens to their content
Removing someone doesn't delete the work they did. Most of it stays exactly where it was, and a few things change to reflect that the person is gone.
Element
What happens
Journey map they created
Their name stays on the map as the creator
Journey map coordinator role
Becomes unassigned
Comments they left on cards
Stay on the cards
Portfolio item assigned to them on a card
Their name stays visible on the card, but the item shows as unassigned when you open it to edit
Share links they created
Stop working
Version history entries they authored
Removed from the version history
If you re-invite the person, they recover almost everything. Their journey map creator attribution is never reassigned, so it stays as them. The share links they created and their portfolio item assignments work again once they accept.
Remove a user or change them to Viewer?
Removing is the more drastic option. If you only want to limit what someone can do rather than cut their access entirely, change their role to Viewer instead. A Viewer keeps access to your content but can only look at journey maps, and they can still comment on cards.
