Data & support
Data & support14

Access, roles and team

How PROVEN decides who can use each store and which actions each team member can perform.

Updated 3 Oct 2026
On this page

Access to a store in Shopify Admin and access to PROVEN are two different things. A user can have Shopify access without automatically receiving every PROVEN function.

How access works

To use a PROVEN function, the user must be recognized for the current store and have the required PROVEN permissions. If either condition is missing, that function remains unavailable.

First app open

A team member first opens the correct store with their own Shopify account, then opens PROVEN. The first attempt may say that access has not been granted yet, but it allows PROVEN to recognize the user for that store.

After that, the store owner or an authorized administrator can configure the required access.

PROVEN roles

The interface uses three base roles:

  • Shopify Owner - the recognized owner for the current store;
  • Admin - can receive administrative rights within the access they have been granted;
  • Member - receives only the permissions needed for their work.

The role sets the general limit, while permissions decide which concrete actions are available.

Separate permissions by area

Access can be split across:

  • catalog and store settings;
  • synchronization and checks;
  • problems and fixing;
  • audit;
  • team access administration;
  • billing, where the role and configuration allow it.

For example, a user can see a problem without receiving the right to approve or publish a fix.

Preparing access for a user

An authorized administrator can prepare access using the Shopify user identifier. Access becomes effective only after that person opens PROVEN in a valid Shopify session for the same store.

Store separation

Access is configured separately for each store. A role or permission from another store does not automatically grant access to the current store.

This separation matters for people, agencies, and teams working with multiple merchants.

What a user sees without the required permission

PROVEN clearly shows when an area is unavailable. Settings and Audit, for example, can be blocked independently, while a problem may remain visible without also granting the right to fix it.

The agency model is implemented with per-store separation, access that can be limited to selected stores, and operator-assisted onboarding. Merchants can see the active agency relationship, while assignment changes remain administrative. See Agencies and multi-store administration. For general access and sensitive-change principles, see Security & trust. For change history, see Audit and traceability.