There is no "deactivate" for a user. Access is removed by taking away roles, tribes or membership. Pick the smallest thing that achieves what you need.
| Action | What it removes | Use when |
|---|---|---|
| Remove roles | Their organisation-wide access | They are changing job, not leaving. |
| Detach from a tribe | Their administration of one tribe | They have moved to another tribe. |
| Delete User | Their organisation membership and roles | They have left your organisation. |
| Detach from Organisation | All of the above plus their Organisation Chart record | They have left and should disappear entirely. |
When somebody leaves
- Remove their organisation roles.
- Detach them from every tribe they administer.
- Disconnect their team member login, and check on the Users screen that it actually went.
- Use Detach from Organisation if they should also come off the org chart, the tribe directory and your website team page.
DETACH FROM ORGANISATION ALSO DELETES THEIR ORG CHART RECORD
Their work stays
None of these delete anything the person created. Their enquiries, CRM records, notes, articles and media all remain exactly where they are, still credited to them. Only the access goes.
Their Gorilla Dash account also survives — it belongs to them, not to you, and they may work with other organisations on the platform. Removing them from yours does not close it.
A trap when detaching from a tribe
DETACHING SOMEBODY WHO NEVER ACCEPTED REMOVES THEM ENTIRELY
Things you cannot do yourself
- Edit the name or email of somebody who belongs to several organisations — they change it themselves in their own account.
- Reset two-factor authentication for a multi-organisation user — that needs Gorilla Dash support.
- Transfer or remove the Owner role.
Every one of these actions confirms with "This will be permanent". For roles and tribe detachment that overstates it — you can simply add them back. For Detach from Organisation it is accurate.