Skip to main content

How does membership automation work?

An access profile is a resource in the C1 app. When a user matches the membership condition on the access profile, a request task for the access profile’s membership entitlement is automatically created. When this request is approved, the user becomes a member of the access profile and automatically requests all of its access, all without the user, their manager, or the IT team manually creating a single access request. When the user no longer matches the membership condition on the access profile, a revocation task for the membership entitlement is automatically created. When this revocation is confirmed, the user is removed from the access profile’s membership. You can configure the access profile to determine what happens to the user’s access in this case (more on this below).
Membership automation is available on two access profile types: role and hybrid. Catalogs don’t track members, so they don’t have it. See Access profile types to learn more.

Are new members immediately granted the full access profile?

It depends. When a user is assigned the membership entitlement for the access profile, a request task is created. Based on the request policy set on the access profile, the request for membership might be auto-approved, or it might need one or more human reviewers to sign off. Once the user’s request for access to the membership entitlement is granted, C1 will automatically create access request tasks for each item in the access profile. Based on the request policies on each individual entitlement, this access might be automatically approved, or it might require human intervention to approve and provision. If an access profile contains only low-risk access, you can set the policies on the access profile itself and the entitlements within it to automatically approve these requests, essentially granting users who are members of the access profile all of its access immediately.

What happens to access when a user is removed from membership?

Here too, it depends. When setting up the access profile, you have the option to determine whether some or all of the access included in the access profile is automatically revoked when a user is removed from membership. When a user is removed from the access profile’s membership, a revocation task for the membership entitlement is created. Based on the revoke policy set on the access profile, the revocation might be auto-approved, or it might need one or more human reviewers to sign off. Once revocation has been confirmed, C1 will follow the rules set up in the access profile to determine what to do with the user’s access. The options here are:
  • Do nothing, and leave the access granted by the access profile as-is
  • Create revocation tasks for any entitlement granted by the access profile that the user does not also have access to via another access profile (these are called “unjustified” entitlements)
  • Create revocation tasks for all entitlements granted by the access profile
Based on the revoke policies on each individual entitlement and how the access profile is configured, access marked for revocation might be automatically revoked, or it might require human intervention to confirm the revocation and deprovision the access.

Set up membership automation

Before you begin, make sure you’ve followed the instructions in Create access profiles to set up an access profile and add the relevant entitlements. You set up membership automation on the role or hybrid access profile’s Settings tab. The settings you see depend on the access profile’s type, so follow the steps for your type.

Set up membership automation on a role

If you’re creating a new role, you can set the membership condition on the Birthright membership step of the creation wizard. To set it up or change it later, use the role’s Settings tab.
1
In the Birthright membership area of the page, click Edit.
2
Under Add and remove users based on, set the membership condition:
  • Choose Users with entitlements and select one or more entitlements from the dropdown. Users who are currently granted any of the entitlements you select become members of the role.
  • Choose Expression and write a CEL expression that describes the condition. Click Run in the Preview area to test it, or describe the condition in plain language and let C1AI draft the expression for you.
3
If you’re ready to start using the membership automation, click to turn on Enabled at the top of the drawer.
If you don’t want to start adding and removing members immediately, leave the toggle disabled and save your progress. You can enable the membership automation whenever you’re ready.
4
Click Save.
5
On the Advanced area of the Birthright membership card, click Edit to set the following:
  • Exclude users: add any users who should not be members of this role, even if they currently match, or are later granted, the entitlements or attributes in the condition.
  • Change access with membership: leave this toggle disabled if you want to update the list of members but take no other action. Enable it if you want to update the list of members and kick off the membership and access changes that go with it.
  • Revoke behavior: choose what happens to the role’s entitlements when membership is revoked through a task. You can choose Leave access as-is, Revoke unjustified entitlements (the entitlements the user was granted only by this role), or Revoke all entitlements.
  • Anomaly detection: configure the safeguard that pauses the automation if too many members would be removed at once.
