Quick answer: In tnova's current access model, the authenticated Shopify store owner changes box settings and handles publishing, orders, reports, billing and in-app support. Other users have read-only access to setup, tutorials and configuration summaries. Assign staff the observation and preparation work, then give the owner a precise change request and a time to review it.
Shopify access and permissions inside an app are separate. Giving someone permission to open tnova in Shopify does not grant owner actions inside tnova. This guide helps an existing authorized team divide the work; public installation is not available yet. The feature catalog records current availability.
Separate opening the app from acting inside it
Shopify lets eligible administrators grant app access through user roles. Its store-permissions documentation explicitly distinguishes those permissions from permissions enforced by apps themselves.
tnova identifies its owner role from Shopify's authenticated online session. When owner status cannot be confirmed, access remains read-only. A Shopify role name, broad app access, or a job title such as “store manager” does not substitute for that confirmation.
Shopify's role guide explains how roles group permissions and how availability depends on the store's plan and organization. Use those settings for the Shopify tasks each person needs, then plan separately around tnova's current owner requirement. Granular staff editing roles inside tnova are not part of the current workflow.
Divide the work before a change is urgent
Use a responsibility sheet like this. “Staff preparation” means work someone can do with the information and Shopify permissions they actually have; it does not grant access to owner-only tnova pages.
| Task | Staff preparation | Owner action in tnova |
|---|---|---|
| Review assortment or wording | Identify exact variants and propose a change | Save the appropriate box settings |
| Change a selling box | Describe the affected offer and review window | Confirm pause, revise and republish after checks |
| Investigate a storefront issue | Record URL, theme version, selection and observed result | Review relevant app state and submit support if needed |
| Review sales or component records | State the question and reporting period | Open orders/reports and create the needed export |
| Review plan or support access | Explain the business need | Review billing or any temporary support grant |
The owner can share an appropriately limited working sheet outside the app when colleagues need operational instructions. That does not give staff live access to tnova's reports or order reconciliation. Shopify's own order, fulfillment and product permissions continue to govern work done in Shopify admin.
Write a change request that preserves the original offer
Consider this fictional handoff for a six-item snack box. It is a document template your team can use, not a built-in tnova approval form.
- Box: Weekend Snack Box; include its saved configuration reference if available.
- Current offer: Six item units, fixed price $30, maximum four of each eligible variant.
- Requested change: Replace the 40 g cocoa variant with the 40 g berry variant; keep count, price and repeat limit unchanged.
- Reason: The next planned assortment uses berry. Stock and eligibility still require owner review.
- Affected material: Product description, picker candidate list and the team's packing reference.
- Review window: Owner to confirm a pause before the promotional page changes.
- Acceptance check: New picker shows the intended variant; a valid two-plus-four selection and ordinary product purchase route behave as expected in the authorized test.
Use exact variant identifiers or product links alongside readable names. “Replace the cocoa item” is ambiguous when several sizes share a product title. The variant-identification guide supplies a fuller candidate sheet.
Keep the current state, requested state and observed result in separate fields. Do not mark a request completed because an email was sent or a draft was saved.
Reserve the owner's time for the actual decision
For a price, count, repeat-limit or candidate change, the owner should follow the pause-and-republish procedure. Confirm the pause, review the revised draft and current publishing checks, then record what actually became effective. Copying proposed wording into a staff document does not update the app's rules.
Arrange the handoff so the owner is available when a pause or publishing decision is needed. If the owner is away, staff can continue gathering observations and preparing copy within their access. They should not promise a configuration change or launch time that still depends on an owner action. Use individual accounts; sharing the owner's login is not a handoff process.
The current verified purchase baseline is Dawn 16.0.0, cart type Page, default market and currency, and a shared component fulfillment location. A person assigned to review the storefront should record that exact context. Scheduling, Sidekick and cart-drawer changes remain awaiting release; do not use them as substitutes for arranging the owner's review.
Diagnose read-only access without repeating writes
If a staff member sees Read-only access, first compare the intended task with the responsibility sheet. For an owner-only task, pass the request to the store owner rather than repeatedly submitting it.
If the actual owner unexpectedly sees read-only access, confirm the Shopify account and store, reopen tnova from that store's Shopify admin, and check whether the session has expired. Before repeating any interrupted save or publication, reload and inspect the saved state. A recovered session does not tell you whether a previous request completed.
If the problem remains, record the time, affected page and visible message. The support-report guide explains what to include and how temporary support permission differs from Shopify collaborator access. Do not include passwords or session cookies.
Finish with an operational handoff
After an approved change, give the team the confirmed box version or state, the effective assortment, the tested route and any unresolved checks. Update the working packing reference when the assortment changes, while preserving the original component details for orders already placed.
For a report request, share the needed rows and explain the period and metric; use the CSV-report guide to avoid counting repeated box amounts. Keep customer details out of a general setup sheet. A useful handoff lets each person complete their task with the information they need and makes the next owner action explicit.
Prepared with AI assistance and checked against tnova's implementation and the official sources linked in this guide. Examples are fictional.
See a gift box in action
Try the sample picker with fictional products. It creates no cart or order.
Try the box builder