Coursedog

Submit a Ticket My Tickets
Welcome
Login  Sign up

Setting Up Roles in Catalog - All Catalogs


Table of Contents

Overview
Viewing Roles
Adding a Role
Different Role-Based Permissions
Related Articles

Overview

  • Coursedog allows institutions to set a variety of permissions by assigning roles to their users.

  • Each role can be configured to allow or limit access to Coursedog functionality across the Catalog platform, allowing you to differentiate between an admin that can edit the catalog directly and faculty that can only request changes to pages of the catalog.

  • There are several delivered user roles in Online Catalogs that you can select from, though you may choose to design and add a new role if one is needed.


Viewing Roles

On your dashboard, navigate to Catalog > Settings > Roles. 



Adding a Role

If your institution needs to add a new role, you can do so by selecting +ADD ROLE under the Roles tab. 


Different Role-Based Permissions

Overview | Best Practices | Pages (Standard/Contemporary) | Navigation 
Requests | Settings | Reports

Overview

  • You can view and edit permissions by clicking on the toggle next to each role name.

  • All permissions include “Allow” and “Deny” options. 

  • Some permissions also have an “Allow If” option, which is followed by a condition that must be met in order for a user with that role to have access to the listed functionality. 

  • The tables below detail the specific permissions that you can manage with roles.


Best Practices

If you give a role the ability to view or edit anything within settings, they will also need the “View Settings” permission. 


Pages (Standard/Contemporary)

Access

Description

Add Pages

  • Allows user to create new pages in a catalog. 

Edit Pages

  • Allows user to make changes to a catalog page directly.  

  • Any edits saved will immediately reflect in the catalog and will not go through an approval workflow.

Delete Pages

  • Allows use to delete pages. 

  • It is NOT recommended to give roles this permission. 

Requests Changes

  • Allows user to submit a Page Change Request.

Publish Pages

  • Allows user to Publish a page and make it visible in the catalog. 

Unpublish Pages

  • Allows user to Unpublish a page. 

  • This makes the page no longer visible in the catalog, but keeps the page in the inventory. 




Requests 

Access

Description

Archive Requests

  • Allows a user to archive a request.

Edit Requests

  • This grants a user the ability to edit ALL requests they have access to.

  • To restrict which proposals can be edited, utilize the "edit proposal" permission in workflows.

  • The author of the request can always edit the request regardless of permission settings.

View All Requests

  • Gives a user access to view every request made within an institution.

View Archived Requests

  • Allows a user to view archived requests.

Delete Requests

  • Allows a user to delete a request.

Edit Requests without Updating Workflow

  • Allows a user to edit requests without updating workflow.

Allow Additional Requests for In Flight Requests

  • Allows a user to request changes when a proposal is already in flight for the same page (see “Request Editing Permissions” below for more information).

  • If this is set to ALLOW, and multiple proposals are in flight, the second one will override the changes from the first one.

  • Best practice is to set this to DENY for all roles.

  • Setting this to DENY prevents overlapping proposals for the same page, which can lead to loss of approved changes due to conflicting proposed changes.


Settings

Access

Description

View Settings

  • Allows a user to view settings.

Edit Public Catalog Settings

  • Allows user to edit the catalog that is set as the Default catalog.

View Workflows

  • Allows a user to view workflows.

Edit Workflows

  • This allows a user to make edits to workflows.

  • Recommended for Super Admin and Admin only.

Update Workflows for In Flight Proposals

  • Setting this permission to “Allow” will give users the ability to click “Update Workflows for In-Flight Proposals” upon editing a workflow. 

  • If a user clicks “Update Workflows for Inflight Proposals” after making changes to a workflow, those changes will retroactively impact any in-progress requests that are not yet approved. 

  • If a user makes changes to a workflow – but this permission is set to “Deny” for their role – they won’t have the option to update workflows for inflight proposals.

View Roles

  • Allows a user to view roles.

Edit Roles

  • This allows a user to make edits to existing roles or create new roles.

  • Ability to create an Allow If conditional, specifying the allowed roles the user is allowed to edit. This allows a restriction where a user can edit Role X and Y, but not edit Role Z. If a user has restricted edit access to roles, they will see only a subset of those roles appear when they visit the Settings → Roles page

  • This permission should be set to “Allow” for Super Admins only and “Deny” for everyone else. 

Edit Workflow Notification Settings

  • This allows a user to edit workflow notification settings.

View Users

  • Allows a user to view users.

Edit Users

  • This allows a user to create, delete and edit Users.

  • This permission should be set to “Allow” for Super Admins only and “Deny” for everyone else. 

View Terms

  • Allows a user to view terms.

Edit Terms

  • This allows a user to edit terms.

  • Recommended for Admin only.

View Page Templates

  • Allows a user to view Page Templates.

Edit Page Templates

  • Allows a user to edit Page Templates.

View Search Configurations

  • Allows a user to view Sidebar Search Filters.

Edit Search Configurations

  • Allows a user to edit Sidebar Search Filters.

Edit Committees

  • Allows a user to edit Committee details other than its members. 

  • Recommend setting to DENY unless you wish to assign committees as page owners.

  • If set to “Allow”, the role will also need “View Committees” and “View Settings” permissions in order to edit committees.

  • Note that the "Allowed Roles" setting within a Committee's profile provides additional control as to which roles can edit a committee. A user must have a role with the "edit committees" permission and a role that is specified in "allowed roles" dropdown to edit the committee.

Edit Committee Members

  • Allows a user to edit Committee members. 

  • Recommend setting to DENY unless you wish to assign committees as page owners.

  • If set to “Allow”, the role will also need the “View Settings” permission in order to edit committees.

  • This allows a user to edit only the members + member workflow permissions in a committee, provided they are also listed in the committee's "Allowed Roles" dropdown. 

View Committees

  • Allows a user to view Committees. 

  • Recommend setting to DENY unless you wish to assign committees as page owners. 

  • If this is set to “Allow”, the role will also need the “View Settings” permission.


Reports

Access

Description

View Reports

  • Allows user to view "reports" in the left-hand navigation. 

Run Reports

  • Allows user to run a new scan/report. 

Edit Reports

  • Allows user to edit report settings, including which types of errors are scanned for by default and whether scans are run weekly or paused for each catalog. 



Related Articles

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.