• 126
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      Currently, the process of finding and deactivating inactive users(haven't accessed any products for a long time) is strictly manual as admins can either use:

      1. The Export accounts feature inside the Managed Accounts
      2. The Organization get users REST endpoint

      To find those users by looking at the Last active date.

      So, the deactivation of the accounts still depends on manually checking how long your users have been inactive and then manually deactivating them or developing a script to use the user management REST deactivation endpoint.

      Many admins are also interested in disabling the notifications that are sent to their end users upon deactivation, or improving the deactivation message to include more information about the reason for deactivation to keep users better informed.

      Suggested Solution

      Implement a deactivation policies feature for Atlassian Access where admins can configure default time for users to be deactivated by being inactive.

      Admins would then be able to configure that users who haven't accessed any products in the last 3 months will get automatically deactivated.

      Additionally, the feature could trigger an email message to the deactivated users saying why they were deactivated and who they need to contact, as well as an option to disable the notification from being sent. 

      Why this is important

      For organizations with thousands of users, the current methods of finding and deactivating, inactive users requires a lot of work from the organization admins and as the company grows this tends to get more difficult to be done.

            [ACCESS-720] Deactivation policies for managed accounts

            brady added a comment -

            This should definitely be an inherent feature available in to the Atlassian Guard to apply a policy to not just managed users but also to external users added to the org.

            It seems that the only way to do it now is to either manually audit user access or implement automations through an integrated IdP like Crowd or Okta.

            It seems like Atlassian Guard is turning out to just be a paywall to features that should be native to the platform.

            brady added a comment - This should definitely be an inherent feature available in to the Atlassian Guard to apply a policy to not just managed users but also to external users added to the org. It seems that the only way to do it now is to either manually audit user access or implement automations through an integrated IdP like Crowd or Okta. It seems like Atlassian Guard is turning out to just be a paywall to features that should be native to the platform.

            James added a comment -

            Hi,

            You can install this app from the marketplace:

            Auto Users Management 

             

            It will deactivate all inactive users you have periodically by the time you choose.

            It's totally secure, and uses Atlassian's Api's only

             

            James added a comment - Hi, You can install this app from the marketplace: Auto Users Management     It will deactivate all inactive users you have periodically by the time you choose. It's totally secure, and uses Atlassian's Api's only  

            We have developed automation to do this in crowd (as we are using data center) for users who have not logged on within 15 days. Not having this feature in Access is a very large impediment for moving to cloud.

            Daniel Bugeja added a comment - We have developed automation to do this in crowd (as we are using data center) for users who have not logged on within 15 days. Not having this feature in Access is a very large impediment for moving to cloud.

            hen.korman added a comment -

            Please Do!!!!

            hen.korman added a comment - Please Do!!!!

            This would be a big helper!

            Ricardo.Gomes added a comment - This would be a big helper!

            This will really go a long way to help we Jira admins. It might not necessarily be an automation; it could just be a feature. Probably a user management feature embedded in Jira, it could also be a setting feature which we can manually change the dates of inactivity, it is 60days for my organization. or a feature that automatically removes a user license, if they log less than twice in 30days and they can automatically be reinstated if they log in provided there is still space available. 

            Ismail Sanni added a comment - This will really go a long way to help we Jira admins. It might not necessarily be an automation; it could just be a feature. Probably a user management feature embedded in Jira, it could also be a setting feature which we can manually change the dates of inactivity, it is 60days for my organization. or a feature that automatically removes a user license, if they log less than twice in 30days and they can automatically be reinstated if they log in provided there is still space available. 

            Exactly. We don't even need this to necessary be api endpoint to automate (thought it would eb great) we just need some sort of policy enablement in place to automatically remove users after a period of inactivity

            Hamdy Atakora added a comment - Exactly. We don't even need this to necessary be api endpoint to automate (thought it would eb great) we just need some sort of policy enablement in place to automatically remove users after a period of inactivity

            This will definitely help admin to manage users efficiently and effectively. simply introduce some policy rule feature to configure default time for users to be deactivated by being inactive.

            Gain Credit added a comment - This will definitely help admin to manage users efficiently and effectively. simply introduce some policy rule feature to configure default time for users to be deactivated by being inactive.

            This would be extremely helpful to have – but also for user accounts which do not belong to Managed Accounts.

            Jana Volencova added a comment - This would be extremely helpful to have – but also for user accounts which do not belong to Managed Accounts.

            Has there been any further updates with this? I've recently got Atlassian Access and only just discovered the manual process to deactivate users. Quite disappointing considering how much we pay for it.

            Gaj Umapathy added a comment - Has there been any further updates with this? I've recently got Atlassian Access and only just discovered the manual process to deactivate users. Quite disappointing considering how much we pay for it.

              c6c23291180e Ilya Bagrak
              akasper André K. (Inactive)
              Votes:
              180 Vote for this issue
              Watchers:
              136 Start watching this issue

                Created:
                Updated: