In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds:
Our developers need Page Builder access to create and manage Apps/Boards for model building and enhancements. This is primarily a development capability, and we understand the need for Create / Read / Update permissions to support this work.
However, Page Builder is currently a tenant-level role (not workspace-specific), so granting it provides access across Dev, Test, and Prod. In addition, Page Builder includes elevated capabilities such as:
- Changing/revoking page access for users
- Moving pages
- Deleting pages
These actions -especially Delete in Production workspaces - create significant risk of accidental impact to business users and live content.
How often is this impacting your users?
Anytime developers need to build or update Apps/Boards, we must grant tenant-level Page Builder access, which unintentionally includes Production.
Who is this impacting?
- Developers / Model builders
- Solution architects / Admins
- Business/end users (indirectly, due to potential accidental changes in Prod)
What would your ideal solution be? How would it add value to your current experience?
Please enhance Page Builder to be more workspace specific instead of tenant specific.
This would let us grant Page Builder access to developers in Dev and Test while avoiding Production workspaces exposure and reducing the likelihood of mishaps.
