ShopView tool
The canonical version always lives at https://tavina.ai/docs/friendly/tools/shopview
ShopView tool
The ShopView tool connects Tavina to your ShopView shop-management account. Your agent can read shop information โ customers, assets and units, work orders, parts and inventory, purchasing, billing, and team records โ directly in chat, and you get a dedicated ShopView workspace inside the Tavina app with module panels for browsing and working with that data.
The ShopView tool is currently rolling out gradually and may not be enabled on every account yet.
Availability and how to get it
ShopView is an On Request tool. It is not part of the default toolbar, and it is not available to every account: it is enabled per subscriber when the shop integration is set up for you. If you need ShopView, ask for it through the in-app Help support route and the team will enable it and connect your shop.
When enabled, the tool appears in your toolbar like any other tool. There is nothing extra to install on your side, and nothing changes for your other tools.
Connecting your shop
You connect ShopView with an API key created in your ShopView account:
- In ShopView, open Administration > Open API > API Keys and create an API key.
- In the Tavina app, open the ShopView tool, choose the gear icon, and open the Connection tab.
- Paste your API key and connect.
Your key is stored securely for your own account only. Tavina never needs your ShopView password.
Connection settings (gear > Connection)
The Connection tab holds everything about the link between your Tavina account and your shop:
- ShopView API key – paste the key here. It is stored write-only: after connecting, only a last-few-characters hint is ever shown again, never the full key.
- Test connection – checks the key against the ShopView API with rate-limit headroom, so testing never eats into your normal request budget.
- Default location – pick which shop location the tool treats as home for location-scoped views.
- Available modules (scope readout) – shows exactly what your key can reach, so a limited-scope key (like a staff key) is never a mystery.
- Last-sync timestamp – when your local shop data cache was last refreshed. Background syncing starts automatically once a key is connected โ you never need to leave the panel open to keep data fresh (tavina/tavina#2880).
- Disconnect ShopView – removes the connection and your key.
- Local cache > Purge local cache – wipes the cached copy of your shop data. It is confirmation-gated, and shop data is re-fetched from ShopView on the next sync; purging never deletes anything in ShopView itself.
Request limits and errors
Tavina talks to ShopView under a per-key rate limit (300 requests per window) with a 20% reserve kept for your interactive use, backs off politely when ShopView signals throttling (HTTP 429), and maps ShopView error responses into plain-language messages instead of raw codes. Retryable writes are idempotent, so a retried add or update does not create duplicates.
Sections & agent settings (gear > Sections & agent)
The Sections & agent tab controls what appears in your workspace and what your agent may do in each module:
- Sections – the eight module panels: Shop Floor, Work Orders, Customers & Fleet, Billing & AR, Parts & Inventory, Purchasing, Team & Time, and Shop Setup. Toggle visibility per module.
- Default agent permission – the fallback permission tier your agent uses in modules without their own setting: off, read, draft, or write (default read). A per-module tier can override it, or sit on inherit to follow the default.
- Modules governed by a shop role show Managed by a shop role. – the role decides the tier, and the control stays locked.
- Recent permission changes – the latest tier changes with who made them; older entries stay available server-side.
- Reset ShopView settings – restores section visibility and permission tiers to defaults (your connection and key are untouched).
Browsing the panels
Each module is a read-oriented panel over your live shop data:
- Shop Floor – open work orders grouped by status and type, vehicles on site, assignments by technician and bay, today’s time entries, and unpaid invoices, with as-of stamps.
- Work Orders – a filterable list with a detail drawer that loads labor lines, parts, tasks, time entries, invoices, and approvals one child view at a time.
- Customers & Fleet – contacts, fleet lists, and per-asset spec sheets (VIN, plate, unit, mileage, engine hours), plus a live accounts-receivable card per customer.
- Billing & AR – invoice list with the same filters ShopView’s own server offers, cache-computed AR aging buckets with customer rollup, payments, credit memos with remaining balances and applications, and deposits. Vendor invoices carry their own balance fields โ total balance and amount already paid โ so outstanding vendor amounts are read directly rather than derived (tavina/tavina#2880).
- Parts & Inventory – the catalogue, per-location stock with min/max/quantity/bin/cost/sell, a below-minimum reorder list sorted worst-shortfall first, and per-part cross-location views with cycle-count dates.
- Purchasing – vendor list with a lazy-loaded drawer for contacts and parts, vendor invoices with server-aligned filters, and embedded line-item detail.
- Team & Time – staff records (salaries shown only where your key permits), time entries with derived hours and per-technician detail, per-tech open assignments, locations, departments, and a utilization view that reconciles one-to-one with raw time entries.
- Shop Setup – the reference data behind your shop, collapsed by default.
Panels read from a per-subscriber local cache that syncs on a tiered cadence – every few minutes while the panel is open, every 15-30 minutes when idle, and daily for reference data – with search across customers, assets (VIN/plate/unit), work orders (number/PO), parts, and vendors. Deletions in ShopView are reconciled by re-walking data rather than destructive deletes, and every view carries an as of stamp so you always know how fresh it is.
Each cached view is also judged against its own freshness rule: data that is within roughly twice its intended refresh interval (plus a grace window) counts as fresh, older data counts as stale, and data that has never synced counts as unknown โ never as current. The Shop Floor and Billing & AR headers show this status as a small chip, and when your agent reads stale or unknown data in chat, the answer carries a warning saying so (tavina/tavina#2880).
Delegated roles for staff
If you run a shop with staff, you can give team members scoped access to ShopView through their own Tavina accounts. Instead of sharing your full admin access, you assign a role โ for example a Parts Manager โ that defines exactly which parts of the shop each person can see.
A role controls:
- Module visibility โ which ShopView modules appear at all. A role without billing sees no Billing & AR module anywhere: not in the app, not in their agent’s tools.
- Read vs. read-write โ whether they can only view a module’s data or also make changes in it.
- Sensitive-field protection โ confidential fields such as salaries, tax IDs, account balances, and credit terms are simply not included for restricted roles. Aggregated figures derived from them, like aging summaries, are left out too. Restricted staff never see a placeholder or a blanked-out value; the information is just not there.
Role-governed modules appear as managed in the staff member’s own settings โ locked to the access level you chose. Attempts to widen their own access are refused by the server and recorded for the account owner’s review.
How to set up a staff member
- Follow each other in Tavina Community. A mutual follow between the shop owner’s account and the staff member’s account is required before a role can be assigned.
- Create a reduced-scope API key in ShopView. In Administration > Open API > API Keys, create a second key limited to only the resources that role needs (for example, parts and purchasing โ no invoices). Each key has its own usage budget, so staff activity never competes with yours.
- Assign the role. From your Sharing menu, issue the role grant to the staff member โ pick the role (e.g. Parts Manager) and whether their modules are read-only or read-write. Revoking the grant takes effect immediately.
- The staff member connects their own key. On their own account, they open the ShopView Connection tab and paste their key โ exactly like connecting in step one.
You never need the staff member’s credentials, and they never need yours. Each person’s Tavina talks to ShopView directly with their own key.
What your agent can do
With ShopView connected, you can ask your agent things like:
- “Look up the service history for this serial number.”
- “What’s our current stock on this part, and is any on order?”
- “Add this new part to our inventory.”
- “Update the contact details for a customer.”
- “Summarize this month’s purchasing.”
Your agent’s access automatically matches the connected key’s permissions, and for staff accounts it matches their assigned role โ including the sensitive-field protection described above.
Notes
- The shop owner account keeps full fidelity: connected as an admin, all data and cached history remain complete.
- All changes made through the tool are recorded in a per-account activity log.
- If you change or revoke a role, the staff member’s access updates the next time they use the tool โ no redeployment or reinstall needed.