# data[].attributes.body
HR and OGC are currently working on a Visitor Program update, redefining visitor types to be more intuitive, streamline the visitor process, and reduce visit coordinator burden. When this is approved and implemented, how will we map these changes with respect to the defined sources of authority as shown on p. 13 of the IGA design document?

# data[].attributes.body
As we look to leverage DUO as a possible "replacement" for RADIUS, development of targeted solutions will take a significant investment in time/testing. If there are near(ish) term plans to re-evaluate other MFA options, it would be helpful to let IT staff know sooner that later so that we can plan and prioritize appropriately.

# data[].attributes.body
When onboarding, is there a limit to the scope of what gets activated? OIS manages Box for Government, InCommon / Sectigo certificate management and Palo Alto's Cortex XDR which all have onboarding / offboarding requirements. I assume other departments have tools that have similar requirements.

# data[].attributes.headline
Role-Based Access should be added to the roadmap

# data[].attributes.subject
Role-Based Access should be added to the roadmap

# data[].attributes.headline
Be transparent about what topics are being addressed in what phase of the roadmap.

# data[].attributes.subject
Be transparent about what topics are being addressed in what phase of the roadmap.

# data[].attributes.body
Assures the broader UCAR community that something is not being forgotten or passed over—and help people to focus their feedback at the right time and service owner.

# data[].attributes.body
For mission critical access in emergency situations (power control systems, required administrative access to on site services, etc.), alternative access is required. Is there a plan to exclude some mission critical systems or provide that alternative mechanism?

# data[].attributes.body
I used to use PBD to create and manage some aliases. Now many are managed in Google Groups. BUT, normal people don't have the capability to create aliases in Google Groups (which is really annoying). Will there be an alias creation / management function part of FI?

# data[].attributes.body
How will staff know which system to go to in order to request changes? I might think if I wanted to change my username that I'd have to first change my name in Workday. Should we point everyone to make a JIRA ticket and then the request would get triaged?

# data[].attributes.body
Remind me: will signature authority be integrated into FI? Or is that something within the realm of the Workday Financials rollout?

# data[].attributes.body
There are cases where employees take a new role in the organization, but continue to support their previous team for a period of time. I want to make sure there is a workflow and/or exception process for those situations so that the employees' old access isn't prematurely shut off in those circumstances if they are going through a phase out/phase in process.

# data[].attributes.body
How is on-boarding ahead of an actual start date handled? For instance, the host of a visitor wants them to start using the HPCs before their actual start date.

# data[].attributes.body
Say an employee suddenly leaves the organization (no notice, walked off the premises, death) how is access to their work, files, etc. granted?

# data[].attributes.body
The IGA + Workday Financials teams should work together on synergies between IAM and Signature Authority.

# data[].attributes.body
It's still unclear to me if the solution will support managing application specific roles, groups, user identities. I know there are some "out-of-the-box" applications (like Workday, Box, etc) that will be supported, but will we be able to arbitrarily add roles or policies that will trickle down to other third-party or custom applications?