is the concept of Personal Overrides outdated in the Machine Identities world? i.e. since I can't tie a machine identity to a user what's the recommended approach for user-specific overrides of keys?

Hi @Jordan Singer! Personal Overrides are a user-level feature. They let individual developers override shared secret values for their own local dev workflow (e.g. via the dashboard or CLI when logged in as yourself). They're intentionally not available for Machine Identities, since machine identities represent workloads/applications, not individual people. If you need different secret values per context with machine identities, the recommended approach is to use separate folders or environments (e.g.

/dev/jake

,

/dev/alice

) and scope each identity's role to its path. That gives you the same "override" effect with proper access control. Let me know if you have any other questions! Thanks