More specific edit permissions in Avo
k
klara@avo.sh
Enable admins to define more specific permissions on what edits users can make, so we can clearly separate “safe” changes from structural taxonomy changes.
Distinguish between:
- Low-risk changes (should be broadly allowed):
- Adding or updating allowed values on existing properties.
- Updating descriptions / implementation notes.
- Managing how existing events and properties are used (e.g. in Journeys).
vs.
- High-impact structural changes (should be restricted):
- Creating new events.
- Adding new properties to existing events.
- Changing event/property names, types, or core structure.
Concretely, this would mean roles where a user can:
- Can add/modify allowed values on approved properties.
- Can configure journeys using existing events/properties.
- Cannot create new events.
- Cannot add new properties or otherwise change event structure.
This would let more people self-serve on day-to-day usage details (like new allowed values) without opening up full control over the taxonomy schema.