Overview
Admina may assign a retirement label to an account even though the user has not retired.
This page explains the causes and how to resolve them.
How It Works
Account statuses, including the retirement label, are determined automatically based on the employee master data.
In general, Admina assigns the “Retired” label to an account under two conditions. The account does not exist in the employee master, and it has an active account in another SaaS service.
For detailed conditions, see Employee status conditions.
Solutions
Check whether any of the following approaches (1, 2, or 3) applies to your situation.
1. Register the SaaS account in the employee master
Register the email address labeled as retired in the employee master. This resolves the discrepancy and removes the retirement label.
After registration, go to Integrations > Status and run Sync.
2. Check the employment end date
Go to Directory > User Info and check the employment period end date. After the employment end date passes, the status changes to “Retired” automatically on or after the following day. If you change only the status back to “Active” and leave the end date in place, the status changes to “Retired” again.
If an end date is present, clear the date field first. Then change the status to “Active” and click Apply.
The status will show “Active” after the next sync.
3. Use the mute feature to exclude the account from alerts
If you cannot register the account in the employee master, use the mute feature instead. This temporarily excludes the account from alerts, though the retirement label itself remains.
For details on account muting, see Mute alert notifications.
If you checked 1, 2, and 3 and still cannot find the cause, contact support. Include the email address of the affected user.Last modified on October 6, 2026
