Understanding the Auto-Delete Users Feature in Adobe Learning Manager (ALM)

Introduction

User lifecycle management is a critical component of any enterprise learning platform. Adobe Learning Manager (ALM) provides administrators
with powerful governance controls, including the Auto-Delete Users feature available under:

Admin Role → Settings → General → Auto Delete Users

This auto-delete functionality of ALM soft deletes the users automatically, the system retains all the historical learning records of the users in this deletion process.

This article explains how the auto-delete mechanism works, why users may be removed, and how administrators can manage this feature effectively
to avoid confusion.
---

What Is the Auto-Delete Users Feature?

The Auto-Delete Users feature is designed to automatically remove inactive users (No logins for a period) from the system after a defined period.
This helps organizations:

• Maintain a clean user database 
• Reduce inactive account buildup 
• Support data governance policies 
• Improve reporting accuracy 
• Align with compliance and retention standards 

Administrators can configure the number of days of inactivity after which a user account will be deleted.

In the referenced case, the account was configured to auto-delete users after 540 days of inactivity.
---

How the Auto-Delete Counter Works:

The most important concept to understand is how the inactivity countdown is calculated.

Key Rule:
The auto-delete counter checks inactivity when a user is first added to ALM and resets ONLY when the user logs into the platform.

This means:

• Creating a user starts the inactivity Job check.
• Marking a newly created user as registered does NOT reset the clock.
• Deleting and re-registering does NOT reset the clock.
• Updating user details does NOT reset the clock.
• Only a successful login (Either by admin impersonation or user login themself) resets the counter.

This distinction is critical.
---

Example Scenario

Let’s walk through a real-world example to understand the behavior:

1. A user is added to ALM on January 1, 2023.
2. The auto-delete policy is set to 540 days.
3. The user never logs into the platform.

Result:
On approximately June 24, 2024 (540 days later), the system automatically deletes the user.

Now consider a slightly different case:

• The user is re-added/re-activated from deleted state.
• The user is marked as “Registered” by admin or automatic.
• The user does NOT log in within 24 hours.
• The user has already crossed 540 days of inactivity and then system deletes the user again.

In this case, the account will still be deleted because registration status does not count as activity. Only login activity resets the counter.
---

Why Deleting or Re-Registering Does Not Reset the Counter

Administrators sometimes assume that modifying the user profile will restart the inactivity period. However, the system logic is based strictly on login timestamps.

The system tracks:

Last Login Date

It does NOT track:

• Last profile update 
• Last registration change 
• Last admin modification 
• Last enrollment action 

The auto-delete mechanism is tied specifically to authentication activity.

This confirms that the only way to reset the countdown is through login activity.

Another important aspect:

If a user is marked as “Registered” after already being inactive for more than the configured threshold (540 days in this case),
they must log in within 24 hours.
If they do not log in, the system proceeds with deletion because the inactivity period has already been exceeded.

This is working as designed and prevents bypassing inactivity rules through administrative status changes.
---
Best Practices for Administrators

To avoid unexpected deletions, administrators should:

1. Review Auto-Delete Settings Regularly 
   Confirm that the inactivity period aligns with business policy.

2. Communicate Login Expectations 
   Inform newly created users to log in at least once.

3. Monitor Inactive Users Reports 
   Track users approaching the inactivity threshold.

4. Use Impersonation When Necessary 
   If appropriate and compliant with internal policy, admins can impersonate users to generate a login event.

5. Consider Adjusting the Threshold 
   If 540 days is too restrictive for certain user groups, adjust accordingly.
---.
The feature supports governance and data hygiene standards, especially for large enterprises with thousands of users.

Key Takeaways

• The inactivity checker job starts when the user is first added.
• Only login activity resets the auto-delete timer.
• Registration or profile updates do not reset the counter.
• Users exceeding the configured inactivity period will be automatically deleted.
• Admin impersonation can generate a login timestamp if appropriate.
• The behavior is expected and policy-driven.

--

Conclusion

The Auto-Delete Users feature in Adobe Learning Manager is a powerful governance tool designed to automatically manage inactive accounts.
While unexpected deletions may initially appear concerning, they typically reflect the enforcement of configured inactivity policies.

Understanding that only successful login activity resets the countdown is essential for administrators managing user lifecycles.

By reviewing configuration settings, monitoring inactive users, and ensuring timely logins, organizations can effectively leverage this feature
without disruption.

Clear awareness of how the mechanism works ensures smoother user management and eliminates confusion around expected system behavior.

-------------------------------------------------------------------------------------------------------------
#ALM #Adobe learning manager #automatically delete users #auto-delete #auto gdpr delete #user clean up #compliance #period #inactive users #inactivity #no login #soft delete