What you’ll do
Decide whether your account runs flat or parent/child, then send the structure to your Tread implementation lead. Hierarchy is not self-serve — Tread creates the parent and child companies for you. Your job is to decide, confirm, and provide the list.Before you start
- A list of every legal entity, division, or terminal that dispatches trucks.
- Agreement from operations on whether dispatchers cross divisions today.
- Your Tread implementation lead’s contact.
Walkthrough
1
Default to flat
Most Tread accounts run flat — one company, one set of master data. Pick this unless you have a hard reason not to.
2
Use parent/child only for real regional splits
Ask for child companies only when divisions have their own dispatchers, fleets, and books. Users added to the parent can navigate down to every child; users added to a child cannot see parent-level data.
3
Decide where master data lives
If drivers, equipment, and Sites are used across children, create them at the parent and share them down via Company Shares. If children are truly independent regions, manage data at each child. See Companies & Hierarchy for the full model.
4
Send the structure to Tread
Give your Tread implementation lead the entity list, which users belong at the parent, and which belong at each child. Tread creates the companies — confirm the result before any master data is uploaded.