30 days free. No credit card. Full access from the moment you connect your site.

Start free trial

The “Who can access” options

Every option in the User Access dropdown, explained — from locking a resource to opening it to a role, capability, specific users, or a membership.

Across the AcrossAI plugins, every ability and every MCP server has a User Access setting. A single Who can access dropdown decides who is allowed — and choosing an option reveals the controls for it. One rule always holds: administrators always have access, whatever you pick.

Here is every option, in order.

1. No user access added by admin

The Who can access dropdown set to No user access added by admin

The default. No rule has been set, so the resource is locked to everyone except administrators. Use this when a feature should stay admin-only until you deliberately open it up.

2. Everyone (no restriction)

The Who can access dropdown set to Everyone (no restriction)

The opposite: every user is allowed, with no further checks. There are no extra controls to fill in.

3. WordPress Role

The WordPress Role option with checkboxes for Administrator, Editor, Author, Contributor and Subscriber

Restrict by role. Tick one or more roles — Administrator, Editor, Author, Contributor, Subscriber, plus any custom roles on your site. A user is allowed if they have any ticked role. Leaving all boxes unchecked denies everyone (except administrators).

4. Users

The Users option with a search-by-username-or-email field and a selected user tag

Pick specific people. Search by username or email, then select one or more users; each chosen person appears as a removable tag. Only those exact users are allowed (administrators always are, regardless of the list).

5. WordPress Capability

The WordPress Capability option with a long checklist of capability slugs

Restrict by capability — the granular permissions behind roles (edit_posts, manage_options, activate_plugins, and so on). The list is built from every role on your site, so capabilities added by other plugins (WooCommerce, Members, and the like) appear automatically. A user is allowed if they hold any ticked capability.

6. BuddyBoss Profile Type

The BuddyBoss Profile Type option with checkboxes for each profile type

If you run BuddyBoss, restrict by profile type (member type). Tick the profile types that should have access; a user is allowed if they’re assigned to any ticked type. This option only appears when BuddyBoss is active and the feature is enabled.

7. MemberPress Membership

The MemberPress Membership option with checkboxes for each membership plan

If you sell access with MemberPress, restrict by membership. Tick the plans that should unlock the resource; a user is allowed if they have an active subscription to any ticked membership. Like BuddyBoss, this only appears when MemberPress is active and enabled.

All checks are “any of”: for roles, capabilities, profile types and memberships, holding any one of the ticked items grants access. And administrators are always allowed. See How access is decided for the exact order.

Was this page helpful?