What an organisation keeps separate
Each organisation has its own:
- Data — drivers, stops, runs, orders, customers, rates and invoices.
- API credentials — a client id and secret is issued inside one organisation and can only ever see that organisation's data.
- Webhooks, map keys and settings.
- Members — the people who can sign in to the management portal and manage it, each with their own roles.
- Modules — the capabilities it has been given, such as route optimisation or real-time tracking.
There is no way to move a driver, a stop or an invoice from one organisation to another afterwards. Decide where something belongs before you start putting data into it.
How many do you need?
Signing up creates you as a person, not an organisation. You create organisations yourself, as many as suit what you are building. Three patterns cover most cases.
One per application
If you are building more than one product on Mesh, give each its own organisation. Their data, credentials and webhooks stay apart, and a credential leaked from one cannot read the other.
One per customer of yours
If your application serves several businesses of its own — you sell software to courier companies, say — each of them can be an organisation. Their data is then separated by Mesh rather than by your code, and each can be given different modules.
The alternative is a single organisation in which you keep each business's records apart yourself, using Mesh's own customer records. That is simpler to run, and the separation is then your application's responsibility.
One for building, one for real
A separate organisation for development and demonstrations keeps test drivers and test invoices out of the data your business runs on.
Creating one
In the management portal, choose Create organisation. You become its first member.
An application or AI assistant can create one too: POST /api/orgs on the management API, or the create_org tool on the Mesh MCP server. It needs a person's sign-in rather than an API credential, because a credential always belongs to an organisation that already exists.
Core APIs work straight away. APIs that belong to a module answer 403 with module_not_enabled until Locate2u grants that module, as agreed in your Locate2u agreement. Contact your account manager to have one switched on.
Next
Once you have an organisation, create an API credential in it and make your first authenticated call.