Skip to main content

Dynamic Groups

Last updated: 2026-05-20

A dynamic group recomputes its membership from rules instead of being managed by hand. You define one or more conditions that an entity must match, and the rule engine keeps the membership in sync.

Permissions — listing dynamic groups needs group:read. Creating or editing rules needs group-rule:create / update / delete. Running an ad-hoc sync needs group-rule:execute. In the user shell, dynamic groups show an "admin feature" notice — use the admin shell to manage them.


When to use a dynamic group​

  • Audiences whose membership changes daily (e.g. "all users active in the last 7 days")
  • Beta programmes opted into via a tag or attribute
  • Feature-flag groups computed from a property on the User entity
  • Resource collections grouping files / vibedecks by metadata

For everything else — small teams, security groups, ad-hoc projects — a STATIC group is simpler and faster.


Membership types​

TypeBehaviour
STATICMembers added/removed manually only
DYNAMICRule-driven; manual edits are blocked
HYBRIDRule-driven membership plus manual additions on top

Set the membership type when creating the group, or change it later via the Settings tab. Switching to DYNAMIC requires at least one enabled rule.


Browsing dynamic groups​

Open /groups/dynamic. The page lists every group in the workspace whose membershipType is DYNAMIC or HYBRID.

From the list you can:

  • Click a group to open its detail page
  • Click New Dynamic Group to start creating one (routes you to the create wizard with membership type pre-set)

Creating a rule​

  1. Open the rule builder at /groups/dynamic/new (or /groups/dynamic/:groupId/rules to edit an existing rule on a specific group).
  2. Fill in:
  • Rule name — required, human-readable
  • Description — optional
  • Entity type — User, App, File, VibeDeck, Resource, or Group
  • Assigned role — role given to members added by this rule (MEMBER, MODERATOR, etc.)
  • Auto-add — when toggled on, entities that newly match are added automatically
  • Auto-remove — when toggled on, members that stop matching are removed automatically
  1. Add one or more conditions:
  • Field — the attribute to test (e.g. email, metadata.department, tags.team)
  • Operator — EQUALS, NOT_EQUALS, CONTAINS, IN, NOT_IN, GT, LT, ... (varies by field type)
  • Value — the value(s) to compare against
  1. Click Add Condition to add more rows. Multiple conditions are AND-combined.
  2. Click Save Rule.

Tip — click Test Rule before saving to see a structural preview of the generated rule definition. This is informational; it does not actually evaluate the rule against your data.


Editing a rule​

  1. From the group's detail page, open the Overview tab.
  2. Scroll to Membership Rules and click a rule.
  3. Modify fields and click Save.

You can also disable a rule (toggle enabled off) without deleting it.


Deleting a rule​

From the rule row, click the trash icon and confirm. Members added by the rule remain in place until you also run a sync with autoRemove: true.


Running a sync​

Rules normally sync on their own schedule. To force an immediate evaluation:

  1. From the rule row, click Sync Now.
  2. The rule engine evaluates all candidate entities and shows the result in a toast:
  • N entities evaluated
  • X members added
  • Y members removed
  1. A GroupRuleSyncExecution record is appended to the rule's history.

Each execution records duration, errors, and status (PENDING, IN_PROGRESS, COMPLETED, FAILED, CANCELLED, TIMEOUT).


Execution history​

Each rule keeps a paginated history of its sync executions. Open the rule's detail page to see:

  • Start / end timestamps
  • Status
  • Counts: entities evaluated, members added, members removed
  • Duration (executionTimeMs)
  • Any error payload

See also​