6
In the Approval policies area, click Edit to set the following:
  • Membership grant policy: the approval policy used for the role’s membership entitlement. When a user is added to the role through membership automation, C1 creates a request task for their access to this entitlement, and the user doesn’t become a member until it’s approved. If you don’t set a policy here, the role uses the default policy set on the C1 app.
  • Entitlement provisioning: choose Bypass each entitlement’s grant policy or Enforce each entitlement’s grant policy. Bypassing means that approval of the membership entitlement is understood as approval of the user gaining access to everything in the role, so individual requests for each entitlement aren’t needed.
  • Membership revoke policy: the revocation policy used for the role’s membership entitlement. If you don’t set a policy here, the role uses the default policy set on the C1 app.
  • Entitlement deprovisioning: choose Bypass each entitlement’s revoke policy or Enforce each entitlement’s revoke policy. Bypassing means that confirming the revocation of the membership entitlement is understood as approval of the user losing access to some or all of the entitlements in the role, so individual requests for each entitlement aren’t needed.
7
Optional. If membership in this role shouldn’t last indefinitely, set a Max membership duration in the Self-service membership area. This limits how long users can be members of the role.
Done. Once you enable the membership automation, request tasks are immediately created for the users who match your condition. Users added to the exclusion list automatically request the access profile’s excluded from rule entitlement.

Set up membership automation on a hybrid profile

Step 1: Configure access request settings on the access profile

1
On the access profile’s Settings tab, make sure that Allow requests is set to On. Click Edit and enable the toggle if needed.
2
Stay on the Settings tab. We’ll set up the access profile to automatically add and remove members for users who match or no longer match a membership condition that we define.

Step 2: Set joiner rules

In the Joiner section of the page, click Edit and set the following:
1
Select the Approval policy that will be used for this access profile’s membership entitlement.When a user is added to the access profile via membership automation, C1 creates a request task for their access to the access profile’s membership entitlement. The user will not be added to the list of members until this request is approved.If you don’t set a policy here, the access profile will use the default policy set on the C1 app.
2
Once the user’s membership in the access profile has been approved, access request tasks are created for each entitlement in the access profile. Under Entitlement provisioning, select whether these request tasks should apply the grant policy on their respective entitlements (Enforce each entitlement’s grant policy), or whether they can bypass the individual entitlements’ policies (Bypass each entitlement’s grant policy).In practice, choosing Bypass each entitlement’s grant policy means that approval of the access profile membership entitlement is understood as approval of the user gaining access to everything in the access profile, so individual requests for each entitlement are not needed.
3
Optional. If membership in this access profile should not be granted indefinitely, set a Max membership duration. This limits how long users can be members of the access profile.
4
Click Save.

Step 3: Set leaver rules

In the Leaver section of the page, click Edit and set the following:
1
Select the Leaving policy that will be used for this access profile’s membership entitlement.When a user is removed from the access profile via membership automation, C1 creates a revoke task for their access to the access profile’s membership entitlement. The user will not be removed from the list of members until this revocation is confirmed.If you don’t set a policy here, the access profile will use the default policy set on the C1 app.
2
Under Access change behavior, set what to do with the access that has been granted by the access profile when a user is removed from membership. You can:
  • Leave access as-is
  • Revoke all entitlements granted by the access profile
  • Revoke unjustified entitlements (these are the entitlements that the user was granted only by this access profile; any entitlements that are duplicated in other access profiles the user is still a member of will not be revoked)
3
Once the user’s removal from the access profile has been confirmed, revocation tasks are created for any impacted entitlements in the access profile. Under Entitlement deprovisioning, select whether these revoke tasks should apply the revoke policy on their respective entitlements (Enforce each entitlement’s revoke policy), or whether they can bypass the individual entitlements’ policies (Bypass each entitlement’s revoke policy).In practice, choosing Bypass each entitlement’s revoke policy means that confirmation of revoking the access profile membership entitlement is understood as approval of the user losing access to some or all of the entitlements in the access profile, so individual requests for each entitlement are not needed.
4
Click Save.

