Update the user information in the context of a repository.
Repositories
Update the user information in the context of a repository.
Access control rules
- The requester must have access to the repository, they can update their own information.
- Repository admins can update any users’ information.
PATCH
Update the user information in the context of a repository.
Documentation Index
Fetch the complete documentation index at: https://docs.cantina.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Body
application/json
Update User information in the context of a repository.
When the interests are deleted it will use the user's default notification interest.
When the frequency is deleted it will use the user's default notification frequency.
Available options:
immediate, daily, default Specifies whether the user wants to receive immediate notifications for findings with specific severities.
Role the user has in the repository.
Allowed changes:
| From | To client | To judge | To triager | To reviewer | To admin |
|---|---|---|---|---|---|
| Client | No-op | Ok | Ok | No | Not in competitions |
| Judge | Ok | No-op | Ok | No | Yes |
| Triager | Ok | Ok | No-op | No | Yes |
| Reviewer | No | No | No | No-op | No |
| Admin | Ok | Ok | Ok | No | No-op |
Available options:
client, reviewer, judge, triager, admin Asset group IDs for filtering finding notifications.
Safe harbor asset notification preference.
Response
Update successful