Description of user permissions

Overview

User permissions control which areas of the Yari Flow Dashboard a team member can access and which actions they can perform.

Permissions are assigned through roles. When creating or editing a role, select only the access required for that team’s responsibilities.

This allows you to create different permission levels for teams such as:

· Customer support

· Ecommerce

· Operations

· Finance

· Technical teams

· Administrators

Permission types

Most areas use one or more of the following permissions:

Permission

What it allows

Read

View the relevant page, records or settings

Create

Add new records or configurations

Update

Edit existing records or configurations

Delete

Remove existing records or configurations

Some areas include additional permissions:

· Login: Access a customer’s My Account experience from their customer record

· Edit Price: Change the price applied to an individual subscription

The number beside each area shows how many permissions are selected.

For example, Automations (1/4) means that one of the four available permissions has been enabled.

Available permission areas

Analytics

Controls access to subscription analytics, reports and performance information.

Automations

Controls access to creating and managing automated workflows.

Give editing access only to users responsible for maintaining automations, as changes may affect customer communications or subscription activity.

Billing

Controls access to the fees and account activity associated with the merchant’s Yari Flow account.

Cancellation Flow

Controls access to the standard Cancellation Flow and Cancellation AI Flow.

Editing access allows users to manage cancellation reasons, conditions, solutions and retention actions.

Collections

Controls access to collection information available within Yari Flow.

Customers

Controls access to customer records and their associated subscriptions.

The additional Login permission allows authorised users to access the customer’s My Account experience.

Delivery Profiles

Controls access to the delivery profiles used by subscription products and orders.

Changes may affect how subscription deliveries are scheduled or processed.

Integrations

Controls access to integrations connected to Yari Flow.

Editing access should normally be limited to administrators or technical users, as changes may affect data sharing and connected workflows.

Invoices

Controls access to the monthly invoices issued for the merchant’s Yari Flow account.

Orders

Controls access to subscription order records and available order-management actions.

Pricing Plans

Controls access to Pricing Plan configuration.

How they differ from Selling Plans and Selling Plan Groups.

Products

Controls access to product and variant information available in Yari Flow.

Product catalogue changes may still need to be completed in Shopify.

Roles

Controls access to creating and managing permission roles.

This is sensitive administrative access and should only be given to users responsible for account security and permissions.

Selling Plan Groups

Controls access to Selling Plan Groups, which organise the subscription options associated with products.

Changes may affect which subscription choices are available to customers.

Selling Plans

Controls access to the individual Selling Plans contained within Selling Plan Groups.

These plans may define billing frequency, delivery frequency and subscription discounts.

Shop Job Schedules

Controls access to scheduled background processes associated with the store.

This is a technical area and should normally be restricted to administrators or technical users.

Shop Settings

Controls access to account-wide Yari Flow settings.

Changes may affect subscription rules, billing behaviour, customer messages, payment retries and out-of-stock handling.

Restrict editing access to users who understand the effect of store-wide changes.

Subscriptions

Controls access to subscription records and management actions.

The separate Edit Price permission allows users to change subscription pricing. This should only be given to team members authorised to make commercial or pricing changes.

User Roles

Controls how roles are assigned to Yari Flow users.

Users

Controls access to team-member records and user management.

Editing access may allow users to change another user’s assigned role or account details.

Voucher Batches

Controls access to groups of vouchers created or managed together.

Changes may affect multiple vouchers, so editing access should only be given to users responsible for promotions or retention offers.

Vouchers

Controls access to individual vouchers and their configuration.

Recommended permission practices

When creating roles:

· Give users only the access required for their responsibilities

· Use Read access when editing is not necessary

· Restrict Billing and Invoices to authorised finance or administrative users

· Restrict Roles, User Roles and Users to administrators

· Restrict Integrations, Shop Settings and Shop Job Schedules to experienced users

· Give Edit Price access only to users authorised to change subscription pricing

· Review roles whenever a team member’s responsibilities change

· Remove access promptly when a user no longer requires it

Frequently asked questions

Are all permissions required?

No. Every permission is optional.

Select only the permissions required for the role you are creating.

Can different roles have different access to the same area?

Yes. For example, one role could only view Automations, while another could create, update and delete them.

What does the number beside a permission area mean?

It shows how many of the available permissions are selected.

For example:

· Subscriptions (1/3) means one of three permissions is selected

· Roles (0/4) means no permissions are selected

Should every user have administrative access?

No. Administrative access should only be given to users who need to manage account-wide settings, integrations, users or permissions.

What happens when a user does not have Read access?

The user should not be able to open or view that area of the Yari Flow Dashboard.

‍