Modules, licences and permissions
Two things decide what you see in the app: which modules your organisation licenses, and which permissions your roles grant you. Both have to say yes.
Modules
A module is a capability your organisation licenses and pays for separately. There are four today:
| Module | What it does | Guide |
|---|---|---|
| Receipts | Issue Receipts and print them on a thermal or paper printer. | Receipts |
| Customers | Keep a customer list and attach customers to documents. | Customers |
| Products | Maintain a product list with units and prices. | Products |
| Inventory | Track quantities against other records, with a full adjustment trail. | Inventory |
- There are no bundles. An organisation licenses exactly the modules it wants.
- No module requires another, but modules light each other up when both are present: Receipts gains a customer search with Customers and a product search with Products; Inventory tracks Products. Each module's How … connect page spells this out.
- Licensing is arranged with Greyield Labs, not switched on in the app. A newly licensed module appears for the owner at their next sign-in; other people see it once a role grants them its permissions.
The platform
Everything else is the platform, which every organisation has regardless of licences: signing in, the dashboard, Locations, Users, Roles, Organisation settings, Reporting, and the audit log. Their permissions are always available to roles.
Permissions and roles
A permission is one ability, named like Receipts.Create. A role is a named list of permissions. Your abilities are the union of your roles. Details in Roles; the full list is the Permissions reference.
- The owner has every permission automatically.
- A module's permissions can only be granted while the module is licensed, and only work while it is.
- Some permissions come in an "all" and a "mine" flavour: the whole organisation's records, or only the ones you created.
Why something is missing
| You do not see… | Because… |
|---|---|
| A module in the navigation or on the dashboard | The organisation does not license it, or you lack its View permission (for example Customers.View). |
| A button such as New Product or Delete | You lack the matching permission (Products.Create, Products.Delete). Each guide names it. |
| Reporting, or a particular report | You lack Reports.View, or the module's plain View permission (the "mine" flavour is not enough for reports). |
| A settings section | You hold none of the permissions for its pages. The Organisation page is owner-only. |
| A record another person made | Your permission is the "mine" flavour, which reaches only records you created. |
The server checks the same licence and permission on every request, so nothing hidden can be reached by other means. An unlicensed module answers "module not licensed", a missing permission "permission denied".
Reading the guides for a module you do not license
Every module is documented in full here. When a page describes a screen you do not have, it also says what happens without the module: for example, receipts take a typed customer name when Customers is not licensed. Use the How … connect pages to see what licensing a module would add.