• Levels of Permisisons Granted: Admin level
  • Department: Marketing, IT

This persona is known as the gatekeeper of the CMS. They are in charge of adding and removing individuals.

Jobs to be done

  • As an Admin, I expect to assign cloud users on my team as admins of specific Drupal instances. When the user logs in as an admin to a Drupal instance, I expect them to have the admin role in that Drupal instance.
  • As an Admin, I want to add/remove platform roles on the CMS.
  • As an Admin, I want to block specific users causing them to loose access to the CMS instantly.
  • As an Admin, I want to leverage SSO to authenticate user access to the CMS.
  • As an Admin, I want quick access to in-product support; help documentation, view support tickets, submit support tickets.
  • Asan Admin, I want to configure system and account settings.
  • As an Admin, | want to set region and language settings.

Decisions they must make

  • Is my organization secure?
  • Has anyone left
  • Is there a potential "bad actor" that needs to be blocked?
  • What sites are not being used?
    • Who are the admins for those sites?
    • Can they be removed?

Pain points/Frustrations

  • Keep away from technical workflows that require others to be brought in (bottleneck)
  • Lack of admin security settings by role and content

Delights

  • Security settings by role and content
  • Notifications to alert them to things that need their attention / items need theirs review