Breadcrumbs

Automate Nimble AMS Permission Set Assignment with User Access Policies

Use Salesforce User Access Policies to assign Nimble AMS permission sets automatically when users are created or updated, instead of assigning them by hand. This guide explains how the feature works and how to set it up for Nimble AMS. For the list of permission sets and what each does, see Nimble AMS Product Permission Sets.

What is a User Access Policy?

A User Access Policy is a built-in Salesforce rule with three parts:

  • Criteria: which users the policy applies to (for example, Role equals Membership Staff).

  • Actions: what to grant or revoke. A policy can grant or revoke permission sets, permission set groups, permission set licenses, package licenses, public group membership, and queue membership.

  • Trigger: when the policy runs: when a user is created, updated, or both. You can also run a policy manually, once, for existing users.

User Access Policies replace the Flow or Apex automation that admins previously built to create and delete permission set assignments. They are generally available (Summer '24) and require no code.

Before you begin

  • You need the Manage User Access Policies permission (System Administrators have it).

  • Enable the feature in Setup > User Management Settings. A User Access Policies page then appears in Setup.

  • Build and test in a sandbox first.

  • Decide which permission sets will be policy-managed. Don't also assign those same sets manually, or admins won't know which is the source of truth.

  • Know your personas. The Which one do I assign? section of the permission set reference gives the starting set for each user type.

Example policies for Nimble AMS

Pick a user field that identifies the persona, such as Role, Profile, Department or a custom picklist, then create one policy per persona.

Policy

Criteria (example)

Grant

Nimble AMS Staff

Role in (your staff roles)

NimbleAMSStandard plus feature sets for their area (for example NimbleAMSManageMembership, NimbleAMSOnePayment)

Nimble AMS Read-Only Staff

Role equals Read Only Staff

NimbleAMSReadOnly plus the matching View All feature sets

Nimble AMS Admin

Role equals Nimble Admin

NAMSSetup, Community_Hub_Setup, plus admin sets for features they configure

Member Portal user

Profile equals “Community Hub Login User”

NimbleAMSCommerce plus your gateway set (NimbleAMSCardpointe or NimbleAMSPreczn)

Integration user

Username or custom field identifies the integration

Only that integration's API set (for example NimbleAmsLmsApi)

Tip: group sets into permission set groups (for example, a Nimble Staff group) and grant the group. Then you update one group instead of every policy when a set changes.

Do not grant both halves of a pair (Create and Modify All and View All / Read Only) to the same user. Put them in separate policies for separate personas.

Create a policy

  1. In Setup, enter User Access Policies in Quick Find and select it.

  2. Click New User Access Policy.

  3. Enter a Name, API Name and Description, and set the Order (see Order and overlap below). Save.

  4. Click Edit Criteria and add filters:

    • User Filters: up to 3, on Profile, Role, Permission Set / Group, Package License, or Public Group / Queue (operators: equals, in).

    • Additional User Fields: up to 10 standard or custom User fields (Text, Picklist, Number, Checkbox).

    • All criteria must be met (AND). Custom filter logic isn't available in the UI.

  5. Add one or more Actions. Choose Grant or Revoke, then the permission set, permission set group, license, group or queue.

  6. Choose how the policy runs:

    • Automate Policy: select Create, Update, or Create and Update, then Activate. The status changes from Design to Active.

    • Apply Policy: run once for selected users or all users who meet the criteria. Use this for existing users and one-time migrations.

To edit an active policy, deactivate it, make the change, and automate it again.

Order and overlap

If a user meets the criteria of more than one policy, only the active policy with the lowest Order value is applied. This is the most common cause of "my policy didn't run."

  • Give each persona's criteria a distinct, non-overlapping definition where possible.

  • If someone needs access from two personas (for example, staff who also administer), create a combined policy for that case with a lower Order number than the individual ones.

  • Policies are not chained: an action by one policy doesn't trigger another.

Verify and monitor

  • Open a user record and check the Recent User Access Changes tab. It shows whether each change was manual or automatic (automatic runs show Automated Process) and what was granted or revoked.

  • Only changes still in effect are listed. If someone later removes a policy-assigned permission set, it disappears from the list.

  • Spot-check with Permission Set Assignments on a test user after creating or updating them.

Limits and gotchas

  • Up to 200 active policies per org.

  • Use Revoke actions deliberately. A policy that grants a set doesn't remove it when the user stops matching the criteria. Add a separate policy to revoke it.

  • Criteria are evaluated against the User record when it is created or updated. If you key off a field you change later (such as Role), use Create and Update.