Restrict User Access models membership as access levels rather than products. Levels are stored as the rua_level custom post type, and assignments live in user meta with the level ID, the start timestamp, and an expiry timestamp where the level was given a duration. The plugin's API exposes rua_get_user()->add_level(), ->has_level(), and ->get_level_expiry() for programmatic work, but the admin treats levels primarily as configuration screens — capability sets, content rules, redirect targets — rather than as rosters.

That means there isn't a default "who's on this level, when do they expire, when did they last log in" view. Listing the members of a level means filtering the users screen by capability or running a custom query against user meta. Multi-level users (someone on Gold and Beta) appear once in the user list with no indication of which levels they belong to. Expiry-driven workflows — surfacing accounts that lapse in the next 7 days, sweeping expired accounts off a level, comping extensions — sit outside the default UI.

SleekView reads rua_level joined to user meta and produces a per-level roster with member, last login, expiry, and assignment source as columns. The expiry sort is the renewal-risk list. The members-on-multiple-levels view is one filter.

Restrict User Access is a clean piece of engineering for access control, but its admin is built around configuring levels rather than operating on the members assigned to them. That's a sensible default — the level is what controls capability — but it means most of the questions that come up in day-to-day membership work don't have a one-screen answer. Which Gold members lapse in the next 7 days? Which users hold both Gold and Beta? Which Silver members haven't logged in this month and are likely to churn at renewal? RUA stores all the data to answer those, just not in a way the level-config screens surface.

SleekView's per-level roster fills that gap by reading the same user meta RUA already maintains and rendering it as columns ops can sort and filter. The renewal-risk list is a sort by expiry. The dormant cohort is a filter on last login.

The access review is the roster filtered to expired. None of this changes RUA's underlying access model — it gives the operator a workspace where the questions are one filter away.