Removes an operator from the Network directory.
Drops the operator from the directory entirely. Escalation ladders that still reference the participant degrade gracefully (the operator is skipped during the ladder walk). Removing a participant that is not an enrolled operator yields `404 Not Found`. To keep the row but stop offering escalations, PATCH the status to `DISABLED` instead. Applies immediately.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The owning Network id.
uuidThe operator participant id.
uuidThe tenant identifier
Response Body
curl -X DELETE "https://api.fruxon.com/v1/tenants/string/networks/497f6eca-6276-4993-bfeb-53cbbbba6f08/operators/497f6eca-6276-4993-bfeb-53cbbbba6f08"{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Searches enrollable-operator candidates for the Add-operator picker.
A DB-paged, name-searchable page of curated directory Persons who could be enrolled as an operator here, each carrying the server's verdict: `status` (`ELIGIBLE` / `PROMOTABLE` — enrolling first classifies them as internal — / `INELIGIBLE`) and, when ineligible, a stable `ineligibleReason` code. Existing operators, external customers, disabled people, groups and ambient identities are all filtered out — nothing an admin can act on — so in practice every row is selectable. Holding a served (customer) grant in this Application is <b>not</b> a rejection: per design §3 an internal teammate may be served and an operator at once. The `servedHere` flag says so for display only. This backs the picker's server-side type-ahead so it no longer loads the whole tenant directory or the whole served set. The verdict is the same predicate the enroll path enforces, so a selectable candidate is one `POST` accepts. The literal `candidates` segment out-ranks the `{operator}` route, so there is no collision.
Partially updates an operator's live status, presence, role keys, and/or pool.
Live drain/disable, presence, and retagging: set the status to `DISABLED` to drain the operator, set the presence to `AWAY` to mark them stepped-away (both skip the operator in escalation resolution; the row and its role keys / pool survive so re-activating restores it), replace the role keys, or set/clear the pool. Omitted fields stay unchanged. Applies immediately.