Skip to main content

Group Settings

Last updated: 2026-05-20

The Settings tab on a group lets administrators manage three different things:

  1. Group configuration — name, description, visibility, membership policy, nesting policy
  2. Key-value settings store — arbitrary keyed configuration with optional scope
  3. RBAC role assignments — assign workspace-level RBAC roles to the group as an actor, so every user member inherits them

The Settings tab is only available in the admin shell (/groups/:groupId/settings). In the user shell, the tab is hidden.

Permissions — group:update for configuration changes, group-setting:{create,update,delete} for the key-value store, and group:update again for role assignments.


1. Group configuration​

Open /groups/:groupId/settings. The top section shows editable form fields:

FieldNotes
NameMust remain unique in the workspace
DescriptionFree text
VisibilityPRIVATE, INTERNAL, PUBLIC_LINK, DIRECTORY_LISTED
Membership typeSTATIC, DYNAMIC, HYBRID — switching to DYNAMIC requires at least one membership rule
Composition modeHOMOGENEOUS / HETEROGENEOUS
Allowed entity typesMulti-select: User, App, File, VibeDeck, Resource, Group
Allow member invitesToggle
Require approval to joinToggle
Max membersOptional integer cap
Allow nested groupsToggle
Max nesting depthOptional integer

The page tracks unsaved changes — the Save Changes button is enabled only when the form differs from the persisted group.

System groups (isSystemGroup: true) show a read-only banner — settings cannot be modified.


2. Key-value settings store​

Below the configuration section, a CRUD panel lets you store arbitrary {key, value, scope} records on the group.

Adding a setting​

  1. Click Add Setting (or expand the inline form).
  2. Enter a Key (unique within the group).
  3. Enter a Value — plain text or JSON.
  4. Pick a Scope: group, workspace, or global.
  5. Optionally add a Description.
  6. Click Save.

Editing or deleting​

  • Hover a row → click the edit icon to update the value, scope, or description.
  • Click the trash icon to delete a single setting.
  • Use the row checkboxes + Delete Selected to bulk-delete settings.

Setting scopes​

ScopeDescription
groupApplies to this group only
workspaceSuggests workspace-wide configuration; consumed by integrations that read all groups
globalPlatform-level setting, typically read-only and managed by system groups

The isOverride flag marks settings that intentionally override an inherited or default value.


3. RBAC role assignments​

Under RBAC Role Assignments, you can grant the group itself one or more workspace RBAC roles. When a user is a member of the group, the role applies to them transitively — including via hierarchy inheritance.

  1. Select a role from the Available roles dropdown.
  2. Optionally provide a scopeResourceType and scopeResourceId to scope the role to a specific resource (e.g. a project).
  3. Optionally set an expiresAt date.
  4. Click Assign Role.

Existing assignments are listed below the form. Click the Remove icon on an assignment to revoke it.

Each assign/remove is audited as GROUP_ROLE_ASSIGNED / GROUP_ROLE_REMOVED in the activity feed.


Lifecycle actions​

The Settings tab also exposes lifecycle actions:

  • Archive — soft-delete the group (status becomes ARCHIVED). Members lose access but the group can be restored.
  • Restore — bring an archived group back to ACTIVE.
  • Delete — permanently delete (OWNER only). Irreversible.
  • Transfer Ownership — hand the group to another member who becomes the new OWNER; the current owner becomes ADMIN.
  • Clone — copy this group into a new one, with an option to copy members too — see bulk operations.

Who can manage settings?​

ActionRequired role / permission
Edit configuration formOWNER, ADMIN, or group:update workspace permission
Create / update / delete key-value settingsOWNER, ADMIN, or matching group-setting:* permission
Assign / remove RBAC rolesOWNER, ADMIN, or group:update
Transfer ownershipOWNER only
Delete groupOWNER only

See also​