How to Reassign Work When Removing a Team Member
When removing a team member with open work, URBI requires you to reassign their tickets, tasks, and subtasks first.
Last updated
When you remove a staff member, board member, or PM who has open service tickets or tasks assigned to them, URBI will block the removal until their work is transferred to someone else. This prevents tickets from becoming orphaned with no owner.
This applies in two places: - Property settings — removing a member from a single property - Company settings — removing a member from your company (which removes them from all properties your company manages)
Steps
Removing a member from a property
Go to Settings → Users for the property.
Find the member you want to remove and click Remove (or the remove action in their row).
If the member has any open assigned tickets, tasks, or subtasks, a Reassign Work modal appears before the removal proceeds. It shows the total number of items that will be transferred.
Select a recipient from the Transfer work to picker. The list shows only team members who are eligible — meaning they are already a member of the property (or all affected properties, for company-side removals). You cannot type in a free-form name; only eligible members appear.
Click Reassign & Remove. URBI transfers all assigned tickets, tasks, and subtasks to the chosen recipient and then removes the member. The recipient receives a single summary notification.
A confirmation toast appears and the member is removed from the user list.
Removing a member from your company
Go to Settings → Company → Team.
Find the member and click Remove. (Note: only a company admin can remove a member from the company.)
The same Reassign Work modal appears. For company-level removals, it shows a breakdown of affected tickets per property (since the member may be assigned across multiple properties your company manages).
Select a recipient and click Reassign & Remove. The transfer covers only the properties your company formally manages — it does not touch unrelated properties.
The "no eligible recipient" block
If no one else on the team is eligible to receive the work, the modal shows a blocked state:
No eligible recipients All tickets and tasks must be transferred before this member can be removed. There are no other team members who share access to all affected properties.
What to do: - Add another team member to the relevant property first, then return to remove the original member. - If the work can be resolved before the removal, close or complete the open tickets and tasks, then try removing the member again — the modal will not appear if there is no open work.
Things to know
The removal does not proceed until you confirm. The Reassign Work modal must be completed; there is no way to skip it when open work exists.
The recipient must have access to all affected properties. If a member is assigned to tickets across two properties, the recipient must be a member of both. The picker automatically filters to only show eligible recipients.
If the modal shows an error after confirming, it will stay open with a message explaining what went wrong. The removal has NOT been completed. Try again or contact support if the error persists.
If the member has no open work, they are removed immediately without any modal.
Subtask-only assignments count. If a member is assigned only to subtasks (not the parent ticket), the modal still appears. All assigned work — tickets, subtasks, and collaborator rows — is transferred.