FruxonDocs
AgentsCollaborators

Adds or updates a collaborator's access to an agent.

Grants the given user the specified role on this agent, or upgrades/downgrades their existing role. Requires Admin on the agent; admins cannot demote the last remaining Admin. Roles map to capabilities as: Viewer (read only), Editor (read + edit draft + deploy revisions), Admin (everything including managing collaborators, budgets, and deletion). To remove access entirely use `DELETE /v1/tenants/{tenant}/agents/{agent}/collaborators/{user}`.

PUT
/v1/tenants/{tenant}/agents/{agent}/collaborators
AuthorizationBearer <token>

JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.

In: header

Path Parameters

agent*string

The agent ID.

tenant*string

The tenant identifier

The collaborator details.

userId*string|null

The FruxonUser ID to grant access to.

role?string

Defines the access level a collaborator has for an agent. Wire form is UPPER_SNAKE per project convention; Unspecified = 0 is the AIP-126 zero-sentinel.

Value in"UNSPECIFIED" | "VIEWER" | "EDITOR" | "ADMIN"
alertPreferences?

Per-collaborator alert preferences stored as JSONB on AgentCollaborator. All properties default to true so existing collaborators keep receiving all alerts. To add a new alert type, add a bool property here and register it in AlertTypeRegistry.

[key: string]?never

Response Body

curl -X PUT "https://api.fruxon.com/v1/tenants/string/agents/string/collaborators" \  -H "Content-Type: application/json" \  -d '{    "userId": "string"  }'
{
  "agentId": "string",
  "userId": "string",
  "role": "VIEWER",
  "status": "PENDING",
  "alertPreferences": {
    "errorAlerts": false,
    "accessRequestAlerts": false,
    "budgetAlerts": false
  },
  "createdAt": 0,
  "modifiedAt": 0,
  "tenantId": "00000000-0000-0000-0000-000000000000"
}
Empty
Empty
Empty
Empty