Jump to HeaderJump to Main ContentJump to Footer
Michigan State University
Michigan State University
Digital Experience Studio

University Communications and Marketing

Digital Experience Studio

  • Experience Program
    • Website Project Process
    • Working with a Vendor
    • Glossary
    • Taxonomy Data Dictionary
  • |
  • Experience Design
    • Website Strategy
    • Website Structure
    • Information Architecture and Navigation
    • User-Centered Design Conventions
    • Common UX Issues
    • Enterprise Design System
    • Content Planning
    • Creating Accessible Content
    • Taxonomy and Filters
  • |
  • Website Technology
    • Web Standards
    • Search Engine Optimization
    • Cascade CMS
    • Sitecore CMS
    • Content Hub Overview
    • Content Hub DAM
    • Content Hub Operations

    SitecoreAI

    Sitecore user login
  • |
  • Social Media
    • Alt Text Bookmarklet
    • Meta Ad Pixel
    • Social Media and Web Integration
    • Sprinklr

    Sprinklr

    Sprinklr user login
  • |
  • Analytics
    • Google Analytics (GA4)
    • Testing
    • Data Visualization

    Google Analytics

    Google Analytics user login
  • |
  • News and Events
    • News and Updates
    • Events and Trainings
Digital Experience Studio

University Communications and Marketing

  • Experience Program
  • Experience Design
  • Website Technology
  • Social Media
  • Analytics
  • News and Events

< Experience Program

  • Website Project Process
  • Working with a Vendor
  • Glossary
  • Taxonomy Data Dictionary

< Experience Design

  • Website Strategy
  • Website Structure
  • Information Architecture and Navigation
  • User-Centered Design Conventions
  • Common UX Issues
  • Enterprise Design System
  • Content Planning
  • Creating Accessible Content
  • Taxonomy and Filters

< Website Technology

  • Web Standards
  • Search Engine Optimization
  • Cascade CMS
  • Sitecore CMS
  • Content Hub Overview
  • Content Hub DAM
  • Content Hub Operations

SitecoreAI

Sitecore user login

< Social Media

  • Alt Text Bookmarklet
  • Meta Ad Pixel
  • Social Media and Web Integration
  • Sprinklr

Sprinklr

Sprinklr user login

< Analytics

  • Google Analytics (GA4)
  • Testing
  • Data Visualization

Google Analytics

Google Analytics user login

< News and Events

  • News and Updates
  • Events and Trainings
Digital Experience Studio > Website Technology > Content Hub >

Asset Visibility Groups

MSU Tools and Resources

  • A to Z Index
  • Find People
  • Email
  • Tech Support
  • Social Media Directory

Communications Resources

  • University Communications and Marketing
  • University Trademarks and Licensing
  • MSU Brand Studio
  • MSU Editorial Style Guide
  • MSU Photos

Contact us

517-355-7505

Address

Michigan State University 408 West Circle Drive East Lansing, MI 48824

Follow Us

  • Visit our Facebook page
  • Visit our page on X
  • Visit our Instagram page
  • Visit our LinkedIn page
  • Visit our YouTube page
  • Visit our TikTok page

If you're having accessibility issues, please let us know.

Know MoreTransparency Reporting: Budget & Salary/Compensation
  • Contact Information|
  • Site Map|
  • Privacy Statement|
  • Site Accessibility|
  • Call MSU: (517) 355-1855|
  • Visit: msu.edu|
  • Notice of Nondiscrimination|

SPARTANS WILL|© Michigan State University|

Asset Visibility Groups

University Communications and Marketing uses a visibility restriction function to limit access of specific assets to specified functional groups. See "Restricting Asset Visibility" for more information on this workflow. This workflow requires the establishment of functional user groups. Functional user groups can be created by admins.

Creating Asset Visibility Functional Groups

There are four general steps needed to establish functional groups for controlled visibility. The instructions for creating these groups are below.

Step 1: Create the Functional Group
  1. Log in to Content Hub.
  2. Click the gear icon to open the Manage page.
  3. Click the Taxonomy tile.
  4. Navigate to and click the name MSU.FunctionalGroup in the list of taxonomies.
  5. Click the “+” icon to add a new functional group to the list.
  6. Fill in the fields to create the new group:
    1. Name — The name of the group; no special characters are allowed.
    2. Label — What will be visible to users.
    3. Identifier — This will automatically populate based on the name.
    4. Synonyms — Optional.
    5. Description — Optional, but it is a best practice to complete this information.
  7. Click Save.

 

Documentation updated: June 14, 2025

Is there an issue with this documentation? Report it here.

Step 2: Create the Viewing User Group
  1. Click the gear icon to return to the Manage page.
  2. Click the Users tile.
  3. Click the User groups tab on the Users page.
  4. Click the “+ Usergroup” button to add a user group.
  5. Fill in the Usergroup properties options, as needed. 

