Removing or deactivating team members
How to offboard a team member from Rezi while preserving their history and protecting account security.
When a team member leaves or no longer needs Rezi access, removing or deactivating their account immediately is an important security step. A former team member with active Rezi access can view guest conversations and contact data. Do not delay this step when offboarding.
Rezi offers two options for handling departing team members: deactivation (recommended in most cases) and deletion. Understanding the difference helps you choose the right approach for each situation.
Deactivating vs. deleting
Deactivating a team member immediately revokes their login access. They cannot sign in and will see an access denied message if they try. However, all their historical activity is retained, messages they sent, conversations they handled, notes they added, and is still visible to the rest of the team. Deactivated accounts can be reactivated if the person rejoins. This is the correct option for most offboarding situations.
Deleting a team member permanently removes their account. Their historical activity is attributed to 'Deleted user' in the activity log. Deletion cannot be undone. Use deletion only when there is a specific reason you need to remove all trace of the account, such as a compliance or legal requirement.
How to deactivate a team member
- 1
Go to Settings > Team
- 2
Click on the team member's name
- 3
Click Deactivate account
- 4
Confirm the deactivation
- 5
The team member is immediately signed out of all active sessions and cannot sign back in
Deactivating a Rezi account does not revoke the team member's access to any other tools you gave them credentials for (your booking-platform accounts, a smart lock app, shared calendars). Revoke access to those services separately through their own admin consoles.
Reassigning work before offboarding
Before deactivating a team member, reassign any active guest conversations they own to another team member. Open items assigned to a deactivated user still exist but are not actively monitored by anyone. Use the bulk reassignment tool in Contacts to transfer all assignments in one operation.
Handling the transition for guests
Guests do not see individual team member names in Rezi messages unless you have enabled per-agent attribution. In most configurations, all messages appear to come from your property name, so guests are typically unaffected by a team member change. If you have custom attribution enabled, update the outgoing name on any ongoing conversations with the new responsible team member.
What happens to messages sent by a deactivated team member?
Can I reactivate a deactivated team member?
Can I transfer ownership of the account to another team member?
Was this article helpful?