# flow2act · Update an approval group

Rename a group or replace its member selection with revision protection.

Use the latest revision and an Idempotency-Key. Member changes take effect on the next permission check, including gates already waiting. Removing a member does not undo an earlier decision. Group IDs and published flow definitions stay fixed. Integration keys cannot administer approval permissions. needsMemberReview signals a pre-existing assignment: saving replaces it with exactly the selected people.

## PUT /v1/approval-groups/{groupId}

Authentication: FLOW2ACT_ACCESS_TOKEN from flow2act sign-in
Required tenant header: X-Organization-Id.
Required user permissions: Administrator or Sandbox developer required. The API checks current membership, roles, key scopes and resource permissions on every request. Documentation visibility grants no access.

## Input parameters
- name (string, required): min length 1 · max length 80
- accessScope (string, optional): min length 1 · max length 60 · default "general"
- memberIds (array, optional): max items 1000 · default []
- revision (integer, required): min 1 · max 9007199254740991

## Request example (replace example IDs)

```sh
curl -X PUT "https://api.flow2act.com/v1/approval-groups/10000000-0000-4000-8000-000000000009" \
  -H "authorization: Bearer $FLOW2ACT_ACCESS_TOKEN" \
  -H "x-organization-id: 10000000-0000-4000-8000-000000000001" \
  -H "idempotency-key: example-update-group-001" \
  -H "content-type: application/json" \
  --data-raw '{
  "name": "Operations",
  "memberIds": [
    "10000000-0000-4000-8000-000000000006"
  ],
  "revision": 1
}'
```

Source: /docs/update-group
Full schemas: /docs/openapi.json