-
Suggestion
-
Resolution: Duplicate
-
None
- duplicates
-
- Gathering Interest
- is cloned from
-
- Gathering Interest
[ACCESS-1204] Request to make changes to the email message sent when an account is deactivated
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| Link | New: This issue duplicates ACCESS-720 [ ACCESS-720 ] |
| Reporter | Original: André K. [ akasper ] | New: npv [ 07b65cdcf5f4 ] |
| Assignee | Original: Ilya Bagrak [ c6c23291180e ] |
| Description |
Original:
h3. 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: # The *Export accounts* feature inside the *Managed Accounts* # The Organization [get users REST endpoint|https://developer.atlassian.com/cloud/admin/organization/rest/#api-orgs-orgId-users-get] 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|https://developer.atlassian.com/cloud/admin/user-management/rest/#api-users-account-id-manage-lifecycle-disable-post]. h3. 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. h3. 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. |
New:
h3. Problem Definition
The email message sent during the time of user deactivation is too generic right now. h3. Suggested Solution Requesting for provisions to customise this message to include more information about the background of deactivation to keep the users better informed. |
| Link | New: This issue is cloned from ACCESS-720 [ ACCESS-720 ] |
Thanks everyone for watching and commenting on this ticket. As part of an initiative to better consolidate customer feedback, we are closing this ticket as a duplicate. Please vote, watch and comment on ACCESS-720 going forward.