This onboarding guide covers the early access for enabling permissions in project policies to restrict access to project map nodes and compositions based on their location in the the project map.

Key benefits:

• Grant or restrict access to project map nodes and their compositions based on the location in the project map
• Protect important project map nodes from accidental edits, deletions or other operations that may break your website
• More granular permissions for project map nodes: Read, Create, Edit, Delete
• Restrict which types of compositions or composition patterns can be created based on the location in the project map

https://www.loom.com/share/ec081570709349a8bae7f48d2c8ea25e

🚀 Quick-start

Prerequisites:

• Share your Uniform team ID with your main Uniform contact so we can enable the feature.

  We’ll confirm once it’s turned on for your account.

• Optional: Schedule an onboarding call with our team if you want some help with onboarding

Product chat about permissions in Uniform | Richard Bausek | Cal.com

Getting started

Please check out the documentation to learn how to set up project map permissions: 📚 Documentation and use case example

💬 What kind of feedback are we looking for

As an early adopter, we’d love your input on:

• How do you want to set up governance and permissions around your project map structure?
• Does this cover what you need in order to govern specific branches of your project map? Where does it fall short?
• What would you change, add, or remove?