Project Settings

A project carries a small set of settings of its own, apart from the project row. Today there is one: payload_min_role, the lowest built-in role that may read the request and response bodies payload capture stored for the project’s traffic.

value	who reads the captured bodies of this project’s requests
`member` (default)	the project’s members and admins
`viewer`	its viewers as well

Admins always may. Whether anything is captured at all is still the deployment-wide log settings, and who sees the request-log rows themselves is covered in who sees which request logs.

Read the settings#

Any role on the project may read them.

curl -s https://control.example.com/api/v1/projects/$PROJECT_ID/settings \  -H "Authorization: Bearer $ROLTER_SESSION_TOKEN"

{ "payload_min_role": "member" }

Change them#

Changing a project’s settings takes the admin role on the project (or on its team or org). The body names every setting; an unknown field is rejected.

curl -s -X PUT https://control.example.com/api/v1/projects/$PROJECT_ID/settings \  -H "Authorization: Bearer $ROLTER_SESSION_TOKEN" \  -H "Content-Type: application/json" \  -d '{"payload_min_role": "viewer"}'

The response echoes the stored settings. The change is recorded in the audit log as project.settings.update, with the value it was set to.

status	when
`200`	saved
`400`	`payload_min_role` is not `member` or `viewer`
`401`	no valid session or admin token
`403`	the caller is not an admin of the project
`404`	no such project

In the dashboard the same switch is Viewers can read captured payloads, in the project’s ⋯ menu in the scope switcher (Project settings).