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. The page shows two card sections — Active members and Pending invitations — plus an Invite member button.
An active-member card shows:
name and email
the member's role label
tags for the permissions they hold
the date they joined (not their last sign-in)
If you have team-management rights, each card also carries Edit permissions and Remove buttons.
A pending-invitation card shows the invited email address, the invitation's expiry date, and Resend / Cancel invitation.
Roles and permissions
A store has one owner — the account that created it — plus any number of team members. There are no Owner / Admin / Manager / Operator / Read-only roles: each member gets a free-text role label (for example "Orders manager") and a checkbox permission matrix.
When you invite someone you pick one of three presets, or Custom:
Preset | What it grants |
Orders Manager | Dashboard view; orders view / edit / export; customers view |
Products Manager | Dashboard view; products and categories view / create / edit |
Full Access | Everything except Team management and Domain management |
Custom | Tick individual permissions across Dashboard, Orders, Products, Categories, Customers, Shipping, Landing pages, Pixels, Customization, Settings, Domains, Add-ons, Team and Analytics |
⚠️ Warning — Full Access is not everything
The Full Access preset deliberately withholds two permissions: Team management and Domain management. Grant those only through the Custom preset, and only to people you fully trust — Team management lets a member invite and remove other members, and Domain management lets them link or remove your custom domain.
The store owner is the account that created the store and cannot be changed from the dashboard. If you need to move a store to a different account, contact support.
Permissions are enforced server-side
Permissions are not just a UI filter. Every dashboard route checks them: a member who lacks a permission is redirected back to /dashboard with an error, not merely shown a greyed-out link. Narrow permission sets are therefore genuinely safe to hand out.
Inviting a member
Dashboard → Team → Invite member
Enter the new member's email address
Pick a preset (or tick Custom permissions) — the role label comes from the preset you choose; Custom members are labelled
staffuntil you rename them via Edit permissionsSend invite
The invitee receives an email with a join link valid for 7 days. The email address must not already have a DZBuild account — if it does, the invite is refused. On the join page they create their account (first name, last name, phone, password); after that they sign in normally and land in your store's dashboard with the permissions you granted. Automated abuse checks protect the join page — if you believe a legitimate invitee was blocked, contact support.
Team membership is per store, and in practice a person can belong to only one store, because the invite is rejected for any email that already has a DZBuild account. To staff a second store you must invite a different, previously-unregistered email address.
Pending invitations
An invitation stays in the Pending invitations section until it is accepted, cancelled or expires:
Expiry — 7 days from the moment it was sent.
Resend — issues a fresh link.
Cancel invitation — withdraws it and frees the seat.
Pending invitations count against your plan's team-member limit, not just accepted members.
Removing a member
/dashboard/team → on the member's card, click Remove. They lose access immediately. Their actions remain in the internal activity log.
Activity log
Team actions are recorded in an internal activity log (who, what, when, IP address). There is currently no merchant-facing view or filter for it on /dashboard/team — if you need the history, ask support to pull it.
Best practices
Orders Manager for call-confirm staff. It keeps them out of pricing, discounts and settings, and is the safest preset for high-turnover ops teams.
Products Manager for catalogue work — product and category editing without touching orders or customers.
Full Access rarely. It covers shipping rates, payment settings and add-ons; only assign it to people you fully trust.
Custom whenever a preset is wider than the job. Tick only the modules the person needs.
Rotate access when team members leave. Remove them immediately.
Encourage two-factor authentication. Each person turns on TOTP 2FA (authenticator app plus backup codes) at
/dashboard/account→ Security. It is available on every plan, and each person enables it for their own account — the store owner cannot turn it on for them or require it.
Team-member limits per plan
The number of additional team members you can add depends on the store's plan:
Plan | Team members (in addition to the owner) |
Free | 0 — owner only |
Pro | 1 |
Unlimited | 3 |
Enterprise | 25–200 — 25 seats included; buy extra seats when you subscribe (+200 DZD/month each on a 1-month term, discounted on longer terms, up to 200 total) |
The owner does not count toward the limit. Pending invitations do.
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: In practice no. An invite is rejected if the email address already has a DZBuild account, so one person can staff only one store. Use a different, previously-unregistered address for each store.
Q: How do I transfer ownership? A: You can't from the dashboard — the owner is the account that created the store. Contact support if a store needs to move to a different account.
Q: How many members can I have? A: 0 on Free, 1 on Pro, 3 on Unlimited, and 25 to 200 on Enterprise depending on the seats you bought. See the table above. The cap applies in addition to the owner, and pending invitations consume a seat.
Q: Can a member see more than one of my stores? A: No. Team membership is per store — see Multi-store.