Org Settings > Remove a member
Troubleshooting member deletion
Can’t delete a member from your Tallyfy organization? The system requires specific conditions to be met before member removal. Here’s how to resolve common blockers and handle edge cases.
Run through this checklist to identify your issue:
- Check member status - Active, Disabled, or Invited?
- Check admin role - Default Admin or Administrator badge?
- Count administrators - How many total admins in your organization?
- Note exact error - What message appears when attempting deletion?
Tallyfy uses a two-step deletion process for safety:
- Navigate to Settings > Organization > Members
- Click the member’s name
- Click Deactivate Member
- Complete task reassignment
- Then use the permanent deletion option
Transfer the default admin role first:
- Click on a different administrator’s profile
- Select Make Default Administrator
- Return to original member
- Proceed with deactivation
If no other admins exist, promote a Standard member to Administrator first.
Bot accounts (like Tallyfy Bot) cannot be removed. They:
- Don’t count toward billing
- Post automated comments
- Handle system tasks
Create another administrator first:
- Select any Standard member
- Click Change Role → Administrator
- Then remove the original admin
- Clear browser cache and cookies
- Verify member status shows “Deactivated”
- Check for active API tokens - revoke manually
- If access persists after 30 minutes, contact support
Deactivated members are hidden by default:
- Go to Members list
- Use filter: Show: All or Show: Deactivated
- Search by name or email
For multiple deletions via API:
- Process in batches of 10
- Allow 5 seconds between deletions
- Always disable before deleting
- Use the two-step process for each
When deleted, the system:
- Appends “(Deleted)” to last name
- Changes email to
{email}.deleted.{user_id}
- Example:
john.doe@company.com
→john.doe@company.com.deleted.12345
This allows re-inviting the same person later without conflicts.
Immediately removed:
- Login capability
- API access tokens
- Active sessions
- Password data
Preserved for compliance:
- Task completion history (name shows with “(Deleted)”)
- Process participation records
- Comments and attachments
- Audit trail entries
When no suitable member exists for reassignment:
- Tasks default to “Tallyfy Bot” (system user)
- Common in: last member deletion, bulk deletions, API deletions without reassignment
Required sequence:
1. DELETE /organizations/{org_id}/users/{user_id}/disable2. Wait for 200 response3. DELETE /organizations/{org_id}/users/{user_id}/delete
With reassignment:
DELETE /organizations/{org_id}/users/{user_id}?with_reassignment=true&to={new_user_id}
Rate limits: Maximum 10 deletions per minute, 429 error if exceeded
- Cannot delete last member
- Contact support for organization closure
Admin A backs up Admin B, Admin B backs up Admin A:
- Add third admin temporarily to break cycle
- May timeout during deletion
- Use batch reassignment via API
- Process in groups of 100
Accidental deletion: Contact support immediately with:
- Organization name
- Member email
- Deletion date
Support may restore recent deletions. For older deletions, send new invitation.
Contact support when:
- Errors don’t match those listed
- Deletion affects 50+ processes
- Server errors (500-series) appear
- Deletion pending over 1 hour
Provide: Organization name, member email, exact error, screenshot
- Maintain at least 2 administrators
- Document default administrator
- Test deletion in sandbox first
- Use consistent offboarding procedures
Members > How to remove a member
Org Settings > Member statuses
- 2025 Tallyfy, Inc.
- Privacy Policy
- Terms of Use
- Report Issue
- Trademarks