Organization

Companies, sites and teams, the modules people open, and the place every action happens in.

How Netzo is organized

People open a module for a scope. The module shows tables, and each table belongs to a domain and has fields:

Domain: PartiesDomain: PartiesDomain: LogisticsDomain: LogisticsshowsshowsScope: MonterreywarehouseModule: LogisticsTable: ShipmentsTable: CustomersFields: carrier, dateFields: name, tax ID
LevelIsRead
DomainAn area of the business that owns a set of tables: sales, logistics, financesDomains
ModuleWhat people open in the launcher to do one jobModules
ScopeThe company, site or team a module works forPlaces
TableOne kind of record: shipments, invoicesTables
FieldOne value of a record: its carrier, its dateTables

Each table belongs to exactly one domain. A module shows the tables its job needs, and they can come from several domains: Sales shows customers, from the Parties domain, and products, from the Catalog domain. Permissions follow the same levels: see Access.

Structure

Your organization is your Netzo account. Everything in it belongs to it, and nothing leaves it. Inside, three levels describe how your business is laid out:

OrganizationCompany: Acme MéxicoCompany: Acme USASite: Monterrey warehouseSite: Downtown storeTeam: Inside salesSite: Houston plant
LevelIsExample
CompanyA legal entity, with its own tax ID, books and documents.Acme México S.A. de C.V.
SiteA physical place of a company: a warehouse, a store, a plant.Monterrey warehouse
TeamA group of people who work together.Inside sales

A record carries the levels it belongs to. A sales order belongs to a company and is fulfilled from a site; a stock count belongs to a site.

Modules

A module is what people open in the launcher: Sales, Purchases, Inventory, Finances, Point of sale and others. A module shows the tables its users need, in a navigation of its own. The launcher groups modules in sections: organization setup, insights, daily operations and work at a shared device.

Every module, with its tables, is in Modules.

Places

Every action happens in a place: a module and one of its rows, written <module>/<entity>. sales/acme-mx is the Sales module for the company Acme México; pos/store-1 is the Point of sale module in store 1. A place can also be the whole organization (<module>/organization) or the person (user/user).

Permissions name the place they apply to, so a place decides what a person may do there. See Access. Every integration names the place the same way: see API and CLI.

Portals

A portal is a focused screen for a shared device on the floor: receive goods, dispatch orders, count stock, run a cash register. Before a portal acts, the employee at the device identifies with a PIN or a passkey (a phone or a security key). The device stays signed in; each action records the employee who did it. HR manages employee PINs and passkeys on the employee record.