KB User's Guide - Users Tab - Group Authorization
This document describes how to create User Group Authorization rules in order to grant a select group automated read access to either your Live internal KB site or read and write access to a specific KB documents.
Creating an Authorized Group
In the KB Admin Tools, go to the Users tab > Group Authorization link. The image below shows the User Group Authorization screen.
From the User Group Authorization screen, enter a Group authorization name.
Specify the Scope from the dropdown list
Internal site: Allows users that the meet the rule criteria to log in to the Internal Live KB site. These users will have the same level of access as a user account that has the "Internal KB" ("iKB") permission under the Users tab.
Document specific: The group will appear as a option under the WriteAccess and ReadAccess sections of the document editor screen. Users to whom the rule applies will gain read and/or write access to the documents associated with the group.
Note: For group-authorized WriteAccess to work, the user will first need to have a user account in your space with basic author permissions.
For group-authorized ReadAccess to work, the user will first need to have a user account in your space with Internal site access, or they need to meet the criteria for a separate "Internal site" scoped authorization rule.
Enter an Attribute name. Please see the Rule Attributes section for guidance on what attributes can be used.
Choose a Condition from the dropdown list (e.g. is equal to, starts with, contains)
Add the desired Attribute value.
The Active checkbox is enabled by default.
Finally, click on the Add button to save the Group Authorization entry you just created.
Read-only access based on Unit Division Department Sub-department (UDDS) numbers, or any other Shibboleth attribute, can be granted.
The Manifest service is recommended for UW-Madison KB groups who wish to provide access based on UDDS or student affiliation data. For information on setting up and configuring a Manifest group for use with the KB, please see KB User's Guide - Using Manifest to Authorize Users for the KB.
Shibboleth attributes may be used for some data that is not covered by Manifest, though uses are more limited.
Note: For institutions outside of UW-Madison, additional work must be performed to map a specific Shibboleth attribute to the KB for use with Group Authorization. Please contact email@example.com to request a new attribute.
The examples below demonstrate different attributes used for Group Authorization.
isMemberOf attribute grants members of the "uw:domain:kb.wisc.edu:help_desk_west" Manifest group authorization.
eppn (eduPersonPrincipalName) attribute grants authorization to the institution domain "uchicago.edu".
wiscEduUDDS attribute grants all members under the UDDS code
- Note: Manifest UDDS group membership is now recommended instead of the wiscEduUDDS attribute.
Updating Group Authorization Scope
Updating an existing Group Authorization rule and changing the Scope dropdown from Document specific to Internal site will result in the following alert:
Note that updating a Group Authorization rule's scope to Internal site will remove all document specific read and write access restrictions associated with that rule. If this is not the intended outcome, click OK to dismiss the popup and change the Scope dropdown back to Document specific.
If you wish to experiment with Group Authorization rules but do not wish to remove document specific restrictions, consider changing the attribute name, condition, and value instead, or create a new rule entirely.
Deleting Group Authorization Rules
To delete a Group Authorization Rule, click the Delete button corresponding the the desired rule. A dialog window will popup confirming you would like to delete this rule. Note that deleting a Group Authorization rule will remove all read and write restrictions associated with it.
Click OK to confirm the deletion.
When a user stops meeting the criteria for a rule (e.g. the user gets another position or leaves your institution entirely) they will lose access to your Internal KB site and/or the documents they were being authorized for.
There is no limit to the number of Group Authorization rules that can be created for a single KB space.
There is no conflict if a user who has been manually entered into the Users tab of the KB Admin Tools is also a member of an Authorized Group. Any elevated permissions set via the Existing Users list will be honored.
There may be occasion for a KB group admin or author to collaborate with a member of an Authorized Group who is a content expert. However, if that individual is not in the Users list, they will be unable to access the KB Admin Tools to view draft (In Progress or In Review) documents. To remedy this, you may create a privately shared link to share one or many unpublished documents with a member of an Authorized Group. Should it be more practical for the content expert to edit the document, the KB group admin need only add the user to the KB.