Warn sysadmins to check Business Process ownership when revoking a user's system administrator permission
Please modify the 'Revoke system administrator' task (RecordOperation 'Application User: Revoke System Administrator') so that it gives a warning akin to 'Warning: If this user owns any Business Processes those processes may stop working. Check the Business Process Ownership tab. Do you want to proceed?'
Alternatively, consider renaming the Task as 'Revoke system administrator (warning: may stop owned Business Processes working)'.
These ideas are to stop other organisations going through the massive uncertainty, frustration and potential effects on revenue and supporter communications which we recently experienced when dozens of core Business Processes stopped working for no apparent reason and it took us three weeks to understand which processes had been affected, work out why and to clean up the damage.
-
David Wanless
- May 25 2022
- Reviewed: Voting Open
| Organization Name (Please enter full organization name) | The Wilderness Society Ltd (Australia) |
| Reported Version | 4.0 |
Related ideas
You are not alone. We have had this happen to us at The Nature Conservancy as well, though we figured it out quicker. I would say this idea bank item is great to have a warning at the very least, but really there should be no tie between the permissions of the business owner and the running of essential business processes. Staff responsibilities change over time and changes to their permissions should not impact processes they set up in their time as a system admin.