Project Roles

Web Services offers various project roles to allow teams to better differential the level of access and responsibility for each user of their team.

Sponsor

  • Highest level decision maker
  • Responsible for all data and content that is processed and stored
  • Can have access to JIRA upon request for content or support requests
  • Typically does not edit the site themselves, but can be granted site access upon request
  • Can request and approve user access on their site

Primary Web Liaison

  • The lead contact for website issues, content updates, and user-submitted support requests
  • Has access to the site to make updates
  • Has access to JIRA for support and content requests
  • Has access to GatherContent during site build
  • Has access to CUPS for profile updates (upon request)
  • Can request and approveĀ user access on their site

Secondary Web Liaison

  • The backup contact for website issues, content updates, and user-submitted support requests and works closely with the Primary Web Liaison
  • Has access to the site to make updates
  • Has access to JIRA for support and content requests
  • Has access to GatherContent during site build
  • Has access to CUPS for profile updates (upon request)

Site User

  • Reports to Primary and Secondary Web Liaisons for support requests
  • Has access to the site to make updates

GatherContent Editor

  • Has access to GatherContent during site build

CUPS Administrator

  • Has access to CUPS for profile updates
  • Has access to JIRA for CUPS related support requests only