Lock Expiry Date Field in Pod Workflows Post-Review
We need to ensure expiry dates in Pod workflows remain accurate and compliant by preventing unauthorised edits after review. Currently, users can change the expiry date field even after it has been reviewed, which risks compliance issues and undermines governance efforts.
Please implement a lock on the expiry date field once a designated reviewer (e.g. Marketing Compliance) has completed their step in the workflow. This will:
- Prevent accidental or unauthorised changes
- Reduce manual monitoring
- Support consistent asset governance
If full lockdown isn’t feasible, a conditional lock or warning prompt would be a helpful interim solution.
9
votes

-
Sara-Jayne Reid commented
To support requirements for Financial Services clients, this is a critical requirement