Skip to main content
PATCH
Update user permissions

Authorizations

Authorization
string
header
required

Use Authorization: Bearer

Path Parameters

project_id
string<uuid>
required

UUID of the project

permission_id
string<uuid>
required

UUID of the permission record

Body

application/json
permissions
enum<string>[]
  • CAN_PERFORM_ADMIN_ACTIONS: Full administrative access
  • CAN_VIEW_DATA: Read-only access to project data
  • CAN_IMPERSONATE_OTHER_USERS: Impersonate other users in API calls (contact Clarifeye to enable)
Available options:
CAN_PERFORM_ADMIN_ACTIONS,
CAN_VIEW_DATA,
CAN_IMPERSONATE_OTHER_USERS
Example:
profile
enum<string>
default:contributor

Update the user's profile on the project.

Available options:
tech,
contributor,
user

Response

Permissions updated successfully

id
string<uuid>
user
object
permissions
enum<string>[]
  • CAN_PERFORM_ADMIN_ACTIONS: Full administrative access
  • CAN_VIEW_DATA: Read-only access to project data
  • CAN_IMPERSONATE_OTHER_USERS: Impersonate other users in API calls (contact Clarifeye to enable)
Available options:
CAN_PERFORM_ADMIN_ACTIONS,
CAN_VIEW_DATA,
CAN_IMPERSONATE_OTHER_USERS
profile
enum<string>
default:contributor

Profile of the user on the project. The profile shapes the UI surface a user sees (sidebar, available views) and complements the fine-grained permissions list.

  • tech: Technical profile with access to advanced/technical interfaces
  • contributor: Default profile for users who contribute to the project
  • user: End-user profile with the most restricted UI surface
Available options:
tech,
contributor,
user