Summary
After your upgrade to Policy-based Access Control (PBAC), your existing permissions are intact as Local Access Rules on each group. This article explains how to take the optional next step: consolidating those rules into reusable Access Policies that are easier to manage, audit, and update over time.
Your upgrade and your permissions reorganization are two separate steps
Your Ironclad instance is fully functional after the upgrade with your existing permissions intact as Local Access Rules. Your team keeps the access they had before, and nothing needs to change on day one.
Organizing those Local Access Rules into Access Policies is a separate step. It makes PBAC significantly easier to manage over time, but is not a requirement for the upgrade to be complete. You can take this step at your own pace, after you have confirmed your upgrade was successful.
Why it is worth doing
After the upgrade, you may notice the same or similar Local Access Rules repeated across several groups. This is expected as it reflects the way permissions were configured in the legacy model. The opportunity with PBAC is to consolidate those repeated rules into a single shared Access Policy.
When multiple groups share an Access Policy, one change updates all of them at once. Access reviews become faster. Onboarding a new team requires applying an existing policy rather than rebuilding rules from scratch. Audits go from checking each group separately to reviewing a single policy.
How to find rules to consolidate
- Go to Company Settings > Groups and download your Access Rules report.
- Look for groups that carry the same or very similar Local Access Rules.
- Plan a broad baseline policy that covers what most users need, plus smaller specialized policies for groups that need more.
- Create each policy, apply it to the relevant groups, and check the resulting seat type before saving.
- Remove the Local Access Rules that each policy now replaces.
- Check access for a few representative users to confirm nothing changed.
- Document each policy: which groups it is applied to, its scope conditions, and an owner.
Work through a few patterns at a time rather than running one large reorganization project. Keep Local Access Rules where the access is unique to one group and does not need to be shared.
Example: Suppose four regional groups each have a Local Access Rule allowing View on Records with no scope. After your upgrade is validated, you create one Custom Policy called "Records Viewer," apply it to all four groups, and remove the four individual rules. One policy now covers all four groups — and if the rule ever needs to change, you update it once.
Choosing the right building block
| If you need... | Use | Notes |
| A ready-made starting point for a common permission pattern | System Policy | Apply to a group as-is. Read-only — duplicate it to customize. |
| A variation of a policy you already have | Duplicate it | Creates an editable Custom Policy. Review the copied group assignments before saving. |
| Multiple groups to have the same access | Custom Policy | One place to maintain, applied to as many groups as needed. |
| One specific group to have elevated access that should not be shared | Local Access Rule | Lives in that group only. Not reusable. |
For step-by-step instructions on building and managing policies, see:
- Access Policies — overview and key terms
- Create an Access Policy
- Edit an Access Policy
- Duplicate an Access Policy
A note on seat type
When you create, edit, or duplicate a policy, Ironclad shows the resulting seat type for each group the policy is applied to. Some actions are tied to higher seat levels. The rule builder will show a notice when a rule may change a group's seat type. Always review seat type under Applied Groups before saving.
Best practices
- Start with least privilege. Add only the rules a group needs, and use the smallest set of actions that covers the requirement.
- Build a baseline, then layer. One broad baseline policy covers what most users need. Smaller specialized policies handle the rest. Layering keeps each policy focused, reusable, and easier to audit.
- Use Local Access Rules for group-specific elevated access. When a group needs access that no other group should have, a Local Access Rule is the right tool, not a policy.
- Scope only when you need to. With no scope, a rule applies to every resource of that type. Check that the scope attribute exists and is consistently populated on the resource before using it.
- Review before editing a shared policy. A saved change applies to every group the policy is assigned to. Check the Applied Groups list before making changes.
- Document as you go. For each policy, record which groups it is applied to, its scope conditions, and an owner.
Common mistakes to avoid
| Mistake | What to do instead |
| Building launch permissions using the Workflows resource type | Use Workflow Configurations with the Launch workflows action. A rule on Workflows does not grant launch access. |
| Expecting a new group to have default access | Grant access explicitly. New groups start with no access after the upgrade. |
| Editing a shared policy without checking who uses it | Open the Applied Groups list and review every group the policy is assigned to before making changes. |
| Duplicating a policy without reviewing the copied group assignments | Check and adjust group assignments on the duplicate before saving. |
| Applying a scope to an attribute that is missing or inconsistently populated | Confirm the attribute is populated on the resource before using it as a scope condition. |
| Assuming removing a policy removes all access for a user | A user may belong to other groups that still grant access. Check every group the user belongs to. |
| Building one large policy per group | Build a broad baseline policy plus small specialized policies. One large policy per group recreates the problem PBAC is designed to solve. |
Next steps
- Using Access Policies to enforce data segmentation and confidentiality — illustrative guide using real world scenarios