Replace Launch Plan Members
PUT/api/launch-plan/members
Replaces the whole member list; members left out are removed. A removed member's open steps become unassigned (recorded in each step's activity with reason member_removed); steps they already finished keep them as owner. Membership changes are recorded in the plan's activity.
launch_plan:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
members (array, up to 100), each:
user_id(required) — a user on this account.roles(required, may be empty) — any ofowner,ops,catalog,finance,implementer,sku. Roles decide default step owners.watcher(optional boolean) — receives the digest's whole-plan view.digest_opt_out(optional boolean).
Any other key on a member (e.g. a weekly_capacity_hours from an older client) is ignored.
Response: the new member list (as List Launch Plan Members). 422 when a user is not on this account. 404 {exists: false, message} when the account has no plan.
Authentication: Requires Bearer token with the launch_plan:write scope. The user needs the launch_plan.manage permission.
Request
Responses
- 200
- 401
- 403
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Unprocessable Content
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.