browse_admin
: Whether or not the user may browse the Voyager admin panel.browse_database
: Whether or not the user may browse the Voyager database menu section.browse_bread
: Whether or not the user may browse the Voyager BREAD menu section.browse_media
: Whether or not the user may browse the Voyager media section.browse_menu
: Whether or not the user may browse the Voyager menu section.browse_settings
: Whether or not the user may browse the Voyager settings section.read_settings
: Whether or not the user can view or see a particular setting.edit_settings
: Whether or not the user can edit a particular setting.add_settings
: Whether or not the user can add a new setting.delete_settings
: Whether or not the user can delete a particular setting.Generate permissions
for every BREAD type you create. This will create the browse
, read
, edit
, add
and delete
permission.products
table. If we choose to Generate permissions
for our products
table. Our permission keys will be browse_products
, read_products
, edit_products
, add_products
and delete_products
.browse
permission, for example for the Posts
BREAD menu item, it will check for the browse_posts
permission. If the user does not have the required permission, that menu item will be hidden./admin/
. So for a custom page of the form /admin/sub/foo
the menu item will not be hidden from the menu.TCG\Voyager\Models\Permission
). The column table_name
should be set to null. The column key
should be of the form browse_slug
where slug
has to be replaced with the actual slug of your custom page. For example, to restrict access to your custom page with url /admin/create_bill
you may create the permission browse_create_bill
.admin/roles
. In the above example you would find a new checkbox called "Browse Create Bill". If a user does not have the required permission, the menu item leading to your custom page will be hidden.authorize
in your controller:browse_posts
, simple enough we can use the following syntax: