Would it be possible to implement a feature that allows locking the configuration to a single user with write access for a defined time period?
In environments where multiple administrators manage an organisation, it can be problematic if two users submit configuration changes simultaneously, potentially leading to conflicts or unintended overrides. A temporary configuration lock would help ensure that only one administrator can make changes at a time while troubleshooting or implementing updates, reducing the risk of conflicting modifications.
This could be a time-based lock, either manually enabled or automatically released after a set period, ensuring workflow efficiency while maintaining control over configuration changes.
Would this be feasible for future development?