Quick start

The steps every organization takes before its people start working in Netzo, on the surface you choose.

Every organization takes the same six steps, in this order: each step uses what the step before created. You need a user, or an API key, with full access. The person who created the organization has it.

Every step works in the app, with an AI assistant, over the API and in the CLI. Pick yours in any step: all steps follow.

Lay out your organization

Add each company (a legal entity, with its tax ID), then its sites (warehouses, stores, plants) and its teams. Records and permissions refer to these levels, so they come first. See Organization.

In Administration → Organization → Companies, add each company. Under each company, add its Sites and Teams.

Create the company "Acme México" with tax ID AME850101AB1, its site "Monterrey warehouse" and its team "Inside sales".

curl -X POST https://app.netzo.ai/api/rpc/companies/create -H "x-api-key: $NETZO_API_KEY" \
  -H "content-type: application/json" -d '{ "label": "Acme México", "taxId": "AME850101AB1" }'

Then sites/create and teams/create, with the new companyId.

netzo companies create --label "Acme México" --taxId AME850101AB1
netzo sites create --companyId <id> --label "Monterrey warehouse"
netzo teams create --companyId <id> --label "Inside sales"

Check your modules

Your organization's modules (Sales, Purchases, Inventory, Finances and others) are turned on when Netzo sets up the organization; no surface changes them. Check that the modules you need are there, and ask Netzo for any that is missing. See the module reference.

Open your organization in Administration → Organization → Organizations, then its Modules tab.

Which modules are turned on for my organization?

organizationmodules/find lists them.

netzo organizationmodules find

Create roles

Create one role per job: a buyer, a warehouse lead, an accountant. A role holds permission lines, <table>.<action>@<module>/<place>: salesorders.*@sales/* allows every action on sales orders in Sales, in every place. Keep full access (*.*@*/*) for a few administrators. To make an action wait for a second person, add a policy. See Access.

In Administration → Access → Roles, add each role and its permissions. Policies are in Administration → Access → Policies.

Create the role "Buyer" with every action on purchase orders in Purchases, and a policy so that approving a purchase order needs the role "Purchasing lead".

roles/create with { "label": "Buyer", "permissions": ["purchaseorders.*@purchases/*"] }. Policies are procedurepolicies/create.

netzo roles create --input '{ "label": "Buyer", "permissions": ["purchaseorders.*@purchases/*"] }'

Add your people

Add each person with their email and one role.

In Administration → Access → Users, add each person.

Add Ana López, [email protected], with the role "Buyer".

users/create with { "name": "Ana López", "email": "[email protected]", "roleId": "<id>" }.

netzo users create --name "Ana López" --email [email protected] --roleId <id>

Load your master data

Load the records everything else refers to, in this order: catalogs (products, their items and units, services), then customers and suppliers with their branches and contacts, then opening balances such as stock and open invoices. Load a table only after the tables it refers to; Domains lists them. Match each row on its business key, such as a product SKU or a tax ID, so a second run updates instead of duplicating.

Catalogs are in Master data, customers and suppliers in Directory. For more than a few records, use an AI assistant, the API or the CLI.

Attach your spreadsheet or document:

Load the `netzo-mcp-import` skill with `get_skill` and follow it to load the attached spreadsheet.
Map each column to a field from `describe_table`, match existing records on their business key, and run a dry run first.
Show me the mapping and the dry-run result before you save anything.

For each row, find on the business key, then update the record you find or create a new one. Send x-netzo-dry-run: 1 first to check every row without saving.

netzo customers create --label "Ferretera del Norte" --taxId FNO920315KX2 --dry-run
netzo customers create --input @customer.json

Adjust Netzo to your business

Optional: set your options (the values of your lists), tags, views, and document and label templates. They are tables like any other, on every surface.

In Administration → Personalization.

Add the tag "Key account" and a view of open sales orders sorted by delivery date.

options, tags, views, documenttemplates and labeltemplates, with create and update.

netzo tags create --label "Key account"

Done when a person of each team signs in, sees their modules and opens a record.

Who it is for

The businesses Netzo is for, the people and agents who work in it, and where it runs.

Implementation

The phases to set up Netzo in an organization, and what to use in each one.