Access settings and WordPress roles

Control who can see and change folders. Plathix Pro lets you choose Full, Upload, View, or None for each WordPress role. WordPress permissions still apply. If WordPress does not allow an action, Plathix does not add it.

See Plathix PRO

How to set access

Open Plathix → Settings → Access. Then choose the level you want for each role.

1. Open Plathix → Settings → Access.

   Every WordPress role on your site is listed with its current access level.

   

2. Find the WordPress role you want to change.

   Roles appear in the left column, their access level in the right one.

3. Choose Full, Upload, View, or None for that role.

   Open the dropdown next to the role and pick a level, then press Save Settings.

   

Which level should I choose?

• Use Full when the role should organize files and manage the folder structure.
• Use Upload when the role should organize files but not change the folder tree.
• Use View when the role should see folders but not change them.
• Use None when Plathix should not be available to that role.

Four levels of access

Choose what each WordPress role can do inside Plathix. These levels control the folder workspace, but they do not switch every Plathix feature on or off. Ready Folder Sets, Replace Media, SVG controls, imports and exports, galleries and shortcodes, ZIP downloads, the Audit Log, and plugin settings may also use WordPress permissions or feature-specific checks.

Access levels are only one part of Plathix permissions. The role tables below show exactly what Full, Upload, View, and None change. Features with separate permission rules are called out where needed.

WordPress permissions still come first

Plathix adds a folder access layer. It does not replace the WordPress role system.

• A Contributor can be allowed to see the folder tree, but WordPress still does not let that role upload media.
• A Subscriber can see folders only when Plathix access is above None. The role still cannot upload files or edit posts.
• Changing Plathix access does not grant edit_post, upload_files, or other WordPress capabilities.

This makes access predictable: Plathix can limit what a role does inside the folder system, but it does not silently expand the role itself.

Default Plathix Pro levels

With an active Plathix Pro license, the standard WordPress roles start with these levels:

Author starts on View even though WordPress gives the role upload_files. The table below shows what that combination means in practice.

WooCommerce Customer

WooCommerce Customer is not a standard WordPress role. When WooCommerce adds it, Plathix treats it like another role in Access settings. It has no special Plathix capability override.

Role-by-role reference

Choose a role to see exactly what Full, Upload, View, and None allow. These tables show the full result of Plathix access together with the standard WordPress capabilities for each role.

Audit Log has one extra WordPress permission check. It requires Full access in Plathix and the WordPress manage_options capability. Standard Administrators have it. Standard Editors, Authors, Contributors, Subscribers, and WooCommerce Customers do not.

What Access does not control by itself

Normal WordPress uploads

Add Media comes from the WordPress upload_files capability. Plathix Access does not grant or remove that capability. This is why an Author can still use Add Media when Plathix is set to None, while a Contributor cannot upload media even when Plathix is set to Full.

SVG uploads

SVG has another permission layer. SVG support must be enabled, the role must have normal WordPress upload rights, and the role must be allowed in the SVG settings. Administrator and Editor are allowed by default. Author is not.

Folders in posts, pages, and custom post types

A Plathix level above None can show the folder panel in the editor. Saving the selected folder still follows the WordPress edit_post permission for that post.

FAQ

See Plathix PRO