---
sourceDocument: Australia Employee Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/pt-BR/employee-service-management

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Employee Service Management

ft:clusterId :

    - emplsm

bundleId :

    - emplsm

workflow :

    - Employee


---

# Configure COE security policies

# Configuring HR Service Delivery Center of Excellence (COE) security
policies {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

Use COE Access Control List (ACLs) Configuration to allow specific groups read or write
access to HR cases under a specific COE.

For example, you don't want the Benefits group to view the cases created by the Compensation
group. You create a COE security policy that allows the Compensation group access. Groups that
aren't included on the policy cannot access the cases.

Use this feature as an alternative to using ACLs rules. For more information on ACLs, see [Access control list rules](https://www.servicenow.com/docs/access?context=access-control-rules&version=australia&pubname=australia-platform-security&ft:locale=en-US).

COE security policies don't affect case creation. COE security policies affect what cases you
can view or modify after creation.

You can still reclassify (transfer) HR cases from one HR service to another. Depending on the
security policy, you might not be able to view the case after reclassification.

COE ACL Configuration uses the COE Security Policy \[sn_hr_core_coe_security_policy\] table to
determine access to the extended HR case tables (COEs).

The \* next to a table indicates it was deprecated for customers taking the Rome
release to support a new data model. Existing customers using the legacy COEs and tables are not
affected. These tables have been replaced by the Employee Relations feature. For more
information, see [Employee Relations](https://www.servicenow.com/docs/OJBsy3q~vNMLRL6rRflb7g "With Employee Relations (ER), handle a sensitive complaint with tighter security. Maintain complete confidentiality and protect the privacy of the user who has raised the complaint.").  
The tables you can provide security for are:{#hr-coe-security-policies__table_kbb_jbv_kjb__entry__2}

| Label | Name |
|-|-|
| HR Benefits Case | sn_hr_core_case_benefits |
| HR Compensation Case | sn_hr_core_case_compensation |
| HR Corporate Communications Case | sn_hr_core_case_corporate_communcations |
| \*HR Employee Relations Case | sn_hr_core_case_relations |
| \*HR Ethics Case | sn_hr_core_case_ethics |
| HR Global Mobility Case | sn_hr_core_case_global_mobility |
| HR Payroll Case | sn_hr_core_case_payroll |
| \*HR Performance Case | sn_hr_core_case_performance |
| HR Talent Management Case | sn_hr_core_case_talent_management |
| HR Total Rewards Case | sn_hr_core_case_total_rewards |
| HR Workforce Administration Case | sn_hr_core_case_workforce_admin |
| HRIT Operations Case | sn_hr_core_case_operations |
| HR Lifecycle Events Case | sn_hr_le_case |
[Tabela 1. Tables]

{#hr-coe-security-policies__table_kbb_jbv_kjb}  
Nota:  
You can also provide security to any case table you extend.  
To define security for a COE:

* Choose all or specific HR services that fall under a COE.  
  Nota:  
  When you select specific HR services for a COE, the unselected HR services are accessible by the case reader.
* Determine what groups have read or write access to HR services under a COE.
* Create conditions to filter the records that apply to your security policy.  
  Nota:  
  Condition builder is a powerful tool that filters specific actions on the COE. Use caution when using conditions on your security policy. It may also affect system performance.
{#hr-coe-security-policies__ul_olj_sgv_kjb}