Advanced Access Manager Pro writes access decisions across three locations: per-user and per-role rules in wp_usermeta with the aam_ prefix, plugin configuration in wp_aam_policy, and JSON Access Policies stored as the aam_policy custom post type. The plugin's UI walks one actor at a time, which is useful for editing and slow when an auditor asks for an inventory of what is actually active.

SleekView reads all three sources and exposes them as one dataset. Each row carries the rule scope (user, role, visitor, default), the policy name, the resource, and the action it controls.

AAM Pro keeps owning the enforcement and the per-request decisions. SleekView only adds the inventory surface, so saved views like Active policies on regulated post types or Visitor-scoped rules become a one-click reopen instead of a per-actor walkthrough.

AAM Pro is one of the most flexible access-control plugins in WordPress, which is also why its admin is built around editing rather than inventory. The audit question, how many active rules and against which resources, is the kind of thing every quarterly review asks, and the AAM Pro UI does not answer it directly. SleekView reads the same usermeta, options, and CPT rows AAM Pro persists and renders them as one sortable, filterable table.

The plugin keeps owning the rules, SleekView just surfaces the resulting state. Saved views travel with the site so audits stop being a one-off scramble, and filtered rows export as CSV when external reviewers ask for evidence.