Move rules or sections in the Access and Data policy
PATCH/seb-api/v1/policy/access-and-data/positions
Submits an ordered list of moves. Each move repositions one rule or section into an explicit container (target.sectionId) using a position keyword (top/bottom/before/after) plus an optional anchor. Section subjects auto-carry their child rules in the same relative order. Default (baseline) rules are pinned at the bottom and cannot be moved or anchored on. All moves apply atomically; if any move fails, no DB changes or audit events are produced. The failing move's index is in the error details.
Request
Responses
- 200
- 400
- 403
- 404
- 500
Successfully applied all moves.
Bad request. error.code is one of VALIDATION_ERROR, FIELD_VALIDATION_ERROR, CONTIGUITY_VIOLATION, or INCOMPLETE_ARRAY; structured details vary by code. For per-move field errors the failing move index is in details.errors[].index.
Forbidden - Insufficient permissions or feature not enabled
Not found. error.code is one of NOT_FOUND or FIELD_REFERENCE_NOT_FOUND.
Internal server error.