Your idea is very useful! Determining a expiration date for secrets and having reminder notifications can prevent unexpected errors and improve security management. This avoids downtime by reminding users before secrets expires and helping the teams to be active instead of responding to errors, this increases the security of regular updates. But I have a concern that might require additional system resources to track and send a reminder, and if too much more reminders are sent, it can be heavy for users. Sometimes a customizable notification help balance the reminder? What do you think? 

Great idea. Yes this will definitely help for API keys and other secrets that may expire in a fixed time frame. 

@Sriyamini this can be done with a set expiry flag the it will be limited to traking only aite properties with an exipry

@TheSubuIyer it is  nice point because the expiry flag helps limit tracking to only relevant Site Properties. I think adding an option for customizable notifications will help strike a balance between reminders and avoiding too many alerts. 

This is a great idea! Adding an optional expiry date with customizable reminders will help teams stay proactive and avoid disruptions. It also improves security by encouraging timely updates of secrets without overwhelming users