Set two-factor enforcement
Requires every member to have two-factor authentication, or stops requiring it. While it is on, a member without two-factor gets 403 on every workspace endpoint until they enrol. You must have two-factor set up yourself before turning it on.
Requires the admin role on the workspace.
An OpenID Connect access token issued by Keycloak, acting as the signed-in user.
In: header
Path Parameters
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
true to require two-factor authentication from every member, false to stop requiring it.
Response Body
application/json
curl -X PUT "https://api-next.centralcsp.com/v1/workspaces/string/mfa" \ -H "Content-Type: application/json" \ -d '{ "required": true }'{ "id": "string", "name": "Acme", "ownerId": "string", "requiresMfa": true, "disableAiIntegrations": true, "plan": { "slug": "pro", "name": "Pro", "features": [ "compliance", "alerting", "api_keys" ] }, "role": "admin", "createdAt": "2019-08-24T14:15:22Z", "updatedAt": "2019-08-24T14:15:22Z"}Set AI tool access PUT
Cuts every AI tool off from this workspace, or lets them back in. While it is off, existing MCP keys are refused and no new one can be created.
Overview
Give an AI client read and limited write access to CentralCSP over the Model Context Protocol, signed in as you, with your own roles and plan.