Reference

Account and access

Credits and billing, roles, per-system permissions, and where your data lives.

Credits and billing

Credits pay for Winston's work: 100 credits = $1 on Starter, $0.83 on Pro. Cost varies with the job (request length, data volume, date range), so run a report once and read Settings → Billing → Usage before scheduling it. Usage is tracked per workspace, not per person. Plans: Starter $300/mo = 30,000 credits; Pro $1,000/mo = 120,000. Plans are billed from a linked bank account, so there are no card fees; link one under Settings → Billing → Payment method before you choose a plan. Plan credits reset monthly and purchased credits roll over, but the terms can change, so read Settings → Billing for what applies to your workspace. Auto-recharge is off by default and needs an active plan. At zero, Winston replies with an out-of-credits message and does no work; nothing is charged without a payment method and a chosen plan.

First data query+150

Attach billing+600

First approval+150

First web page+150

First schedule+150

Each teammate (up to five)+300

The Earn credits page (click Credits earned, bottom left) lists the setup steps that earn free credits, and you can spend earned credits without an active plan. Expiry terms can change, so check Settings → Billing before you count on a balance being there later.

The Earn credits page, showing the credit balance and the steps that earn more — Earn credits: free credits for setup steps.

Workspaces and roles

A workspace is one business: its connections, its data, its team, its Library. Three roles, no user cap:

Owner

Set up the workspace. Everything an Admin can do, plus ownership of billing. Ask support to transfer ownership.

Admin

Everything a Team Member can do, plus billing, settings, and connections. Can remove members in Settings; if the option is not available, or to delete the whole workspace, email support@winston.team.

Team Member

Chat, run work, review and Approve, browse the Library. Can invite other team members.

Any member can Approve; Winston assumes everyone you invite is back office. Adding teammates earns credits too, up to five (see the Earn credits page, bottom left); invites go out by email as one-time magic links. The Library and Work Audits are team-wide; chat sessions are visible to you and to Admins or Owners with access, and to anyone you share a session link with.

Permissions and data

The rule, from the Winston team: Winston can do in a connected system whatever that connection's permissions allow. The question is never "can Winston write?" but "what access did we grant when we connected it?" Before any write: "Show me exactly what you will change before you change it."

Reads freely

Your POS sales, inventory, products, customers; Metrc package data; whatever Google Workspace grants.

Parks in Work Audits

Anything a workflow wants to publish, create, send, or record: web page, file, email, Slack post, invoice.

Skips Work Audits

A schedule with delivery on, and a typed request that writes to a write-enabled system. Ask to force the gate.

Per system: Treez was read-only when this guide was checked, with no API writes; confirm what your connection allows in Settings → Connections. Metrc follows the per-license user key you supply, so a read-only Metrc user's key keeps Winston read-only. Google Workspace, Slack, and the rest grant whatever their connection grants. The unlink icon on any Connections card is the off switch: Disconnect removes Winston's access immediately. Undo: ask Winston to unpublish a web page and it will; treat sent emails and Slack posts as final.

Your data and security

Where does my data live?

Winston runs in a contained instance that only your team works inside. You own your data, and it is never shared with the Treez platform; the terms commit to that contractually.

Is AI trained on my data?

Frontier models are not trained on your data. Winston improves through your team's feedback and de-identified, aggregated patterns, never your raw business data.

What about changes to my systems?

Consequential work waits for a person to Approve, and every write is logged: what changed, when, and who approved it.

Hosting, certifications, retention

For details on hosting, security certifications, and data retention, contact support@winston.team or see winston.team/faq.

Team rules worth putting in your SOP: decide who clicks Approve; supply Metrc a read-only key unless a workflow needs writes; keep loss-prevention prompts to managers; spot-check one line before approving anything outbound; give schedules with delivery on owner sign-off.