Role Security Administrators (RSAs) can find everything they need to request access to Oracle Financial Cloud (OFC), Jaggaer, Concur and TOE here: what each role does, the training it requires, and the roles that go with each persona.
Start here
Check training
Confirm the course a person must finish before access is provisioned.
Pick the right persona
Match a job function to the roles it receives. Separate lists for department and central users.
Find a role
See what each OFC, Jaggaer, Concur and TOE role can and cannot do.
How a request works
- The RSA submits the request. Only RSAs can submit, using the OFC Access Request form. RSAs can also request access for themselves. In that case, ServiceNow emails the RSA's supervisor for approval, and Security & Controls reviews the request once the supervisor approves. Giving your supervisor a heads up helps keep it moving.
- Security & Controls reviews it. We confirm the persona and roles, the security context (FRU or Business Unit), and required training.
- We check separation of duties (SoD). Some roles cannot be held together. If we find a conflict, we ask which role the person should keep. Jaggaer combinations are listed in the Gateway Roles Matrix (Google Sheet, opens in a new tab).
- Access is provisioned and the ticket is closed. Jaggaer/OFC access can take up to 4 hours to sync. Concur syncs nightly, so it is available the next business day. TOE is available shortly after provisioning.
Before you submit: include the security context for any role that needs one (an FRU for department roles marked with *, or a value such as a Business Unit for some central personas), and confirm training is complete. Missing information is the most common reason a request is delayed.