Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

 


Attendees

Maura Byrne

Cammie Wyckoff

Björn Muschall

Amelia Sutton

patty.wanninger

morganm@gvsu.edu

Michelle Suranofsky

Uschi Klute

Nancy Burford

Brooks Travis

Andrea Loigman

Matthew Harrington


Goals

  • Discuss requirements of a proposed Permissions app
    • What should it look like?
    • What functions should be visible/configurable?


Notes

TimeItemWhoNotes
5 minNote takerAmelia Sutton

Display of nested permission setsBjörn MuschallLeipzig development team took a look.

This is a UI-only change to a single line of code.  Does displaying nested permission sets cause a problem?


Requirements of a proposed Permissions appMaura Byrne

In a Permissions app, we want to do the following:

  • See which permissions a user has
  • See which users have a certain permission set
  • Assign users to permission sets (not just the other way around) 
  • See what are the effective permissions for this user.
    • Listing the sub permissions included in the permission sets assigned to a user and where they come from (which sets they are from)
  • See the permission sets that a specific permission is assigned to
  • We discussed large numbers of nested permissions, but we decided at this time that it was an uncommon edge case.  We would find a solution later.

Possible issues:

    • Currently no way to lock the ability to change permission assignments only to particular apps (i.e. only be able to assign/unassign Access Services permissions to users)
      • This can be resolved internally by institutions that plan to have non-admin folks assigning permissions, and is thus out of scope for this app.

There was some discussion of where this app should exist.  The majority voted for a module in the Settings app.  (Unless a developer says different.)

There was a discussion regarding whether we should take responsibility for the app, with Patty as PO.  No decision was reached.