Step 4: Set the membership automation for the access profile

In the Membership automation area of the page, click Edit and set the following:
1
Under Add and remove users based on, set the membership condition. Choose Users with entitlements and select one or more entitlements from the dropdown, or choose Expression and write a CEL expression. Users who are currently granted any of the entitlements you select become members of the access profile.
2
If necessary, in the Exclude users box, add any users who should not be members of this access profile, even if they currently have, or are later granted, the entitlements in the condition.
3
Under the Access changes heading, select how to manage changes to the list of members:
  • Leave the Grant and revoke entitlements on membership change toggle disabled if you want to update the list of members but take no other action.
  • Enable the Grant and revoke entitlements on membership change toggle if you want to update the list of members and kick off the membership and access changes that go with it.
4
In the Anomaly detection section, configure the safeguard that pauses the automation if too many members would be removed at once. The Removed members threshold (%) field sets the cutoff — for profiles with 100 or more members, if removing that percentage of members within a single hour would be removed, the sync pauses for review. The default is 20%. Disable Pause automation when anomalies are detected to turn the safeguard off entirely.
5
If you’re ready to start using the membership automation, click to turn on Enabled at the top of the page.
If you don’t want to start adding and removing members immediately, leave the toggle disabled and save your progress. You can enable the membership automation whenever you’re ready.
6
Click Save.
Done. Once you enable the membership automation, request tasks are immediately created for the users who match your membership automation condition. Users added to the exclusion list automatically request the access profile’s excluded from rule entitlement.

Pending members

While request tasks await approval, you’ll see a count of Pending members on the Members tab.
The Members page.
As request tasks are approved, users will be added to the Members list, and C1 will create access requests for the full contents of the access profile.

Safeguards for automated access changes

By default, C1 pauses any membership automation sync that would remove more than 20% of a profile’s members within a single hour. This safeguard applies to access profiles with 100 or more members. The threshold is configurable — you can adjust Removed members threshold (%) in the Anomaly detection section to set a different cutoff. This safeguard is the access profile circuit breaker. In the API and the C1 CLI, setting the bundle automation’s disableCircuitBreaker field to true is the same as turning off Pause automation when anomalies are detected. It’s separate from the automation circuit breaker, which rate-limits workflow automations.
The Anomaly detection section of the membership automation edit drawer, showing the Pause automation when anomalies are detected toggle and the Removed members threshold (%) field set to 20.

Turn off automatic safeguards on an access profile

Automatic safeguards are enabled by default on all access profiles, but you can turn them off temporarily or permanently as needed. To disable safeguards on a profile:
1
On a hybrid access profile’s Settings tab, in the Membership automation area, click Edit.For a role, click Edit on the Advanced line under Birthright membership instead.
2
In the Anomaly detection section of the drawer, disable Pause automation when anomalies are detected.
3
Click Save.

Review a paused membership automation sync

When a membership automation sync triggers a safeguard and is paused, you’ll see alerts on the main Access profile page and the impacted access profile’s details page alerting you to the fact. If your organization uses Slack, C1 admins will also receive a Slack message about the pause.
1
Navigate to the impacted access profile and click Review in the banner at the top of the page.
2
Review the list of access profile members staged for review.If the list of members looks correct, click Resume sync to tell C1 to proceed.If the list of members doesn’t look correct, click Go back and make changes as necessary in the Membership automation section of the page.

Frequently asked questions about access profile membership

A new sync is kicked off each hour. Click Sync now in the Membership automation area of the access profile’s Settings tab (Birthright membership for a role) to manually start a sync at any time.
No, when a new entitlement is added to a profile, current members do not receive any notifications. Notifications about approval or provisioning tasks for the new access (and any comments on these tasks) will be sent to approvers or provisioners, as needed.
Yes. If you need to manually add users to the access profile, navigate to the access profile’s Members tab and click Add users.