# flow2act · Create an approval group

Create a named approval team and select people from the organization directory.

Administrator user token required; Sandbox developers may manage Sandbox groups. memberIds are person IDs from GET /v1/organization/directory in the same organization/environment. Pending invitation profiles may be selected; decisions require a linked active user and active organization membership. Empty groups are allowed for preparation. Use the stable group ID in approval nodes. Requires Idempotency-Key.

## POST /v1/approval-groups

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 []

## Request example (replace example IDs)

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

## Response excerpt

```json
{
  "id": "10000000-0000-4000-8000-000000000009",
  "name": "Operations",
  "revision": 1,
  "memberIds": [
    "10000000-0000-4000-8000-000000000006"
  ],
  "needsMemberReview": false
}
```

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