Org Settings > Remove a member
Member deletion
Can’t delete a member from your Tallyfy organization? You must disable a member before you can permanently delete them. Here’s how to fix common blockers.
- Check member status - Active, Disabled, or Invited?
- Check admin role - Default Admin or Administrator?
- Count admins - How many active admins in the organization?
- Note the exact error - What message appears?
Tallyfy requires a two-step process - disable first, then delete:
- Go to Settings > Organization > Members
- Click the member’s name
- Click Deactivate Member
- Reassign their tasks when prompted
- Then permanently delete them
The full error reads: “Cannot modify the default administrator. Please assign another member as default administrator first.”
To fix this:
- Click a different administrator’s profile
- Select Make Default Administrator
- Go back to the original member
- Proceed with deactivation
No other admins? Promote a Standard member to Administrator first.
Bot accounts (like Tallyfy Bot) can’t be removed or disabled. They don’t count toward billing - they handle automated comments and system tasks.
When removing a member through the DELETE /organizations/{org}/users/{user_id} endpoint, you’ll see “You can’t remove a bot user from this organization!” instead.
If you try to disable the only administrator, you’ll get the “Cannot modify the default administrator” error. Fix it by promoting any Standard member to Administrator first, then remove the original admin.
- Clear browser cache and cookies
- Verify status shows “Deactivated”
- Check for active API tokens - revoke them manually
- If access persists after 30 minutes, contact support
Deactivated members are hidden by default:
- Go to the Members list
- Filter by Show: All or Show: Deactivated
- Search by name or email
For multiple deletions via API:
- Always disable before deleting (two-step process for each)
- Space out requests to avoid rate limits
- Process in reasonable batches
When permanently deleted, Tallyfy:
- Appends “(Deleted)” directly to the last name (no space) - e.g.
SmithbecomesSmith(Deleted) - Changes email to
{email}.deleted.{user_id}- e.g.john@company.combecomesjohn@company.com.deleted.12345
This prevents conflicts if you re-invite that person later.
Removed immediately:
- Login access
- Active sessions
Kept for compliance:
- Task completion history (name shows with “(Deleted)”)
- Process participation records
- Comments and attachments
- Audit trail entries
When no member is available for reassignment, tasks fall to “Tallyfy Bot” (the system user). This commonly happens with API deletions that skip reassignment.
Two-step sequence:
1. DELETE /organizations/{org}/users/{user_id}/disable2. Wait for 200 response3. DELETE /organizations/{org}/users/{user_id}/deleteSingle-step with reassignment:
DELETE /organizations/{org}/users/{user_id}?with_reassignment=true&to={new_user_id}The single-step endpoint handles deactivation and removal together, and reassigns tasks to the specified member.
- You can’t delete the last member
- Contact support for organization closure
If Admin A backs up Admin B and vice versa, add a third admin temporarily to break the cycle.
Accidentally deleted someone? Contact support immediately with:
- Organization name
- Member email
- Deletion date
Recent deletions may be restorable. For older ones, send a new invitation.
- Error messages don’t match those listed here
- Server errors (500-series) appear during deletion
- Deletion seems stuck for over an hour
Provide: organization name, member email, exact error message, screenshot
- Keep at least 2 administrators at all times
- Document who the default administrator is
- Use consistent offboarding procedures
Members > How to remove a member
Org Settings > Member statuses
Was this helpful?
- 2025 Tallyfy, Inc.
- Privacy Policy
- Terms of Use
- Report Issue
- Trademarks