Team & permissions
Most DZBuild stores grow beyond a single owner. Team management lets you invite collaborators with scoped permissions, so a call-confirm operator doesn't accidentally change shipping rates and a finance reviewer doesn't ship orders.
Where this lives
Open /dashboard/team. You'll see:
- The list of current members (name, email, role, last sign-in)
- An Invite member button
- For each member, a role dropdown and a Remove action
Roles
| Role | Capabilities |
|---|---|
| Owner | Everything — products, orders, customers, billing, team, settings, ownership transfer. Only one Owner per account. |
| Admin | Everything except billing and ownership transfer |
| Manager | Products + orders + customers; cannot change settings, shipping rates, or payment methods |
| Operator | Orders only — call-confirm, mark shipped, mark delivered. The right role for call-confirm staff. |
| Read-only | Read all dashboards and reports; cannot change anything. The right role for finance reviewers. |
The Owner is the account creator. Transferring ownership requires a confirmation email round-trip.
Inviting a member
- Dashboard → Team → Invite member
- Enter the new member's email address
- Pick a role
- (Multi-store accounts) Pick which stores this member can access — and the per-store role
- Send invite
The member receives an email with a magic link. Once they click and accept, they sign in with their own credentials and see the stores you granted them in their dashboard.
Per-store roles (multi-store)
A team member you invite can be granted different roles on different stores. Common patterns:
- One operator across all stores — same
Operatorrole on every store, so they can call-confirm anywhere. - Brand-specific manager —
Manageron Brand A, no access to Brand B. - Finance auditor —
Read-onlyon every store.
See Multi-store for the per-store dynamic.
Removing a member
/dashboard/team → click the member row → Remove. They lose access immediately. Their action history (orders processed, products edited) stays in the audit log.
Audit log
Every team-member action is logged: who, what, when. Filter by member, action type, or date range. Useful for:
- Compliance reviews
- Catching accidental changes ("who set free shipping yesterday?")
- Onboarding reviews ("did the new operator confirm the orders correctly?")
The audit log is read-only — you can't edit historical entries.
Best practices
- Operator for call-confirm staff. It keeps them out of pricing and discounts and is the safest role for high-turnover ops teams.
- Manager for trusted ops leads who run product launches.
- Admin rarely. Anyone with Admin can change shipping rates or payment methods — only assign it to people you fully trust.
- Read-only for finance, accountants, agency reviewers — they can read everything but cannot break anything.
- Rotate access when team members leave. Remove their account immediately.
- Enable 2FA for all members on Unlimited plans, especially Owner and Admins.
Team-member limits per plan
The number of additional team members you can add depends on your plan:
| Plan | Team members (in addition to the Owner) |
|---|---|
| Free | 0 — owner only |
| Pro | 1 |
| Unlimited | 3 |
| Enterprise | 10 |
The Owner does not count toward the team-member limit.
If you hit the limit and need to add another teammate, upgrade your plan from /dashboard/subscribe. The ▶ How to renew button on that page launches a guided in-app tour for upgrading; video walkthroughs are also on the DZBuild YouTube channel.
Frequently asked
Q: Can a member belong to my team and another DZBuild merchant's team? A: Yes — email-based invites are independent across accounts. They sign in with one account and see all the stores they were invited to.
Q: How do I transfer ownership?
A: Owner → /dashboard/team → Transfer ownership → pick the new Owner. They confirm via email; once accepted, you become Admin on the account.
Q: How many members can I have? A: 0 on Free, 1 on Pro, 3 on Unlimited, 10 on Enterprise. See the table above. The cap applies in addition to the Owner.
Q: Can a member only see specific stores in multi-store accounts? A: Yes — per-store access is the default. Tick only the stores they need; they won't see the others in the store-picker.