Skip to content
Connect an agent

Organisations

Choose who may read the audit log and the call history

Replaces the roles and people who may read the audit log and the call history besides the owner and admins.

PUT/orgs/{org}/log-access

TL;DR

QuestionAnswer
What does it do?Choose who may read the audit log and the call history.
What does it take?A JSON body of type LogAccessInput.
What does it return?Status 200 with a body of type LogAccess.
What can go wrong?400 the body is not valid; 401 not signed in; 403 not the owner (orgs.forbidden), or the request came from an origin that may not make changes; 404 no such organisation, or the caller is not a member of it; 422 someone chosen is not a member (validation.failed); 429 too many requests; 503 organisations are not set up on this server. Every failure uses the one error envelope.

What it does

Replaces the roles and people who may read the audit log and the call history besides the owner and admins. The owner only; recorded in the audit log.

Path parameters

FieldTypeRequiredDescription
orgstringyesThe organisation's id or its slug.

Request body

The body has the type LogAccessInput.

FieldTypeRequiredDescription
roles("member" | "reader")[]yesRoles let in besides the owner and admins.
membersstring[]yesMembers let in by name, by account id, at most 100.

Responses

StatusMeaningBody
200The setting now.LogAccess
400The body is not valid.ErrorResponse
401Not signed in.ErrorResponse
403Not the owner (orgs.forbidden), or the request came from an origin that may not make changes.ErrorResponse
404No such organisation, or the caller is not a member of it.ErrorResponse
422Someone chosen is not a member (validation.failed).ErrorResponse
429Too many requests.ErrorResponse
503Organisations are not set up on this server.ErrorResponse

Response body

A 200 answer has the type LogAccess.

FieldTypeRequiredDescription
roles("member" | "reader")[]yes
membersobject[]yes
members[].userIdstringyes
members[].emailstringyes
members[].role"owner" | "admin" | "member" | "reader"yes

See also

DocWhy
API referenceEvery endpoint, and the error envelope
SchemasEvery request and response type
Tool referenceThe operations as callable tools