If you are a system administrator, you may need to set up security profiles for different types of users in your organization. Security profiles are a way of controlling what users can see and do in the system, based on their roles and responsibilities. In this blog post, I will explain the different types of security profiles that are available in Oracle Fusion HCM, and how they can be used to grant or restrict access to various data and functions.
Organization Security Profile: This profile determines which organizations (such as business units, departments, or legal entities) a user can access. For example, you can create an organization security profile that allows a user to view only the organizations that belong to a specific region or division. You can assign this profile to a role or a user directly, and it will apply to all HCM applications that use organizations as a security dimension.
Position Security Profile: This profile determines which positions (such as job titles or grades) a user can access. For example, you can create a position security profile that allows a user to view only the positions that are within their own hierarchy or reporting chain. You can assign this profile to a role or a user directly, and it will apply to all HCM applications that use positions as a security dimension.
Document Type Security Profile: This profile determines which document types (such as contracts, visas, or passports) a user can access. For example, you can create a document type security profile that allows a user to view only the document types that are relevant for their country or region. You can assign this profile to a role or a user directly, and it will apply to all HCM applications that use document types as a security dimension.
Country Security Profile: This profile determines which countries (such as the United States, Canada, or India) a user can access. For example, you can create a country security profile that allows a user to view only the countries where your organization operates or has employees. You can assign this profile to a role or a user directly, and it will apply to all HCM applications that use countries as a security dimension.
Payroll Security Profile: This profile determines which payrolls (such as monthly, biweekly, or weekly) a user can access. For example, you can create a payroll security profile that allows a user to view only the payrolls that are assigned to their own organization or legal entity. You can assign this profile to a role or a user directly, and it will apply to all HCM applications that use payrolls as a security dimension.
Flow Pattern Security Profile: This profile determines which flow patterns (such as hire, transfer, or terminate) a user can access. For example, you can create a flow pattern security profile that allows a user to view only the flow patterns that are relevant for their role or function. You can assign this profile to a role or a user directly, and it will apply to all HCM applications that use flow patterns as a security dimension.
Legislative Data Group Security Profile: This profile determines which legislative data groups (LDGs) (such as US Primary LDG, UK Primary LDG, or India Primary LDG) a user can access. For example, you can create an LDG security profile that allows a user to view only the LDGs that are applicable for their country or region. You can assign this profile to a role or a user directly, and it will apply to all HCM applications that use LDGs as a security dimension.
Public Person Security Profile: This profile determines which people (such as employees, contingent workers, or applicants) a user can access in public mode. Public mode means that the user can see only the basic information of the person, such as name, email address, phone number, or photo. For example, you can create a public person security profile that allows a user to view all people in the system, regardless of their organization, position, or country. You can assign this profile to a role or a user directly, and it will apply to all HCM applications that use people as a security dimension in public mode.
Person Security Profile: This profile determines which people (such as employees, contingent workers, or applicants) a user can access in-person mode. Person mode means that the user can see more detailed information of the person, such as personal details, work details, compensation details, or performance details. For example, you can create a person security profile that allows a user to view only the people who report to them directly or indirectly. You can assign this profile to a role or a user directly, and it will apply to all HCM applications that use people as a security dimension in-person mode.
I hope this blog post was helpful for you. If you have any questions or feedback, please leave a comment below.