Use Cases:

• Compliance with security policies requiring inactive account management
• Reduce attack surface by limiting dormant accounts
• Automatic cleanup of ex-employee or contractor accounts
• Meet audit requirements for user access management
• Protect against unauthorized access through forgotten accounts

Best Practices:

• Start with a higher threshold (90+ days) and adjust based on your needs
• Always exclude Crowdin Agents and critical backup accounts
• Review the log regularly to ensure expected behavior
• Consider excluding organization admins for safety

Note: Locked users can be manually unlocked through the Crowdin UI if needed. The app respects existing account states - already blocked users remain blocked.

Note:: The app runs once a day at 2:00 a.m. UTC. After enabling the app, it will lock inactive users during the next run, not immediately.

Important: API tokens owned by locked users will stop working. If you have service accounts with Personal API tokens, whitelist them to avoid locking them.