A Robust Security and Permissions Model

Implementing a new, powerful tool like Display Builder across an enterprise like UI Suite requires a robust security model. We've been very pleased with the granular control that Display Builder offers, which allows us to enforce our security policies effectively while still empowering our teams.

Access is governed by a two-tiered permission system. First, to even enter a Display Builder instance, a user must have the specific permission associated with that builder's profile (e.g., "Use 'Marketer' display builder profile"). This is our first line of defense. Second, they still need the underlying Drupal permission for the content they are editing, such as `Administer display` for entity displays or `Administer page layouts` for page layouts.

This dual-permission check, enforced by access control handlers at both the page access and API levels, ensures that users can only edit displays they are explicitly authorized to manage. By creating different profiles and assigning their permissions to different roles, we can carefully control who can build what, and what tools they have at their disposal. This layered approach to security gives our administrators peace of mind while rolling out this powerful new functionality.