RevertToFlatResponseDto

Example

JSON

{
  "assignments_moved": 0,
  "assignments_deduplicated": 0,
  "assignments_expired_dropped": 0,
  "assignments_dropped_scoped": 0,
  "nodes_deleted": 0,
  "organizations_preserved": 0,
  "schema_cleared": false
}

Properties

7 properties 7 required

assignments_moved number Required

Number of unique (identity, role) pairs reseated at the root node.

assignments_deduplicated number Required

Number of duplicate assignments collapsed during the dedupe pass.

assignments_expired_dropped number Required

Number of expired assignments (those whose `effective_to` was already in the past) that were discarded during the flatten. Expired rows grant no access; preserving them as unbounded root rows would silently reinstate dead access, so they're dropped. Surfaced explicitly so the admin sees the cleanup actually happened.

assignments_dropped_scoped number Required

With organizations enabled: number of assignments made at nodes beneath an organization that were dropped. Such a grant is scoped to one branch of one tenant; reseating it at the organization would widen it to the whole tenant and reseating it at the root would cross tenants, so it is removed instead. Always `0` without organizations.

nodes_deleted number Required

Number of hierarchy nodes deleted as part of the flatten: every non-root node without organizations, every node beneath an organization with them.

organizations_preserved number Required

With organizations enabled: number of organizations that stayed in place with their memberships. Always `0` without organizations.

schema_cleared boolean Required

Always `true` on success — the schema is wiped from `Application.settings`.

Was this page helpful?

Tell us how we can improve this guide.