Access to every organization permission, including team management and settings reserved for the account holder.
The organization brings headquarters and branches into the same account, each agency with its own data. Every person on the team has their own login and role, and the owner knows who did what.
It is the part of the system that organizes who works and where. The organization is the group's account: it can have one or several agencies, such as headquarters and branches, each with its own separate passengers, trips and finances.
Inside each agency, every person has their own login. When it is time to invite someone, you create the access and send the link: the person sets their own password and signs in with the role you chose for them.
The role defines what each person can see and do. The salesperson sells and looks after their customers without opening the finances. Finance handles payments and reports without touching settings. And it is all recorded in the audit trail.
If your operation still runs like this, you have already paid that price.
The same username and password going around the team's group chat. When something goes missing or changes, nobody knows who touched it.
"Don't touch the finances, okay?" said in the hallway. In practice, everyone opens everything, because the system does not separate.
Headquarters and branches in separate files, with no consolidated view. The owner adds it all up by hand to know how the group is doing.
Each agency operates with its own data. The owner follows the whole.
The group comes in as one organization and registers each agency: headquarters, branch, new unit. Each one has its own passengers, trips, documents and finances.
The organization's owner follows the group's indicators and can work within each agency's scope. Operational data stays associated with the corresponding agency.
One access can cover every agency in the organization or be limited to just one. Role and scope are set separately under Team > Access.
The manager registers the person and picks the agency and the role. The system shows a first-access link to share.
The role determines which actions are available. The scope defines whether the person works across the whole organization or in one specific agency. The roles below are the starting points; organization administrators can create custom roles.
Access to every organization permission, including team management and settings reserved for the account holder.
Broad permissions to run operations and access, except actions reserved for the account holder, such as subscription and transfer.
Access to the finance and reporting areas, plus the view permissions needed to follow operations.
Permissions to work with trips, passengers, bookings and CRM. The default role does not include finance permissions.
Read permissions to follow the information without changing records.
The organization administrator chooses the new role's permissions and decides who to assign it to.
Role names are starting points. The exact list of actions comes from the permissions available in the system, and a person's scope also limits the data they can access.

In the app, the manager uses the Team > Access area to manage people, roles and the scope of each access. The organization view brings the group's agencies together; each agency keeps its own operation.
Real separation, in the database, and a record of what was done.
Someone from one agency cannot access another agency's data. Not passengers, not trips, not finances. The separation holds in the database, not just on the screen.
Access and sensitive actions are recorded. The owner knows who entered the system and what was done, without having to ask.
Driver, guide and coordinator go in the Staff tab of each trip, with per diems in the transparent finance breakdown.
On the team screen you create the access and get a link to send to the person, who sets their own password. The system does not send an automatic email.
Owner, admin, finance, agent and read-only, each with its own set of permissions. You can also create a custom role with whatever permissions the agency wants.
No, if their role does not include finance. Each role unlocks only what the person needs: the agent sells and looks after their customers without opening payments and reports.
Yes. The organization brings headquarters and branches into the same account, each agency with its own data, and the owner follows the whole with a balance per agency.
No. Isolation is per organization and per agency: someone from one agency cannot access another agency's data, and the system records access in an audit trail.
Yes. Access and sensitive actions are recorded in the audit trail, so the owner knows who signed in and what was done.
Message us on WhatsApp and we will show you the team screen, the roles and the per-agency view using your own examples.
I want to organize my team See how OnWay works