Comment on page
This feature allows you to map a Discord Role to a Sobol User Permission. Use the following commands to map the roles to those permissions:
1. Read Only: Member can only view and navigate map
2. Regular: Member can edit Sobol member profile and contribute to workstreams
3. Admin: User can add/edit/delete member profiles and Teams. Full add/edit/delete access to Sobol instance. Admin should only be granted to a small handful of trusted members of your Discord.
/user-map add-readonly @everyone
You can map multiple Discord Roles to a given Sobol User Permission by running these commands multiple times. When you are finished, you can review the mapping by running:
You can also remove any role from the mapping by running:
Important: Don’t forget to add an admin role that you have or your Sobol user will be archived or demoted.
How are these roles used?: In BanklessDAO, for instance, Level 1 users in Bankless DAO are given "Regular"-level permissions in Sobol. "Admin"-level permissions are given to "Sobol Editor", "Cartographer", and server admins. "Read-only" perms are given to "Guest Pass" members in Bankless DAO.
Note: Anyone with a Discord Role corresponding to a Sobol User Permission will be automatically added to Sobol with the highest permission level available to them. If someone loses all Discord Roles with permissions or leaves the Discord Server, their Sobol User will be archived and they will lose access to the Sobol Organization.
When you are ready to being provisioning, run the following:
The bot will then start synchronizing all Discord Users with roles that are mapped to Sobol User Permissions. You can update the mapping at any time and it will update all Sobol Users accordingly.
You can pause synchronization at anytime using the following command:
Tip: If your Discord server has a lot of users (hundreds and thousands), use
/sync stopto pause synchronization when you are editing mappings using the
/team-mapcommands to avoid lag. Remember to re-enable synchronization with
/sync startafter you're done.
You can force a full resynchronization in the event of mismatches using the following command:
You can also force an individual resynchronize in the event of a single mismatch using the following command: