Role-Based Scoping

How role-based filtering works on every list view.

What is scoping?

Every list view in the platform filters on the active role of the user:

• iga_admin / iga_auditor — tenant-wide
• iga_manager — only their direct reports
• iga_resource_owner — only their own entitlements
• iga_helpdesk — only open tasks that their role owns
• iga_user — only their own profile

On top of that, list views use server-side pagination via the offset and limit query parameters. Frontend wrappers use unwrapList(r.data) so they work with both Paginated<T> and plain T[] responses.

Scoped roles — delegated admin

Alongside the fixed roles there are scoped roles (Sprint extensibility, 2026-06-16): a capability set bound to a scope that resolves owner-anchored and fail-closed — the scoped objects are exactly the objects the identity owns (via ownership). No owned objects means no access — never a blanket grant. A typical use case is delegated onboarding of external organizations by their own org owner.

Further reading:

• Filter Dsl
• Advisor