Summary
This article explains what Policy-based Access Control (PBAC) is, why Ironclad is upgrading existing accounts, and what admins can expect when their account is upgraded. It covers what changes in the product and how existing permissions carry over automatically on upgrade day.
Upgrade from the legacy permissions model to Policy-based Access Control
Ironclad is upgrading existing accounts from the legacy permissions model to Policy-Based Access Control (PBAC). There are two ways your account may be upgraded:
- Scheduled upgrade: If you’ve received communication from Ironclad about your upgrade date, your account will be upgraded automatically on that date.
- Opt in to upgrade: If you haven't received a date and would like to upgrade, contact your Ironclad account team or Support.
Either way, your team's access is designed to carry over automatically on upgrade day, and the new permission model gives you more precise control with less ongoing maintenance.
Under the current model, permissions are configured separately across group settings, workflow configurations, and records. Getting a complete picture of who can access what means checking several places. 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.
For a full overview of how PBAC works in the product, see Access Policies.
What this upgrade makes possible
- Granular access control. Define precise permissions by resource type, action, and scope so a regional administrator can manage their own territory without needing global admin rights over the entire instance.
- Data segmentation within a single instance. Maintain clear boundaries between business units, regions, or confidentiality tiers without needing separate instances. For example, EMEA reviewers can be configured to see only EMEA workflows and records.
- Confidential contract protection. Restrict sensitive agreements to a named team. M&A deals or executive contracts can be made visible only to the people who need them.
- Centralized permissions management. Consolidate access into a unified policy structure instead of maintaining fragmented settings. Audits become straightforward, and access changes take effect in one place.
What stays the same
- Your users, groups, and group memberships are unchanged.
- Each group's existing access is designed to carry over as part of the upgrade. No one should lose access.
- Admins continue to manage access through groups.
- End users do not need to take any action. If a user notices their access looks different after the upgrade, they should contact their Ironclad administrator.
How your existing permissions carry over
When PBAC is enabled, Ironclad automatically translates every permission currently configured on each group into an equivalent Local Access Rule on that group. This happens in the background, nothing needs to be reconfigured before or on the day of the upgrade.
A Local Access Rule is a rule attached directly to one group. It preserves the same access the group had under the legacy model in the new PBAC format.
After the upgrade, each group's Local Access Rules are visible in its new Access Rules tab.
Before and after: what changes for a group
Before the upgrade:
- A group's permissions are set inside its group settings, across workflow configurations and records.
- To understand what the group can access, an admin has to open several screens.
After the upgrade:
- A new Access Policies tab will appear in Company Settings. This is where all permissions are now managed centrally.
- Inside each group, a new Access Rules tab shows how existing permissions have been carried over as Local Access Rules.
- System Policies are read-only policies provided by Ironclad, built from common permission patterns. They are available in the Access Policies tab. Apply them as-is or duplicate to customize.
- No Access Policies are applied to any group by default on upgrade day. Each group's access comes from its Local Access Rules until you choose to organize them into policies.
- New groups created after the upgrade start with no access by default. Existing groups are unaffected.
It is normal to see similar Local Access Rules across multiple groups after the upgrade. This reflects how permissions were set up in the legacy model. Consolidating them into shared Access Policies is a separate, optional step you can take at your own pace. See Organize your permissions with Access Policies after your upgrade when you're ready.
How access works under PBAC
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.
Before you start managing permissions in PBAC, there are four behaviors to understand.
Access is additive. When a user belongs to multiple groups, their total access equals the combined permissions across all those groups. There is no deny rule in PBAC. To remove access, remove the rule, policy, or group membership that grants it.
Access is denied by default. A group with no rules and no policy attached has access to nothing. A policy with no rules grants nothing.
Saving is not the same as applying. A policy that has been saved but not applied to a group grants no access to anyone in that group.
Edits fan out. Changing a shared Access Policy updates access for every group it is applied to, once saved. Before editing a shared policy, check which groups it has been applied to.
Illustration:
- Maria’s access is granted by her membership in the Legal Ops and EMEA Reviewers groups.
-
Members in both groups have shared access rules that are bundled as a policy and are able to:
- View and edit workflows
- View records
- Launch workflows
- But only members in the EMEA Reviewers group have access to use Playbook on Workflows. This is a Local Access Rule as it only applies to one group.
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.
Key terms
| Term | Definition |
| Access Policy | A named, reusable bundle of access rules that can be applied to one or more groups. |
| Access Rule | The core building block of an Access Policy. Defines what actions are allowed on which resource, and under what conditions. |
| Local Access Rule | An access rule added directly to one group. Gives that group specific access without creating a shared policy. |
| System Policy | A read-only access policy provided by Ironclad, built from common permission patterns. Duplicate it to create an editable version. |
| Custom Policy | An access policy you create or edit. Fully editable and can be applied to one or more groups. |
| Resource Type | The kind of object a rule applies to — for example, Workflows, Records, Groups, or Users. |
| Action | What a group is allowed to do with a resource — for example, View, Edit, Launch, or Manage. |
| Scope | A condition that limits where a rule applies, based on attributes of the resource — for example, region, business unit, or sensitivity. If no scope is set, the rule applies to every resource of that type. |
Next steps
- Prepare for Your Upgrade to Policy Based Access Control — what to do before and after your upgrade date
- Access Policies — a full overview of Access Policies in the product