Plugins 3.3: Roles
Plugins 3.3 brings support for permissions-based access, unlocking Plugins for more users across your team. Plugin builders can now control access to individual features based on the user’s role—whether they’re a viewer, editor, or limited by plan. Designers can use Plugins without needing Deploy access, and CMS editors can sync collections without full design permissions. Since most Plugins don’t require Deploy access, this update makes them accessible to everyone. We’re also introducing APIs for both REM and Vector Sets.
Plugins 3.3 brings support for permissions-based access, unlocking Plugins for more users across your team. Plugin builders can now control access to individual features based on the user’s role—whether they’re a viewer, editor, or limited by plan. Designers can use Plugins without needing Deploy access, and CMS editors can sync collections without full design permissions. Since most Plugins don’t require Deploy access, this update makes them accessible to everyone. We’re also introducing APIs for both REM and Vector Sets.
Plugins 3.3 brings support for permissions-based access, unlocking Plugins for more users across your team. Plugin builders can now control access to individual features based on the user’s role—whether they’re a viewer, editor, or limited by plan. Designers can use Plugins without needing Deploy access, and CMS editors can sync collections without full design permissions. Since most Plugins don’t require Deploy access, this update makes them accessible to everyone. We’re also introducing APIs for both REM and Vector Sets.