Before you start
- List every physical business location and device.
- Decide which packages are shared and which are branch-specific.
- Decide what each staff member needs to do.
Procedure
Follow these steps in order
Create one branch per operating location
Use clear names and confirm country, currency, and network identity. Do not use branches as temporary folders.
Assign each device once
A router or AP belongs to one active branch. Move it when the physical location changes instead of creating a duplicate record.
Choose package scope
Assign a package to specific branches when offers differ by location, or make it available to all branches when the same policy is intentionally shared.
Confirm before generating
The voucher screen must show the selected branch, device, and package. Similar device names are not enough; review the customer and branch context.
Invite staff by responsibility
Owners control the workspace. Managers operate assigned locations, technicians handle devices, and sellers handle voucher sales. Grant only the permissions needed.
Test role access
Ask the staff member to accept the invitation and verify their dashboard and allowed actions. Pending invitations reserve a subscription user seat.
Verify success
- Dashboard branch totals match active locations.
- Each active device appears once.
- Branch-specific packages appear only where intended.
- Staff cannot access actions outside their assigned role and scope.
Troubleshooting
A package is missing for a router
Open the package and assign it to the router's current branch, or intentionally enable all branches. Refresh after saving.
A manager cannot use an assigned action
Confirm the invitation was accepted, the membership is enabled, the role has the required permission, and any site scope includes the target branch.
Was this guide helpful?
Your response helps the system owner prioritize documentation updates.