mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 00:29:48 +03:00
Assing role to multiple people #2084
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sharma-akshay on GitHub (Feb 9, 2021).
Hi,
I have a Bookstack instance and by default I am assigning "Viewer" role to all team members on sign-in using SSO. However I have created a new role "New_Role" and I want to assing this role to multiple people. I have atleast 200 users, out of which I want to assign this role to some 60-70 members. One way I see to do this is to login as admin and go to each user profile and manually add this role to them, but this is a hectic way.
Is there a way I can do it automatically by running some query or script. I have email Id's of all the users to whom I want to add this custom role.
Please help.
@cdrfun commented on GitHub (Feb 9, 2021):
Depending on your SQL knowledge this could be done directly on the database, but Bookstack doesn't offer a native solution imho.
As far as I remember you have to fill the
role_usertable and run thephp artisan bookstack:regenerate-permissionscommand afterwards. You should definitely make sure you have working backups before fiddling with the database directly.@Mynster9361 commented on GitHub (Apr 14, 2021):
Depending on what you are using for SSO and you already have the users you would like in the group you can sync the groups to each other.
In my instance i use Azure and you can setup the group sync by doing the following:
Create the group and write down the Object ID
Go to Roles in your bookstack instance and insert the Obejct ID into External Authentication ID
You will also need to add the following to your .env file in the bookstack directory
The groups link is not there by default so you will need to add it to your application
@ssddanbrown commented on GitHub (Aug 22, 2021):
Thank you @cdrfun and @Mynster9361 for providing detailed answers to this. Will therefore close this off.