Ops User Roles

Permissions within Content Hub Ops are granted based on user role (also called user type) through assignment to a user group. If a user can’t do something they would expect to be able to do in the system, it is likely a matter of permissions or their assigned role(s). The user should contact the UCAM platforms group and describe the issue to assist in diagnosing the problem.

User Groups

There are multiple role-based permission sets that can be granted to users for Ops-related activities within Content Hub. These permission sets are granted by assigning a user to a user group that has been granted the permissions. Users can have multiple roles applied to their account by including the user in multiple user groups. Expand the tabs below to learn about the key responsibilities and permissions granted for each user group.

Content Authors Team (Staff)

Key responsibilities:
- Responsible for creating, authoring and publishing all content sub-types, except Statements. Statements are only created by Issues Team user group members.
Permissions:
- Can create, author and publish all content sub-types, except for Statements.
- Can create, edit and publish all components.
- Can edit and delete content that is "In Progress," "In Review" and in “Pre-publishing" status for all sub-types except Statements.
- Have read-only access to other content types, in any status, except for Statements. The Statements sub-type will be only viewable by the Issues Team until published/final. Published/final statements are viewable read-only for content authors.
- Can transition content workflows when assigned.
- Can add assets (approved DAM assets) as attachments and upload brief files to content.
- Can create new public links but cannot edit or delete others’ public links

Content Authors Team (Student Workers)

Key responsibilities:
- Responsible for creating and developing content items for content sub-types included in the Main and Campus story workflows
- Must identify a Staff Publisher (field requirement) from the Content Authors Team (Staff) for preparing for validating the taxonomy and publishing content.
Permissions:
- Can create and author content sub-types within the Main and Campus Story workflows, except for Statements
- Can create, edit and publish components
- Can edit content items with a status of “In Progress” and “In Review” for content sub-types within the Main and Campus Story workflows, except for Statements
- Have read-only access to other content items, in any status, except Statements
- Can add approved assets from the DAM as attachments to content
- Can upload brief files to content
- Can create new public links but cannot edit or delete others’ public links

Note: The Main Workflow applies to the following content sub-types: Ask the Expert; Expert Advisories; Media Advisories; News Release; Voices/Views Faculty; Voices/Views Graduate; Voices/Views Staff; and Voices/Views Student.

Reviewers Team (Stories)

The Reviewers field is a required field completed when transitioning a content item’s workflow status from “In Progress” to “In Review.” This user group is used to segment out users who can be assigned as a Reviewer in the dynamic user assignment for the “Stories workflow 1 (News releases, etc.)” workflow.
This user group should be used in combination with “Content Authors (Staff)” user group membership.
Key responsibilities:
- The Reviewer user is dynamically assigned, based on the content creator’s choice in the Reviewer field.
- The assigned Reviewer is responsible for reviewing content items for content sub-types in the “Stories workflow 1 (News releases, etc.)” workflow.
Permissions:
- This role does not contain specific role permissions.

MSUToday Team (Staff)

This user group will be used as a fixed user group assignment as part of the Campus Story and Podcast workflows.
Users that are members of MSUToday Team (Staff) are Content Admins. The MSUToday Team (Staff) user group should be used in combination with the Content Admins group membership.
Key responsibilities:
- Review content submitted as part of the “Stories workflow 2 (Campus Story)” and “Stories workflow 5 (Podcasts)” workflows.
Permissions:
- This role does not contain specific role permissions.

Note: The Campus Story and Podcast workflows apply only to the Campus Story and Podcasts content sub-types, respectively.

MSUToday Team (Student Workers)

Key responsibilities:
- Responsible for creating and developing content items for content sub-types included in the Main and Campus story workflows
- Must identify a Staff Publisher (field requirement) from the Content Authors Team (Staff) for preparing for validating the taxonomy and publishing content.
Permissions:
- Can create and author content sub-types within the Main and Campus Story workflows, except for Statements
- Can create, edit and publish components
- Can edit content items with a status of “In Progress” and “In Review” for content sub-types within the Main and Campus Story workflows, except for Statements
- Can add approved assets from the DAM as attachments to content
- Can upload brief files to content
- Can create new public links but cannot edit or delete others’ public links

Note: The Campus Story Workflow applies only to the Campus Story content sub-type.

Editing Team

This user group will be used as a fixed user group assignment as part of the Main Workflow and Photo Gallery Workflow.
This user group should be used in combination with “Content Authors Team (Staff)” user group membership.
Key responsibilities:
- The Editing Team user group is responsible for editing content items for content sub-types included in the Main Workflow and Photo Gallery Workflow.
- Users in the Editing Team user group have the same permissions as Content Authors Team (Staff) user group members.
Permissions:
- This role does not contain specific role permissions.

Issues Team

This role policy user group only contains a limited sub-set of permissions.
This user group should be used in combination with the “Content Authors Team (Staff)” user group membership.
Key responsibilities:
- Issues Team group members are responsible for creating, editing, collaborating and publishing Statements. Only Issues Team group members can view or edit Statements prior to publishing. Statements route through the “Stories workflow 4 (Statements)” workflow.
Permissions:
- Read, create and edit content items for the Statements content sub-type that are in a status of “In Progress” or “In Review”

Note: The “Stories workflow 4 (Statements)” workflow applies only to the Statements content sub-type.

Content Admins

Key responsibilities:
- Content Admins have full access to view, edit, create and delete all content items for any content sub-types, except Statements. Statements are visible only to Issues Team user group members prior to publishing.
Permissions:
- Full permission to read, edit, create and delete all content, except Statements
- Access to Content Mass Edit page, Strategy page and Reporting page
- Manage Campaigns and People directory
- Manage and transition all workflows for all content types
- Manage (create, read, update, delete) all comments and annotations on all content types
- Add approved DAM assets as attachments to content
- Upload brief files as attachments to content
- Use, read, create, edit and delete all public links
- Read, create, update and delete Content Tags