Skip to end of banner
Go to start of banner

Managing Roles and Policies Centrally

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

UXPROD-4707 - Getting issue details... STATUS UXPROD-4708 - Getting issue details... STATUS

Problem(s):

  • Different consortia models will use tenants to represent different entities. In order for these systems to be capable of adapting to changes in the composition or size of the organization, it will need to be possible to add or remove tenants

Use Cases & Requirements:

Legend
Scope may require separate feature

Requirement

Status

Use cases


VERIFIED

User that configures roles is the person who assigns permissions to user


VERIFIED

Multiple Admins create roles and assign permissions to staff. Staff may or may not be assigning and unassigning users. Student perms change so often they try to distribute the responsibility

VERIFIED

1 Admin configures roles and generally assign staff to roles. Staff that manage the student works will actually assign permissions to their student workers

VERIFIED

User needs to see the granular perms of a specific user on the user record for troubleshooting.


VERIFIED

Generally a security vulnerability to display user permissions to anyone who can see staff users (User could target other users based on their permissions linger at their workstation etc.)


VERIFIED

When identifying why user 1 can not do what user 2 can do we compare the users specific permissions or roles.


VERIFIED

When new permissions are added functional roles are updated. Admins then compare roles to verify all necessary functions are included in each role


Proposed workflow:


Questions:

Question

Status

Conclusion

Comments


OPEN




OPEN



Functionality Potentially Impacted by Changes:

Functional area

Records

Potential impact

Suggested Regression Testing








Work Breakdown Structure:

  • No labels