Examples of Location-Based Access in Oracle HCM Cloud

This topic describes some typical use cases for creating public roles for Oracle HCM Cloud users. Using these roles, users can perform a restricted set of tasks from IP addresses that aren't registered.

Public Access for Pending Workers

During preboarding, pending workers may need to complete some tasks in Oracle HCM Cloud. Pending workers can't usually access the office network or use registered IP addresses. So, to let them complete tasks such as viewing personal information or uploading document records, you can make the Pending Worker role public. Or, to limit what the Pending Worker role can do, you could create a custom role with limited privileges and make it public. Pending workers could then complete their preboarding tasks when signed in from any IP address.

Public Access for External Learners

Let's say that you need to let external learners, such as partners, resellers, contractors, or franchisees, complete some company training. Usually, only employees can access learning, and they need to be in the office network or using a registered IP address. To let external learners use selected learning tasks, you could create an External Learner role and make it public. The role would support just the tasks that external learners need. Users with the External Learner role could then access learning from any IP address.

Public Access for Oracle Recruiting Cloud Users

Suppose that all external candidates need to access Oracle Recruiting Cloud career sites from the public domain. To give them this access, you can make the predefined Anonymous User abstract role (ORA_FND_ANONYMOUS_USER_ABSTRACT) public.

Any integrations with approved third-party party vendors use REST APIs to send data back to Oracle Recruiting Cloud. To support these integrations, you can create a custom integration role with integration privileges. You may need more than one of these roles, depending on the integration services, such as job distribution, background check, and assessments, that you enabled. You would need to make all of the custom roles public, so that the REST APIs can be called by partner applications outside your intranet. You would also have to give the integration roles to the Oracle Recruiting Cloud users who start the integration request from the application. Oracle Recruiting Cloud doesn't provide predefined.integration roles.