What are C1 groups?

What can I do with a C1 group?
Key uses for these special groups include:- Organizing employees without creating custom IdP groups. C1 groups make it easy to create groups of employees who share key profile attributes or combinations of access.
- Specifying who is granted an access profile. An access profile can be requestable by, or automatically assigned to, a C1 group.
- Assigning a group as reviewer on a policy step. A C1 group can be set as a policy step reviewer.
What kind of groups should I make?
When considering what groups to make, think about how you want to organize your employees for access management, access profile, and policy reviews. Groups provide a flexible way to do so without needing to manage complex groups in your identity provider. Here are some ideas for groups you might create in C1:- Department or team-based groups: For example, “Marketing Team”, “Engineering Department”, “Sales”. This helps organize employees and manage access relevant to those teams.
- Role-based groups: For example, “Software Engineers”, “Data Analysts”, “Project Managers”. This is useful for assigning access based on job function.
- Location-based groups: For example, “Portland Office”, “London Team”. Useful if access varies by location.
- Project-based groups: For temporary teams working on specific projects, like “Spruce Mongoose Team”.
- Reviewer groups: Groups specifically created to be used as reviewers in policies. For example, “Security Reviewers”, “Legal Reviewers”.
Create a new C1 group
Create a C1 group by setting a rule for membership. C1 will dynamically add or remove members from the group based on their adherence to the rule.1
Navigate to Identities > Dynamic groups and click Create group.
2
Give your new group a name and add a description. Click Create group.
3
In the Membership automation section of the page, click Edit.
4
Choose how to form your membership rule:
- Use the Basic condition builder to construct a rule from a combination of entitlements and profile attributes (see note below on which profile attributes are supported), with the option to add and and or statements to refine the rule.
- Use the Expression field to to compose a CEL expression that describes the membership rule.
5
Click Preview to check the syntax of your membership rule.
Note that not all users who match the membership rule will be shown immediately when you click Preview.
Note that not all users who match the membership rule will be shown immediately when you click Preview.
6
Optional. In the Excluded users field, add the names of any users who should be excluded from this group, even if they match the membership rule.
7
When you’re satisfied, click Save. The Membership rule section syncs and updates the list of matching users.Depending on the number of users in your C1 installation, syncing might take some time. When syncing is complete, the Syncing label will be replaced by a Last sync timestamp.
Create a group from an existing entitlement
If a group already exists in your identity provider or another app, such as an Okta or Microsoft Entra ID group, you can use its membership as the starting point for a C1 group instead of rebuilding it by hand. C1 analyzes who holds the source entitlement and proposes a membership rule that covers as many of those people as it can, plus exact lists of the individual people the rule needs added or removed. You review the proposal and create an ordinary C1 group from it. This is called adoption. Use this when you want to move a provider group’s membership into C1, for example to use the group as an access profile audience or a policy reviewer group without maintaining it in the provider.Before you begin
- You must have the Super Administrator role. Other roles, including Read-Only Administrator, can’t create a group this way.
- Your tenant must allow groups to hold individually added members. C1 groups created this way hold some members individually. If this isn’t enabled for your tenant, the Use an existing entitlement option is unavailable and C1 tells you why.
- The source needs a completed full sync. For a source backed by a connector, such as an Okta or Entra ID group, the connector’s latest sync must be a successful full sync, and C1 must have finished processing it. If a sync is running, partial, or failed, analysis stops and tells you to wait for or run a full sync.
- The source must represent membership. A source can be an app’s access entitlement, an entitlement synced from a connector, an entitlement you manage in C1, or a C1 role. An entitlement that combines multiple connectors, or that represents exclusion, owner, or admin access, can’t be used.
- You must be able to read the source entitlement.
Start from the Dynamic groups page
1
Navigate to Identities > Dynamic groups and click Create group.
2
Under Creation method, choose Use an existing entitlement and click Continue. (Start from scratch creates a group as described in Create a new C1 group.)
3
Under Source, select the app and then the entitlement to use as the starting point. Click Analyze.
4
Wait for the analysis to finish. You can close the window while it runs. Analysis continues, and you can reopen it from the Adoption history tab.
5
Review the results, as described below, then click Continue.
6
Under Group details, enter a name (at least 3 characters) and an optional description. C1 prefills both from the source entitlement. Click Create group.
7
When C1 shows Group created, click View group to open the new group.
Start from an entitlement
To start from the entitlement itself, open the entitlement’s details page, click the … (more actions) menu, and choose Create group from entitlement. The Create group window opens at the Source step with that entitlement already selected. Continue from the Analyze step above.Review the analysis
The Review step shows what C1 found in the source and how it proposes to rebuild that membership.- Recommendation. C1 recommends either Rule-based membership, where a rule adds and removes members as user attributes change, or Individual membership, where C1 adds the listed users and later changes to the source don’t update the group.
- Rule expression. The proposed membership rule, written as a CEL expression.
- Rule coverage. How many of the eligible people the rule covers, such as “Rule coverage: 480 of 500 eligible people.”
- Inclusions. People the rule doesn’t match who still held the source entitlement. C1 adds them to the group individually.
- Exclusions. People the rule would match who didn’t hold the source entitlement. C1 adds them to the group’s exclusion list so the rule doesn’t add them. This tab also lists source members who can’t be adopted, with the reason for each.
Source members who can’t be adopted
C1 doesn’t create users or accounts, so a source member can be left out of the new group. Reasons include an account that isn’t linked to a C1 user, a linked user who is missing, deleted, disabled, or not a person, an app account whose invitation hasn’t been accepted, and a principal type that adoption doesn’t support. When any source members can’t be adopted, the Review step warns you, and you must select I understand these source members will not be added to the group. before you can continue. Open Exclusions first to see who is affected and why. If the source has no eligible users, C1 asks you to choose another entitlement or start from scratch.Manage adoption jobs
Each analysis is saved as a job. The Adoption history tab on the Dynamic groups page lists every job with its source entitlement, app, status, created group, and last update. Select a job to reopen it.
A failed job can’t be resumed. If no group was created, click Start a new analysis to analyze the source’s current membership. If C1 had already created the group, click Manage group and finish setting it up there. If you leave while the group is being created, creation continues. Check Adoption history for its status.
If C1 can’t confirm that an analysis started, check Adoption history before starting another one. Each analysis creates a separate job.
What adoption does and doesn’t do
- It’s a one-time setup. The new group is an ordinary C1 group. Later changes to the source entitlement, or to who holds it, don’t update the group. The rule keeps evaluating user attributes like any other group rule, and you can edit the rule, inclusions, and exclusions afterward.
- It never changes the source. C1 doesn’t write to your identity provider or app, and it doesn’t change the source entitlement or role assignments.
- It doesn’t create users or accounts. Only existing, enabled C1 users become members.
Duplicate a C1 group
Need a group that’s similar to one that already exists? To save time, you can duplicate an existing group and then make adjustments as needed.1
On the Dynamic groups page, find the group you want to duplicate.
2
Click the … (more actions) menu, then choose Duplicate.
Manually add users to a group
If you need to manually add users to the access profile who do not match the membership automation condition, click Add users. The users you add will be shown in the list of members, with a notation that they were added manually, rather than by membership automation.Review group membership in an access review campaign
You can include C1 group memberships in an access review campaign, including memberships in groups that C1 fills automatically from a membership rule. Denying a member removes them from the group. If the membership rule added them, C1 also adds them to the group’s exclusion list so the rule doesn’t add them back. For how to select group memberships and what reviewers can decide, see Choose what to review.Frequently asked questions about C1 groups
How often does the membership rule sync?
How often does the membership rule sync?
A new sync is kicked off each hour.
Can users request access to a C1 group?
Can users request access to a C1 group?
Yes. Add the group’s entitlement to an app’s requestable entitlements or to an access profile like any other entitlement, and users can request group membership with the same approvals, durations, and revocation as other requestable access.Members added through a request aren’t removed by the group’s membership automation rule — the same protection that already applies to users you add manually.
How do I fetch C1 groups with the API?
How do I fetch C1 groups with the API?
There is no dedicated groups endpoint in the C1 API. C1 groups are resources of the group resource type in the C1 app, so you fetch them with the app resource endpoints:
- Find the group resource type for the C1 app:
GET /api/v1/apps/{app_id}/resource_types - List the group resources of that type:
GET /api/v1/apps/{app_id}/resource_types/{app_resource_type_id}/resources - To get a group’s entitlements (such as its member entitlement), list the entitlements associated with that resource:
GET /api/v1/apps/{app_id}/entitlements/resource_types/{app_resource_type_id}/resources/{app_resource_id}
app_id is the ID of the built-in C1 app.