Regent Web-Based Design, Content, and Template Platform

The Vendor is required to provide regent web-based design, content, and template platform for include:
- Adoption, usability and collaboration
• Platform’s adoption within higher education, including examples of enterprise-wide deployments and typical user adoption rates.
• Licensing model, including your ability to support a phased implementation approach, usage-based adjustments of implementation model, and ability to deploy to large-scale student access.
• Account support provided during the implementation of the platform and adoption across the universities' respective campus, including onboarding, training, and account management, etc.
• Platform supports user collaboration, including but not limited to: simultaneous editing, commenting, and version control.
• Platform capabilities are capable for use on mobile devices (iPad, android tablet, phones, etc.)
- Branding governance
• Landing page experience can be customized for institutional use using the platform.
• The ability to apply institutional branding and feature approved templates and assets.
• The ability of the platform to restrict specific template elements such as logos, fonts, layout components, etc. to maintain brand consistency.
- Template system and content creation
• Brand templates are organized, categorized, and presented to users for search and discoverability.
• Manage third-party contractors (marketing services partners) ability to upload assets into the system if needed.
• Platform supports scalable content production including but not limited to, automation features such as bulk creation, dynamic fields, or data-driven content, and multi-format outputs.
• Tools or workflows does the platform provide to ensure accessibility compliance (e.g. WCAG 2.1/2.2, level aa) in digital content outputs, particularly pdf creation, tagging, and remediation.
- Digital asset management
• Media-graph (mediagraph.io) as its digital management system.
• State university uses various systems including but not limited to Smugmug, SharePoint, and box.com.
• Capable with direct integration of the universities' individual digital asset management systems.
- Software authentication integration
• Microsoft active directory from an authentication and authorization perspective.
• All authentication methods the system supports, with specific attention given to shibboleth, SAML, and multifactor authentication.
• University's existing Microsoft Entra id using SSO (SAML 2.0 or OpenID connect).
• Any API and web-hook support available for system-to-system messaging.
• Include details on integration capabilities with Microsoft outlook and Microsoft teams, such as support for email services, calendaring, teams messaging, notifications, and workflow or bot-based integrations if applicable.
- Platform administration
• Centralized administrative control is required for the selected platform solution.
• Platform supports centralized administration of brand asset libraries, templates, and user permissions across both individual and group segmented user groups.
• The extent to which administrators can disable features such as AI, image libraries, printing, etc. And control the visibility of asset libraries to different user groups.
• Clearly identify any limitations of administrative control functionality of the platform.