Using Access Policies to enforce data segmentation and confidentiality
Summary
This article covers real world scenarios on how to use Access Policies to enforce data segmentation across regions and protect confidential contracts.
How access rules work under Policy-based Access Control
An access rule answers three questions: what action is allowed, on which resource, and under what conditions. It does not answer who, and that is on purpose. The who comes from the group the rule is applied to, either directly as a Local Access Rule or through an access policy. Users receive access through their group memberships.
In the product, a rule reads like the example above: ALLOW View and Edit on Workflows, if Region is North America. It has three parts: one or more actions, a resource, and an optional scope. The group is where the rule is applied directly or through an access policy, and users receive access through their group memberships.
What can be scoped?
Scope adds a condition to a rule (often the business context), such as “Region is EMEA.” It is based on attributes of the resource type, so it is only available on resource types that carry attributes. If scope is not available for the selected resource type, the scope section will not display in the access rule builder. Custom properties on the resource can also be used. The first dropdown in the Scope section lists the attributes available for that resource type in the customer’s company.
Under the legacy permission model, permissions were configured separately across group settings, workflow configurations, and records. Getting a complete picture of who can access what means checking several places. Policy-based Access Control (PBAC) replaces this with a single policy model: admins define access through rules, bundle those rules into policies, and apply policies to groups. Everything lives in one place. Here is a quick overview of the resource types available under PBAC.
For a full overview of how PBAC works in the product, see Access Policies.
Illustrative guides to enforce data segmentation and confidentiality
Example 1: Keep regions apart (data segmentation)
- Goal: EMEA reviewers work only on EMEA contracts.
- Build: Create a Custom Policy, “EMEA Reviewer,” that allows View and Edit on Workflows and View on Records, scoped to Governing Law is EMEA. Apply it to the EMEA Reviewers group.
- Who gets access: Members of EMEA Reviewers, for EMEA workflows and records.
- Who doesn’t get access: Anyone not in a group that grants the access.
- Watch for: A user who is also in an APAC group gets both, because access is additive.
Example 2: Protect confidential contracts
- Goal: Only the M&A deal team can see confidential records.
- Build: Create a baseline access policy that grants View on Records where Sensitivity is a non-confidential tier, and assign it to broad user groups. Then create a separate policy, “Confidential Records,” that grants View on Records where Sensitivity is Confidential or Highly Confidential, and apply it only to the M&A Deal Team.”
- Who gets access: Broad groups see non-confidential records. M&A Deal Team members see confidential records.
- Who doesn’t get access: Everyone else cannot see confidential records.
- Watch for: With no deny rule, a broad rule with no scope would grant access to confidential records too, so scope the broad rule to the non-confidential values. A sensitivity value added later is not covered until someone adds it to the baseline access policy.
Example 3: Delegate admin for one region
- Goal: APAC admins manage APAC groups, not every group in the instance.
- Build: Create a Custom Policy, “APAC Group Admin,” that allows View, Edit and Manage membership on Groups, scoped to three specific groups: APAC Sales, APAC Legal and APAC Support. Apply it to the APAC Admins group.
- Who gets access: APAC Admins, for the groups selected in the scope.
- Who doesn’t get access: Those admins, for groups in other regions or instance-wide settings.
- Watch for: Groups can’t be scoped by an attribute such as region today. The scope is a list of specific groups, and the customer selects each group the admins may manage.
Example 4: A user in two regional groups
- Setup: Group North America - Standard has a rule allowing View and Edit on Workflows where Region is North America. Group EMEA - Viewers has a rule allowing View on Workflows where Region is EMEA.
- Maria is in both groups. She can view and edit North America workflows and view EMEA workflows. She should not be able to edit EMEA workflows or touch APAC workflows.
- Dev is only in EMEA - Viewers. He can view EMEA workflows. He should not edit anything or see North America or APAC workflows.
- Priya is in neither group. She has no access to these workflows.
- Watch for: If Maria can edit an EMEA workflow, another group, policy or Local Access Rule is granting it. Check every group she belongs to.
Example 5: Removing a grant does not remove the access
- Setup: Policy Regional records editor (View and Edit on Records where Region is EMEA) is applied to Legal - EMEA. Group Legal - Global has a Local Access Rule allowing View on Records with no scope. Sam is in both groups.
- What happens: When the admin removes the policy from Legal - EMEA so Sam only works with EMEA records, Sam loses edit access, but can still view records in every region through Legal - Global.
- Fix: Scope or remove the rule on Legal - Global, or take Sam out of that group.
- Watch for: This is the most common surprise, so ask “which other groups is this person in?” A policy edit has the same reach: changing a shared policy changes access for every group it is applied to.