Update a workspace's security settings

Turn delegated bypass and validity checks on or off for a workspace.

PATCH/workspaces/{workspace}/security/settings

Owners only.

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: security with action update_workspace_settings, and the same inputs
Scope: An access token needs security:write.

Path parameters

Name	Type	Required	Description
`workspace`	string	Yes	The workspace’s slug, e.g. “flagon-io”.

Body parameters

Send a JSON object. Names are snake_case, as in responses; the camelCase spelling is accepted too.

Name	Type	Required	Description
`delegated_bypass`	boolean	No	Bypasses need an owner’s or the repository’s admins’ approval.
`validity_checks`	boolean	No	Ask issuers whether secrets still work, where that can be done safely.

Example request

curl -X PATCH https://api.g1t.sh/workspaces/flagon-io/security/settings \
  -H "Authorization: Bearer $G1T_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "delegated_bypass": true
  }'

Example response

A successful request answers 200 with:

{
  "settings": {
    "delegated_bypass": true,
    "validity_checks": true
  },
  "activated": true
}

Errors

A failed request answers with one of these statuses and a body like {"error": {"code": "not_found", "message": "Repository not found."}}. See errors.

Status	Code	When
401	`unauthenticated`	A token is required, or the one sent is not valid.
403	`forbidden`	The token is valid but not allowed to do this, such as a member-only change or an agent token outside its repository.
404	`not_found`	It does not exist, or you cannot see it.
409	`conflict`	The request conflicts with the current state.
422	`invalid`	The input is not valid. `message` says which field and why.