Single sign-on

Require single sign-on, or stop

Whether members must sign in through the provider: then a member uses the workspace only from a session that did in the last day, and with tokens and keys once linked; held out otherwise, keeping their place.

PUT/workspaces/{workspace}/sso/required

Owners are never held, and outside collaborators are not asked. Requiring it needs a paid plan and you to have signed in through it yourself (you_linked); stopping never does. Recorded as sso.required or sso.not_required. Owners only, as people.

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: workspace with action set_sso_required, and the same inputs
Scope: An access token needs workspace:admin.

Path parameters

Name	Type	Required	Description
`workspace`	string	Yes	The workspace’s name, e.g. “acme”.

Body parameters

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

Name	Type	Required	Description
`required`	boolean	Yes	True to require it of members; false to stop.

Example request

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

Example response

A successful request answers 200 with:

{
  "required": 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 a token without the scope it needs.
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.