Users & Roles
ThreadCloud uses three roles. Pick the lowest one that lets a person do their job.
| Role | What they can do |
|---|---|
| Owner | Everything. Exactly one Owner per store — usually the founder or buying lead. |
| Buyer | All workflows: Build Order, Enrich, Push, Receiving, Reorder, MTM, Trading, Financials. Can read settings but not change AI prompts or theme. |
| Viewer | Read-only. Useful for accountants, supplier reps, anyone who needs visibility but shouldn’t edit. |
Adding a user
- Settings → Users & Roles
- Click Invite User
- Enter email + role
- Click Send Invite — they receive an email with a sign-in link
They sign in with their Shopify account. The role gets applied on first login.
Changing a user’s role
- Settings → Users & Roles → find the user in the table
- Click the role dropdown next to their name
- Pick the new role
- Confirms — takes effect on their next page load
Removing a user
- Settings → Users & Roles → find the user
- Click Revoke Access
- Confirm — their next page load will show a “no access” page
This doesn’t delete their Shopify account, just their access to ThreadCloud.
Who gets what role
| Person | Role | Why |
|---|---|---|
| Founder / buying lead | Owner | Full control |
| Sales associate doing receiving | Buyer | Needs to operate Receiving + Labels |
| Accountant | Viewer | Reads Financials, doesn’t edit |
| Manager doing reorders | Buyer | Needs to operate Reorder + Trading |
| Supplier rep checking ack status | Viewer | Reads their own orders, doesn’t edit |
What only Owner can do
These are gated to the Owner only:
- Edit AI prompts (Settings → AI & Models)
- Change the metafield schema
- Use dev tools (
/app/settings/dev) - Set up new brands with MTM recipes
- Adjust theme configuration
- Reset / wipe data
Buyers and Viewers will see these pages but get a “permission denied” message if they try to act.
Common mistakes
Giving Owner to multiple people
There should be exactly one Owner per store. Multiple Owners create coordination problems on settings changes. Use Buyer for anyone else who needs write access.Forgetting to revoke when staff leave
ThreadCloud access persists until you explicitly revoke. Add “Revoke ThreadCloud access” to your offboarding checklist.Next steps
- Brands & Suppliers — assign brands a buyer is responsible for
- Runbook — what Buyers can self-serve vs. need Owner for