Team and security
Give everyone the keys they needand see every door they open.
Add staff by email, give each a role made of exactly the permissions their work needs, and protect sign-in with a second code. Every change in the store is in the activity log, with who made it and when.
- Roles built from permissions
- Two-factor sign-in
- Sessions you can end
- An activity log of every change
Protection with numbers you can check
3
roles in every store to start from, and any of your own
10
wrong passwords in 15 minutes pause an address
365
days the activity log keeps by default
The difference
A shared password is not a team. It is a risk with several names.
Without Bazuva
With Bazuva
Everyone uses the owner's password, so anyone can do anything.
Each person has their own sign-in and a role that allows only what their job needs.
A price changes and nobody knows who changed it.
The activity log records each change with the person, the time and what it touched.
A phone you lost is still signed in to the admin.
Your sessions are listed with their browsers, and you end one, or all the others, at once.
Three shops mean three logins and three teams to manage.
One organization holds all your stores, with members who run them together.
Roles and permissions
A role is a list of things a person may do.
Every store starts with Owner, Manager and Staff. Make your own from the permissions the store actually uses, such as viewing orders, booking shipments, managing discounts or reading customers, and give it to anyone you add by email. A page a role cannot open says so instead of showing an error, and the same rule is checked again on the server for every request.
- Owner, Manager and Staff to start
- Roles of your own, permission by permission
- Only the permissions of what your store has switched on
- Checked on every page and every request
Signing in
A second code, and a lock that does not give anything away.
Turn on two-factor sign-in and every sign-in asks for a code from an authenticator app, with recovery codes for the day the phone is lost. Passwords known from breaches are refused. Ten wrong passwords in fifteen minutes pause the address, and the answer reads the same whether the address has an account or not, so nobody can find out who works for you.
- Codes from an authenticator app, each accepted once
- Recovery codes, each struck off when used
- Passwords from known breaches refused
- Never says whether an address has an account
Activity log
Who changed what, and when, for a whole year.
Every change the store records lands in the activity log: a price, a refund, a role, a discount paused, a domain added. Filter it by event, person, what it touched and dates, and keep it a year by default. When Bazuva's support signs in to help, a banner says so on every page, the visit ends within an hour, and the log names both people.
- Every change with the person and the time
- Filters by event, person, record and dates
- A log for each store and each organization
- Support visits shown and recorded under both names
Organizations
Run several stores from one account.
Your stores live in an organization. Its owners and admins reach every store in it; its members are given a role store by store. Open a second store for wholesale or a new brand in the same organization, or start a second organization for a separate business, each with its own members and its own activity log.
- Many stores under one organization
- Owners, admins and members
- Owners and admins reach every store
- A second organization for a separate business
How it works
Ten minutes to set up, and the store is safer every day after.
- 1
Invite your team by email
Each person gets their own sign-in.
- 2
Pick or build a role
Start from Manager or Staff, or tick the permissions one by one.
- 3
Turn on two-factor
Scan the code with an authenticator app and keep the recovery codes.
- 4
Check the log
See who changed what, and end any session you do not recognise.
Everything included
People, sign-in and a record of it all, in every store.
Team
- Staff added by email
- Owner, Manager and Staff to start
- Roles of your own, permission by permission
- Pages a role cannot open say so
Signing in
- Passwords of ten characters or more
- Passwords from known breaches refused
- A pause after ten wrong tries
- Reset links that work once
Two-factor
- Codes from an authenticator app
- Recovery codes, each used once
- Each code accepted only once
- Turned on from your own account
Sessions
- Every open session with its browser
- End one, or every other
- Sign-in history, wrong passwords included
- Every session ended after a password reset
Activity
- Every change with who and when
- Filters by event, person and dates
- A log per store and per organization
- Kept for a year by default
Organizations
- Many stores under one organization
- Owners, admins and members
- Only an owner can make another owner
- A second organization when you need one
Questions about team and security
Can my packing staff see my sales and payouts?
Only if their role has those permissions. A role allows exactly what you tick, and a page it does not allow shows a note instead of the figures.
What happens after too many wrong passwords?
Ten wrong passwords in fifteen minutes pause that address for fifteen minutes, wherever the tries came from. The message is the same for an address with an account and one without, so nobody learns who has one.
Is two-factor sign-in required?
Each person turns it on for their own account from the security page. From then on, signing in asks for a code from their authenticator app, and recovery codes cover a lost phone.
Can Bazuva's support see my store?
Only by signing in as you to help, and never quietly: a banner shows on every page while they are there, the visit ends within an hour, and the activity log records both names.
How long is the activity log kept?
A year by default, and never less than thirty days.
Your store is one sign-up away. Open it today.
Register, choose a design and add your first product. Cash on delivery, couriers and your buyers' language are ready when you are.
Your domain, your brand, no code to write.