The Complete Strapi™ Course with Plugins and Deployment - Admin RBAC: Restricting Plugin Use to Specific Roles

The video tutorial explores how to implement role-based access control (RBAC) in Strappy, focusing on setting up granular permissions for plugins. It covers the process of editing the bootstrap.js file to register actions and permissions, and how these can be used to control access to specific routes and menu items. The tutorial also discusses the limitations of the community edition of Strappy, particularly in terms of editing permissions for different roles. Finally, it demonstrates testing the setup by inviting a new user and verifying the visibility of plugin links based on roles.

What is a limitation of the community edition of Strappy regarding role-based access control?

• It cannot be used for commercial purposes.

• It allows only one admin user.

• It does not support any plugins.

• It has limited control over user roles and permissions.

What file must be edited to set up more granular control on admin user actions?

• index.html

• bootstrap.js

• server.js

• config.js

What is the purpose of creating a role-based access control actions array?

• To store user data

• To log user activities

• To define permissions for plugin functionalities

• To manage server configurations

What key is used to specify the tab where actions should be shown in the admin panel?

• pluginName

• UID

• section

• displayName

How can you ensure a menu item is only visible to users with specific permissions?

• By setting a password

• By deleting the menu item for unauthorized users

• By using a permissions key in the menu item registration

• By hiding the menu item in CSS

Why can't the Super Admin permissions be edited in the community edition of Strappy?

• Because they are hardcoded

• For security reasons

• Due to a software bug

• Because they are not needed

What happens if you comment out the permissions part in the admin index file?

• The plugin becomes invisible to all users

• The plugin stops working

• The plugin becomes visible to all users

• The plugin gets deleted

What is the result of setting a permission for a plugin in the community edition?

• It restricts access to only Super Admins

• It allows all users to access the plugin

• It has no effect

• It causes an error

What role was used to test the visibility of the GitHub Projects plugin?

• Viewer

• Contributor

• Author

• Editor

What is the outcome when an editor tries to access the GitHub Projects plugin without the necessary permissions?

• The editor can access and use the plugin

• The editor cannot see the plugin

• The editor receives an error message

• The editor is logged out