Skip to content Start from ₹499/year for your first year
Contact us
Nothing fits?
Build a custom pack

Pick modules, wire your own actions and automations. Live in two weeks.

  • Modules The screens your trade needs, switched on.
  • Your words Customers, orders and bills called what you call them.
  • Automations Reminders and follow-ups that run by themselves.
For example
Laundry & dry cleaning
Order Laundry ticket
Talk to us about yours Browse all 32 packs →
ERP packs
Classes & coaching Corporate training Schools & colleges Clinics Diagnostic lab / pathology Vet clinic & pet shop Contractors & site projects Event & wedding planner Gym & coaching Professional practice Property broker Rental & hire Repairs & field service Salon & spa Security & manpower agency Services & appointments Travel agency & tour operator Website Bakery & sweet shop Caterer & tiffin service E-commerce Hotel / guest house PG & student housing Restaurant Shops & counters Association & club Exporter Farmer producer organisation Housing society & RWA Manufacturing Trusts & non-profits Wholesale & building materials
Modules Pricing Desktop & mobile apps Documentation Blog Partners About
Contact us Sign in
Theme

Roles, permissions & approvals

Who can see money, who can discount, who signs off - set once and applied everywhere.

Administration Updated 14 September 2026 · 7 min read · Requires: Owner or Admin role

Permissions attach to a membership, not to a person. The same account can own one workspace and be a read-only member of another, and nothing leaks between them.

The roles every workspace starts with

Beside the owner, who can do everything, each workspace starts with six roles: Admin (everything), Manager (runs the business but does not change how the workspace is set up), Staff, Cashier, Accountant and Read only. They are the workspace's own copies - rename them, change what they allow or delete them under Workspace → Roles.

A role is a named set of permissions. New role builds your own from a list of permissions to tick; permissions for modules you have switched off are hidden until you switch them on. You cannot create a role with more access than you hold yourself, nor give a member more access than you hold when you change their roles. Only the owner can make someone an owner.

Every request is checked on the server against the permissions of the person making it. Take a permission away and it stops working on their next click, even if they are signed in at the time.

Approvals

An approval rule makes a document wait for a signature before it goes ahead. Rules are written under Workspace → Approvals, and they apply to six kinds of document: purchase orders, purchase requisitions, vendor bills, quotations, expenses and bill-of-materials versions - whichever of those your modules produce.

A rule names the document, a condition on one of its figures - a purchase order total above an amount, a quotation's discount or margin percentage - and who signs. Several rules on one document build a chain of levels: each is signed in turn, and a rejection at any level ends it and returns the document to its owner.

A level goes to anyone who can approve, the requester's reporting manager, anyone holding a particular role, or one named person. The person who raised a document never signs a level that names a signer. If nobody left can sign a level - the named approver has gone, say - someone who administers approvals can take it over, and the take-over is recorded as one.

Careful: An approval holds the document, not the person: a quotation waiting for sign-off cannot be sent, and a purchase order cannot go to the supplier, until the last level signs.

Was this page useful? You will be asked to log in first.
← Previous
Reading the run log
Next →
Locations & cost centres