Note: Make the use of the group clear in the name. Follow the naming convention of “Functional Group – Insert Group Here.” For example, “Functional Group – Executive Communications.” 

  1. Click Save.
  2. Click the left arrow icon next to the group name to return to the User groups tab on the Users page.
  3. Find the user group in the list. Click the gear icon to open the Policies page for the group.
  4. Click New rule button.
  5. Check the State (M.Automation.State), State flow (M.Automation.StateMachine) and Transition (M.Automation.Route) options in the list and click OK.
  6. Assign the following permissions by checking the box next to their label:
    1. Read
  7. Click Add condition next to the Rule name.
  8. In the “Choose definition” drop-down, select State (M.Automation.State) and click Select.
  9. Check Restricted Visibility and Unrestricted Visibility in the list of options and click Select.
  10. Click New rule button.
  11. Check the Asset (M.Asset) and File (M.File) options in the list and click OK.
  12. Assign the following permissions by checking the box next to their label.
    1. Read
    2. Order
    3. ReadAnnotations
    4. CreateDiscussion
    5. DownloadUserRenditions
    6. DownloadOriginal
    7. DownloadPreview
    8. ReadPublicLinks
    9. CreateAnnotations
  13. Click Add condition next to the Rule name.
  14. In the “Choose definition” drop-down, select Content Repository (M.ContentRepository) and click Select.
  15. Check Standard in the list of options and click Select.
  16. Click Add condition next to the Rule name.
  17. In the “Choose definition” drop-down, select Functional Group (MSU.FunctionalGroup) and click Select.
  18. Check the name of the appropriate functional group and click Select.
  19. Click Save.
Visibility group permission settings example
Fig. 1: The settings for the Viewers functional user group should resemble the above. The only changes that should be made to the above conditions are that the MSU.FunctionalGroup condition should match the functional group you just created.
Step 3: Create the Validation User Group
  1. Click the gear icon to return to the Manage page.
  2. Click the Users tile.
  3. Click the User groups tab on the Users page.
  4. Click the “+ Usergroup” button to add a user group.
  5. Fill in the Usergroup properties options, as needed. 

 Note: Make the use of the group clear in the name. Follow the naming convention of “Functional Group – Insert Group Here.” For example, “Functional Group – Executive Communications Validator.” 

  1. Click Save.
  2. Click the left arrow icon next to the group name to return to the User groups tab on the Users page.
  3. Find the user group in the list. Click the gear icon to open the Policies page for the group.
  4. Click New rule button.
  5. Check the State (M.Automation.State), State flow (M.Automation.StateMachine) and Transition (M.Automation.Route) options in the list and click OK.
  6. Assign the following permissions by checking the box next to their label:
    1. Read
  7. Click Add condition next to the Rule name.
  8. In the “Choose definition” drop-down, select State (M.Automation.State) and click Select.
  9. Check Restricted Visibility and Unrestricted Visibility in the list of options and click Select.
  10. Click New rule button.
  11. Check the Asset (M.Asset) and File (M.File) options in the list and click OK.
  12. Assign the following permissions by checking the box next to their label:
    1. Read
    2. Approve
    3. Order
    4. ReadAnnotations
    5. CreateDiscussion
    6. DownloadUserRenditions
    7. DownloadOriginal
    8. CreatePublicLinks
    9. Update
    10. Submit
    11. DownloadPreview
    12. AddVersion
    13. ReadPublicLinks
    14. CreateAnnotations
  13. Click Add condition next to the Rule name.
  14. In the “Choose definition” drop-down, select Content Repository (M.ContentRepository) and click Select.
  15. Check Standard in the list of options and click Select.
  16. Click Add condition next to the Rule name.
  17. In the “Choose definition” drop-down, select Functional Group (MSU.FunctionalGroup) and click Select.
  18. Check the name of the appropriate functional group and click Select.
  19. Click Save.

Note: This user group should only be assigned to users who also already have the “Asset Validator” user group assigned to their account.

Settings for validators functional user group
Fig. 2: The settings for the Validators functional user group should resemble the above. The only changes that should be made to the above conditions are that the MSU.FunctionalGroup condition should match the functional group you just created.
Step 4: Map the User Groups to the Functional Group
  1. Click the gear icon to open the Manage page.
  2. Click the Taxonomy tile.
  3. Navigate to and click the name MSU.FunctionalGroup in the list of taxonomies.
  4. Click the “i” (information) icon to the right of the group name to open the group details.
  5. Click the pencil (edit) icon to edit the group details.
  6. In the “Restricted Visibility” section, click the “+” icon next to the “FunctionalGroupToUserGroup” field.
  7. Add both the two new user groups to this field.
  8. Click Save.
Assigned functional user groups mapping
Fig. 3: The two functional groups have been added to the FunctionalGroupToUserGroup schema field.