Growth Plays now validate permissions object by object, so users can work with only what they're responsible for.

Opening a Growth Play used to require management permission for every object type that might appear on the canvas, even if you only needed to manage one of them. A user responsible for Connections couldn't touch a Growth Play containing Segments unless they were also granted Segment permissions, forcing a choice between blocking access entirely or over-granting it.

Now permissions are checked per object. Anyone with the Growth Plays permission can open a play and see the full canvas: every node and relationship stays visible, so nothing looks broken or incomplete. Creating, editing, or deleting a specific object still requires permission for that object type; actions for object types you can't manage are hidden or disabled, and clicking one shows a clear permission message instead of an error.

Benefits:

• Opens Growth Plays to focused roles without requiring broad admin permissions
• Keeps the full canvas visible so context is never hidden, even for object types you can't edit
• Blocks edits to unauthorized object types automatically, with a clear message instead of an error
• Supports least-privilege access for teams where different people own different parts of a Growth Play

To learn more, read our documentation.