You must have full administrative permissions in your space to perform these steps. This means access to the Documents, Settings, and Users tabs.
This document explains how to add a user to your KB and grant them permissions consistent with your workflow. In the spirit of Best Practices, KB Admins control permissions to their KB Site. However, please be mindful that any user with the Users permission enabled may make changes to User permissions.
The image below shows 11 attributes to select.
Check this box: | To grant access to: | |
---|---|---|
1 | iKB | The internal KnowledgeBase |
2 | oDocs (Owner Docs) | Create, edit, and review Drafts and Active Docs owned by the user. |
3 | gDocs (Group Docs) | Create, edit, and review Drafts and Active Docs owned by any member of the group. |
4 | News | Post News items. |
5 | Topics | Create, edit, and delete Topics. |
6 | Settings | Access to most of the site administration functions. Note: Best Practices suggests access to the Settings tab is generally limited to only a few people per site. |
7 | Users | Add, delete, alter permissions for New users as well as Existing users. |
8 | Asst |
Add, delete, alter Assessment Modules. Note: The Assessment Tab is not enabled in the KB Admin Tools for groups that do not have any existing quiz/survey questions. Because of this, the Asst attribute will not appear for those groups. If your group would like to use the Assessment Tab features, reach out to kb-team@doit.wisc.edu to have the tab activated. |
9 | Stats | Access to info specifying which documents are being viewed on each site, etc. |
10 | Publish | Activate and deactivate documents on your site. |
11 | Tester | Test beta features on documents on your site. Please refer to [Link for document 93225 is unavailable at this time] for more information. |
OR Group Admins may select one of three quick-access buttons (located under the Tester field).
The image below shows the Tester field with the three buttons underneath; Select all access rights, Select default access rights, Deselect all access rights.
Select all access rights buttons - Checks the box in every permission listed in the above table
Select default access rights - Resets a user to the defaulted checked permissions: Active, iKB, OwnerDocs and GroupsDocs.
Deselect all access rights - Deselects all permissions that have been previously checked.
Determine what access you desite to grant and check the subsequent boxes.
Desired Access: | Check These Boxes: |
---|---|
Access to the internal KB (user can read docs on the KB but cannot create or edit documents). |
Check Active and iKB. Do NOT check oDocs nor gDocs. |
Create and edit only documents they own |
Check oDoc (as well as Active and iKB (for internal sites)) |
Create and edit documents owned by anyone in the group |
Check gDoc (as well as Active and iKB, and probably oDoc) |
Access the Topics, News, Settings, Users, Asst, or Stats tabs: | Check the corresponding checkbox. NOTE: Managers like to review stats, so be sure to give them access to this page. |
Publish documents (make documents active on either internal or external KB sites): |
Check Publish |
Test beta features on your KB Site (Please refer to [Link for document 93225 is unavailable at this time] for more information) : | Check Tester |
Be considered a KB Group Administrator | Check all available permissions (Active, iKB, ... Publish) |
If you begin to add a user who already belongs to another KB subsite, all their information will auto-fill. A line of text identifying what that user's current default group is will appear next to the NetID field, which will read:
FirstName LastName's default group space: KB Subsite Name
KB Admins will easily determine the other KB group in which their new user exists. The KB Admin can then contact that Group, should the user need to be removed (e.g. if the default group list a a department where the new user had worked with in the past). Or, KB Admin(s) may ask their new user to update their own Default KB space.