Site capabilities and project roles

Pomatio adds two groups of checkboxes to user profiles. They extend supported POM administration workflows and record project responsibilities without replacing the user's WordPress role.

Audience and permissions

This guide is for administrators managing user profiles. The Site settings capabilities section is visible only to a network super administrator or a user who actually has the Administrator role and can edit the target profile. Temporary access to another administration screen does not make someone an administrator for this purpose.

The values use network-level user metadata. In multisite, changing them from one site changes the same user's POM flags across the network.

Available checkboxes

Enabled capabilities

These flags participate in Pomatio's administration allowlist. They do not turn a subscriber into an editor and do not grant unrestricted network administration.

Project roles

A user can have any combination of:

• Sales representative
• Project manager
• Designer
• SEO Expert
• Developer
• Copywriter

Project roles primarily describe responsibility so project workflows can find or label the appropriate people. Designer also participates in the supported design-screen policy and enables theme-design access for an otherwise eligible user. The other project roles do not grant a matching WordPress role.

Assign or remove values

1. Go to Users and open the intended user's profile.
2. Find Site settings capabilities.
3. Select only the applicable Enabled capabilities and project roles.
4. Save the user profile.
5. Reload the profile and confirm the selected values remain.

Changes are validated against the supported values, stored on the user's profile and available on the next request. Review access-sensitive changes with the user rather than assuming an open browser session has refreshed its state.

How these differ from WordPress roles

Selecting Advanced does not make a subscriber an editor. Selecting Developer does not grant access to code, plugins or network administration. Use WordPress roles for WordPress permissions.

The separate POM Framework site-settings area uses edit_pages as its minimum capability. Editors and Shop managers can open and save Pomatio's General settings screen without additional profile flags. This screen-specific access does not change their stored WordPress role or grant access to unrelated settings screens.

Network-wide access boundaries

Pomatio disables the legacy WordPress Customizer for every user, including network super administrators. Theme changes must use the supported theme settings workflow. A Designer, Advanced or Reseller flag does not restore the Customizer, and obsolete Customizer, font-library and theme-check actions are removed from the Appearance menu.

Users with the Editor or Shop manager WordPress role may edit the page currently selected as the site's Privacy Policy when they already satisfy WordPress's normal page-editing requirements. This exception does not let them open Settings → Privacy, select or create the Privacy Policy page, or administer network privacy settings.

An Editor or Shop manager with Advanced enabled can select Generate assets in the administration bar. Pomatio opens Settings → POM Theme → Tools → Compile assets in a new browser tab and starts the combined CSS and JavaScript build. The user can also run the CSS-only or JavaScript-only choices from that screen. This permission applies only to the compiler: it does not expose the adjacent settings import/export tool or grant access to unrelated POM Theme options.

Managed user workflows

An Editor can see users assigned to the Editor, Shop manager, Author, Contributor, Customer, Subscriber and Administrator (E-commerce orders) roles in the site's Users list. Visibility does not imply permission to change every listed user: Editors may assign, edit or promote only Customers and Subscribers, plus retain access to their own profile. They do not receive network user administration.

Editors and Shop managers who open WordPress's standard Users → Add New User screen are redirected to Users → Add new customer, where the available role choices remain restricted. WooCommerce additionally lets Shop managers work with Editor and Subscriber accounts alongside the roles WooCommerce already permits.

Add a customer

The Add new customer screen is available to Administrators, Editors and Shop managers who can access site user administration. Editors can assign only the Customer or Subscriber role. Other supported extensions may add a role through the pom_new_customer_roles filter, but the role must exist on the current site and Editor restrictions still apply.

1. Go to Users → Add new customer.
2. Enter a valid Email. Entering Username is optional; Pomatio generates one from the email address when it is left empty.
3. Select one of the available roles.
4. If WooCommerce is active, optionally complete the billing name, company, NIF, address, country, city and phone fields.
5. Administrators and network super administrators can leave Email credentials to me selected to receive the generated username, email and password at their own account email address. Editors and Shop managers cannot request this email.
6. Select Add new customer.

