> ## Documentation Index > Fetch the complete documentation index at: https://docs.ravenna.ai/llms.txt > Use this file to discover all available pages before exploring further. # Groups > Create user groups manually in Ravenna or sync them from identity providers like Okta and Google Workspace to manage access and assignments. User groups organize workspace members into collections for easier collaboration and management. Create groups manually or sync them automatically from identity providers like Google Workspace to coordinate work and manage access within your workspaces. ## Mental model User groups are collections of organization members. They serve as reusable references for access control, workflow assignments, and form fields. Groups can be created manually or synced automatically from identity providers (Okta, Google Workspace, Slack). Groups are organization-scoped. A group exists at the organization level. However, which groups appear in form fields depends on the workspace. Manually created groups only appear in workspaces they are assigned to. Groups synced from identity providers (Okta, Google Workspace, Slack) appear in all workspaces. *** ## Manual vs synced groups | Aspect | Manual groups | Synced groups | | --------------------------------- | -------------------------- | ------------------------------------------------- | | **Source** | Created in Ravenna | Imported from IdP (Okta, Google Workspace, Slack) | | **Membership management** | Edited directly in Ravenna | Managed in the IdP, synced to Ravenna | | **Membership editing in Ravenna** | Yes | No (read-only in Ravenna) | | **Sync behavior** | N/A | Automatic membership updates from IdP | | **Source indicator** | None | Shows source integration | Both types can be used identically in access levels, workflows, forms, and custom fields. *** ## Groups in the platform **Access level mapping**: Groups map to access levels on applications. When a user is granted access at a specific level, they can be added to the corresponding IdP group via workflow actions, enabling automated provisioning. **Workflow approvers**: Assign a group as the approver pool for workflow approval steps. Any member of the group can approve. **Ticket approval rounds**: Select user groups when creating approval rounds on tickets. Groups are immediately expanded into individual users server-side when saved, unlike approval templates which persist group IDs. This maintains the existing approval round behavior where only concrete users are stored as approvers. **Form fields**: The "User group select" custom field type lets requesters select a group when creating a ticket. Admins can configure an **allowlist** on the field to restrict which groups appear as options, and optionally filter groups by **source** (e.g., only Okta groups or only Ravenna-native groups). These constraints are enforced in both the form UI and the agent tool when the agent resolves groups conversationally. **Form audience access control**: Groups can define form audiences. When a form's audience type is set to "Specific" (User Groups), only members of the selected groups can see and submit that form. This filtering is server-side and applies to the Portal, Slack form selection, and ticket creation flows. **Agent rules**: Groups can be referenced in agent rules when the agent needs to identify team membership or route requests. The Group Lookup tool respects workspace visibility, allowlist, and source constraints configured on form fields. *** ## Constraints and gotchas * Group names must be unique within the organization. * Synced group membership cannot be edited in Ravenna. Changes must be made in the source identity provider. * Groups are organization-scoped, but their visibility in user group select fields is workspace-aware. Manually created groups only appear in workspaces they are assigned to, while synced groups are visible across all workspaces. * Synced groups appear alongside manual groups in the UI with a source indicator. * Multiple identity providers can sync groups simultaneously. Okta groups, Google Workspace groups, and Slack user groups can all coexist. * Deleting a group that is referenced in access levels, workflows, or forms may break those references. * When duplicating a request type across workspaces, any allowlist and source filter configured on user group select fields are stripped because group IDs may differ between workspaces.