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.
AuthorizationBearer <JWT>An OpenID Connect access token from signing in to CentralCSP, acting as the signed-in user.
workspaceId*stringThe workspace's id.
application/json- body
required*booleantrue to require two-factor authentication from every member, false to stop requiring it.
A workspace.
application/json- response
id*stringUnique identifier of the workspace.
name*stringDisplay name.
ownerId*stringUser who owns the workspace. The owner can do everything, including transferring ownership and deleting the workspace.
requiresMfa*booleanWhen true, a member without two-factor authentication is refused on every workspace endpoint until they enrol.
disableAiIntegrations*booleanWhen true, AI tools cannot reach this workspace.
plan*|The plan of the current subscription, or null when the workspace has no active subscription and cannot collect reports.
role*|Your role in this workspace, or null when you own it without being a member.
createdAt*stringWhen the workspace was created.
date-timeupdatedAt*stringWhen the workspace was last changed.
date-timecurl -X PUT 'https://api.centralcsp.com/v1/workspaces/01936b7a-6f2e-7c31-9a4d-2f8e1c5b7d90/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
Turns AI tool access to this workspace off, or back on. While it is off, AI tools connected to any member's account get 403 on this workspace.
Vue d'ensemble
Donnez à un client IA un accès en lecture et en écriture limitée à CentralCSP via le Model Context Protocol, sous votre identité, avec vos rôles.