Staff & Permissions
By default, every staff member who can open the app can do everything in it. When you need more control, such as letting your support team look up orders without being able to delete license keys, give each staff member their own permissions.
The app's permissions sit on top of Shopify's. A staff member first needs permission to use the app in Shopify, on their staff account in your Shopify admin. The app's permissions then decide what they can do inside it.
Authorize all Staff Members
Default: On
Every staff member has full access, and individual permissions are ignored.
Leave it on while you set up each staff member's permissions, then turn it off to start using them. Once it's off:
- each staff member can only do what their permissions allow, and
- only admins can manage staff.
Full access includes managing staff, so while this is on, any staff member can make someone an admin, themselves included. When you turn it off, check who is an admin under Staff Members. To take admin away from someone, turn this setting off first, then change their permissions. While it's on, they could make themselves an admin again.
Staff members
Staff members are added automatically the first time they open the app and visit a page such as Products or Orders. You can then set their permissions. To set someone up before they've visited, add them with their Shopify user ID, name and email.
- The store owner is always an admin, so you can't lock yourself out. If someone takes it away, it comes back the next time the owner visits the app.
- You can't remove your last admin. Make someone else an admin first.
- Removing a staff member takes away their access to the app straight away.
Presets
Presets are shortcuts for common roles. After choosing one, you can still adjust individual permissions.
| Preset | Can |
|---|---|
| Admin | Do everything, including managing staff. |
| Staff Member | View, create, edit and delete everything, but not export. |
| Customer Support | View everything, but not change anything. |
| Custom | Any other combination. |
Permissions
| Area | View | Create and Edit | Delete | Export |
|---|---|---|---|---|
| Orders | ✓ | ✓ | ✓ | |
| Products | ✓ | ✓ | ✓ | ✓ |
| Content | ✓ | ✓ | ✓ | ✓ |
| Licenses | ✓ | ✓ | ✓ | ✓ |
| Settings | ✓ | Edit |
Create and Edit includes the settings of what resource it covers. A staff member who can create and edit products can change a product's own settings, such as its button text or Auto Restock Inventory, without the Settings permission. The same goes for content, such as a piece of content's download limit, and for orders, such as an order's Order Reconciliation. Settings applied by a content import or a product import follow the same rule.
Settings: Edit is only needed for the store-wide settings on the Settings page.
Exporting content needs View for content as well as Export, because each file in the export comes with a download link. See Exporting Content.
Whoever started an import can always download its report. For other users, an import's report needs the Export permission for what was imported (content, products, or licenses), because it shows all data the was imported. The validation report, which the import window makes from the file you just chose, needs no permission of its own.
When a new kind of permission is added to the app, only admins get it automatically. Give it to other staff members yourself.
Default permissions
Default permissions are what a new staff member gets the first time they open the app. There are none to start with, so with Authorize all Staff Members off, new staff can't see or do anything beyond the dashboard and Analytics until you give them permissions. When someone doesn't have permission they see an Access Denied page, asking them to contact the store owner or an admin.
Who can see license keys
The app only shows a key to staff whose permissions cover the place it's shown. The general principal is that unassigned keys require license view permissions, and assigned keys (now that they are attached to an order) require order view permissions. The goal is to keep keys as secure as possible, while still providing the ability to view order status and history.
While Authorize all Staff Members is on, every staff member sees every key.
| Permission | Shows the keys |
|---|---|
| Licenses: View | Everywhere: the License Keys page, each key's page, and every alert. |
| Orders: View | On any order's page, including keys returned, restocked or deleted from it, since they're part of the order's history. Also in Order Updates alerts. |
| Orders: Create and Edit | On the order edit page, and in the results of a Manual Sync on the Orders page. |
| Orders: Export | In an orders export, and in an order import's report. |
| Products (any) | Never. Product pages, the Products table and the products export show how many keys each variant has, and only load that count. |
- The other license permissions don't include View. Turning on Create and Edit, Delete or Export for licenses doesn't turn on View, but two of them still show keys: an export lists every key, and Create and Edit can open a key's edit page. Give them only to staff you'd trust with your keys.
- Some key changes on an order need a license permission. On the order edit page, picking a key from stock needs Licenses: View, and deleting a key needs Licenses: Delete. Typing in a key, returning it, and restocking it only need Orders: Create and Edit. See Editing an Order.
- Key Uniqueness lists duplicate keys only with Licenses: View. See Key Uniqueness.
- Manual Sync on the License Keys page needs Licenses: Create and Edit. Without it, the button doesn't show.
- A key's page address holds the key's ID, never the key, so keys don't end up in your browser history or in links you share.
The order status page
Staff can open an order's status page from your Shopify admin, and see it the way the customer does. The app can't tell a staff member there from a customer who has the order's link, so:
- The app's permissions don't apply. Anyone who can open the order in your Shopify admin can reveal its keys and download its content there, whatever their permissions in the app. Require Customer Login stops this, since staff are never logged in as the customer, but every customer then has to log in too.
- What staff do there counts as the customer's activity. A reveal marks the key as seen, so Unused Key Restock never restocks it, and adds your reveal order tag. A download counts toward the customer's download limit and adds your download order tag. Each visit, reveal and download is in the order's Customer Activity, with the staff member's IP address and device, so check whose activity it is before using it as evidence in a dispute.