...
- Ratify Access Management Policy
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| 25min | Review/Discuss Access Management Policy |
| All | LJ - RE: operationalizing this policy - could create challenges to Programs that could be overwhelming, with regard to how Google Drive/Docs are currently used and shared across several team members/work study/etc.. Enforcing will require a challenging culture change We need a policy of what types of data belong on Google Docs vs H: Drive LJ - maybe add a Q&A appendix to policy document AB - updates to off-boarding policies to include checks for Document ownership and transfer protocol. BI - operationalizing support and resources for staff available? How do I abide by policy using my Google Doc ownership/transfer? BV - Finance and Analytics will provide a sample framework that our team uses and could provide a sample operational framework for others to use. |
| 5min | Vote on new policy |
| All | Access Management Policy ratification - RATIFIED 3/31 |
Action items
- Add policy to library (if ratified) Bryon VaughnBryon Vaughn - Add policy to library
- (AL) Just putting in a request for a resource. I think it would be helpful for system administrators to get a monthly list of employees who have left to cross-check system access. We are good with updates related to departures from our own teams, but it is harder to say on top of departures from other teams/programs. (Making a note to remove Tom's Slate access). (AB) Yes, like central CU does for SIS every couple of months verifying that people still need access and level access to university software system
- Future Agenda item - operationalize the policy, onboarding new employees, inventory existing current document access
- Bryon Vaughn - connect with HR (Merideth) regarding existing on/off-boarding process/protocols and find areas were we can operationalize new policy there