Create new settings logic and architecture for applying cascading behaviors or features
Problem
Investigate a system to allow enforcement of features and behaviors globally in an organization.
In our current architecture, settings generally exist only at the object level. We would like to create a system that allows for a uniform enforcement of features to all objects in an organization based on an inheritance model. The assumption is that this would reduce inconsistent behavior, and allow for easier enforcement of controls within an organization at a single point, rather than individually at every object.
JTBD
I want to enforce a standardized feature in my organization to maintain uniform practices for groups and projects so that we can reduce confusion, and ensure security and compliance.
Concerns
A visual representation of one example where this feature would cause complications or an extra level of configuration. Default status should be off to allow maintaining of current settings with out breaking anything.
User experience goal
- A group admin/owner should be able to enforce a settings behavior at the top level of an org which would filter down to every
sub group/project. - A group admin/owner should also be able to import/export these settings to other groups/projects/workspaces.
✏ ️ Figma work file
Proposal
Currently we are working off an iteration using the idea of enforcing project deletion behavior. However this should be given consideration to other places this sort of logic can work.
- evaluate settings to see what can be controlled via this single point.
- evaluate where this new UI component would live.
- produce visuals for feedback
- iterate with various settings
What does success look like, and how can we measure that?
TBD