Skip to content

UI: Individual service approvers should be configured per resource in Admin » Settings » Approvers. #908

@nopivnick

Description

@nopivnick

this will involve refactoring some of the recent work done on #985, specifically wrt the Admin > Settings > Approvers tab UI.

the Approvers tab should have two main sections, ${permissionLabels.reviewer} and ${permissionLabels.services}.

under ${permissionLabels.services}, there should be a table for every ${resources}, sorted by roomId in increasing order.

the header row for each resource table should provide the ability to add a service approver, including:

  • a dropdown menu comprised of each service available in that resource (pulled from ${tenant}-tenantSchema.resources.services)
  • a text field to enter an email (that validates a NetID email with a call to the NYU Identity API)

resource table rows (service approvers) should have three columns:

  • email
  • service (the name of the service)
  • action (a trash can icon to delete the entry)

Metadata

Metadata

Labels

No labels
No labels

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions