pelican-dev
Admin Roles
Uses spatie/laravel-permission to add roles and permissions (for admins). This does not change subuser permissions! (#193)
A role named "Root Admin" is created during seeding. This role has all permissions and will replace the old root_admin bool.
Example:
Looks good, Seems like we will have a lot of updating to do when we add this.
Things like "restore" & "force delete" aren't useful for us.
Looks good, Seems like we will have a lot of updating to do when we add this.
Yeah, we don't have any view pages for our resources. And we need to check all actions. (plus add any "special" permissions if needed)
Things like "restore" & "force delete" aren't useful for us.
True, I removed them.
We can still use root_admin, let's say we have a case where we have 2-3 administrators and one of them decides the invited user chooses to remove the original administrator and grief the entire panel, what do we do in that case?
We can still use root_admin, let's say we have a case where we have 2-3 administrators and one of them decides the invited user chooses to remove the original administrator and grief the entire panel, what do we do in that case?
The same you would now, create a new admin user via artisan cli.
Just having a duplicate and redundant root_admin wouldn't change that.