Mirus Works! Help Centre article

When someone leaves your organisation, we update their status in Mirus Works! to Inactive. Occasionally, leave/shifts that was already rostered for them before they left can still appear against future dates in their roster.

Why this happens

To protect your roster data, Mirus Works! restricts changes to records for anyone marked Inactive. This is intentional for their upcoming shifts, but it currently also means any leave rostered before they became inactive can't be removed from the Rostering screen — even by an administrator.

Recommended: clear the roster before deactivating

The best way to avoid this is to prevent it in the first place. We recommend adding this as a standard task in your offboarding process:

• Before deactivating a team member through the importer, check their roster for any future-dated shifts and leave, and remove these first. Once the import sets their status to Inactive, these records can no longer be edited or removed directly in Mirus Works!.

What to do if it's already happened

If a team member has already been made inactive and you notice future-dated leave or shifts still sitting against them:

• Note the team member's name and the specific leave or shift dates you'd like removed.
• Send these details to Mirus Support at support@mirusaustralia.com, or log a request through your Zendesk support portal.
• Our team will remove the leftover entries on your behalf and confirm once this is done.

Good to know

Removing these leave or shift entries doesn't affect the team member's inactive status or termination date — it's simply a clean-up of historical rostering data. 

Need help?

Contact the Mirus Australia Support team at support@mirusaustralia.com or via your Zendesk portal, and we'll be glad to help.