If the email already belongs to a network user who is not a member of the current site, Pomatio adds that user to the site with the selected role and saves the supplied billing details. If the user is already available, the result links to the existing profile. A newly created user receives a generated password; credentials are sent only to the creating administrator when the checkbox is available and selected, not directly to the customer.

After submission, verify the success or existing-user notice, follow its profile link and confirm the site role and any billing details. If credential delivery fails, the customer remains created and the screen displays the mail error so the administrator can arrange credentials separately.

Import customers from CSV

Administrators on WooCommerce sites can select Import customers from the Add new customer screen. The importer uses WordPress's existing import permission and processes the file on the current site.

1. Prepare a CSV with one header row and one customer per following row. Every row must contain the same number of columns as the header.
2. Open Users → Add new customer and select Import customers.
3. Choose the CSV and select Upload file.
4. For each CSV column, select Do not import, Username, Email, First Name, Last Name, Nickname, Company, NIF, Address Line 1, Address Line 2, Postcode, Country, City, Phone or Role.
5. Map exactly one column to Email. A valid email is required for every imported row. If Username is not mapped, WooCommerce generates it from the email. If Role is not mapped, the Customer role is used.
6. Optionally select Send new customer email to trigger WooCommerce's new-account email after each successful row.
7. Select Import and review every displayed result.

For a new email, the importer creates a network user on the current site and writes the mapped profile and billing values. For an existing network email, it adds that user to the current site with the mapped or default role, then updates the mapped values. A malformed email or a row whose column count differs from the header is skipped and reported without stopping the remaining rows.

After the import, open a sample of new and existing profiles and verify their current-site role, name and billing data. When welcome emails are enabled, also confirm WooCommerce's mail transport and template configuration before processing a production list.

On sites using WooCommerce, Administrator (E-commerce orders) provides the historic order-specific capabilities without network administration or general WooCommerce management. Its dashboard hides Posts, Comments, Tools and the legacy WPBakery welcome page. Assign this role only to people responsible for order operations.

POM AI editorial tools

With POM AI active and the corresponding tools enabled, Editors and Shop managers can use its writing, translation, product-description and image tools. Translation still requires Polylang, and catalog tools require WooCommerce.

These tools receive the content, taxonomy and media permissions they need for the current site. The image tools also allow supported site-wide reference updates while retaining both attachments. This access does not grant MCP user administration, network administration, or new JavaScript creation.

Open translation at Languages → AI translate and image tools under Media. Catalog description tools appear under Products for users who already have catalog access; otherwise the dedicated AI entries appear under Tools. AI tool access does not by itself grant general Products administration.

WordPress accounts must still be authorized separately when connecting an MCP client, and that connection remains subject to its scopes and enabled write groups. An Editor or Shop manager cannot inherit the main site's Unlimited multisite delegation grant.

PDF design access

When Fenómenus is active, users with the Editor or Shop manager role can manage the complete PDF designs workflow. They can list all saved designs, create and duplicate designs, edit designs created by another user, save custom presets, preview dynamic menu data, publish or permanently delete designs, and generate or download the resulting PDF files.

This access is provided by a dedicated PDF capability. It does not grant access to unrelated WordPress settings, plugins, themes, or ordinary content owned by another user.

Verify safely

1. Confirm the user's WordPress role still matches their real responsibilities.
2. Sign in as, or ask, the affected user to check only the workflow they are meant to use.
3. Verify that unrelated administration screens did not become available.
4. Record who approved any access flag and review it when responsibilities change.

Troubleshooting

• The section is missing: confirm that your account has the actual Administrator role or is a network super administrator. Access temporarily extended for another screen is not sufficient.
• A checkbox does not grant page editing: that is expected; assign an appropriate WordPress role separately.
• A project workflow lists the wrong person: reload the profile, verify the selected project role and confirm you edited the correct user.
• A network tool is still unavailable: these checkboxes do not grant network super-administrator access.

Access hygiene

Grant the minimum WordPress role and POM flags required, review them when a project changes, and remove them when a person no longer needs them. Never use a descriptive project role as evidence that a user has a particular technical permission.