| Info |
|---|
Approved for Confluence Data Center |
Simple add-on to remove License for Inactive users and Deactivate or remove Security access groups for users who left organization.
Use Cases:
- To Remove License for Confluence users who are Never Login or Not active.
- To Deactivate or Remove License Access Security Groups for Confluence users who left company or Not exists in organization directory.
- To restore license Or Grant Access on Successful Login attempt.
- To Search inactive users certain number of days and export to CSV.
Features:
- All Atlassian provided user directories are supported.
- Supports custom remote external Directories.
- Option to choose multiple User Directories to process users.
- Option to process users from specific groups.
- Option to skip users from specific groups.
- Option to rename Deactivated user to {username}_inactive_yyyyMMdd
- Useful REST APIs
- Also available for Cloud hosting:
| Info |
|---|
Top Users |
| Info |
|---|
Quick Start Steps. |
Here is Quick Start Steps to start using this plugin.
| Status | ||||||
|---|---|---|---|---|---|---|
|
Go to, System General Configuration > Click Manage Inactive Users
| Info | ||
|---|---|---|
| ||
Configuration to Remove License or Access Security Groups for Confluence users who are Never Login or Not active. |
Manage Inactive Confluence Users
| Status | ||||||
|---|---|---|---|---|---|---|
|
| Info | ||
|---|---|---|
| ||
Configuration to Deactivate and Access Security Groups for Jira users who left company or Not exists in organization directory. It validates user status in remote user directory. |
Manage Former X Confluence Users
| Status | ||||||
|---|---|---|---|---|---|---|
|
To Debug Manage Inactive Users App:
Go to, System General Configuration > Logging and profiling > Add New Entry
| Code Block |
|---|
Class/Package Name: com.tse.confluence.deactivateusers.plugin Level: Debug |
Click Add.
| Status | ||||||
|---|---|---|---|---|---|---|
|
- Known Confluence product bug:
- On Confluence restart, if any custom schedule settings are reverted to default but still schedule runs with default settings.
- Workaround, you need to re-save the custom settings. See, https://jira.atlassian.com/browse/CONFSERVER-55455