Fleet software access controls
Configure organisations, branches, roles, permissions, company policies, notifications, security, privacy, billing, and module settings.
- 01
Define the structure
Create the organisation and branch structure, set business defaults, and decide how access should work between teams and locations.
- 02
Assign the permissions
Invite users, choose roles, and preview the intended access. Test both allowed actions and restricted records before inviting the wider team.
- 03
Review as you grow
Check active users, sessions, activity logs, module settings, and usage. Deactivate departed users and review roles when responsibilities change.
Quick answer
What is MoboSafe Organisation & Access Controls?
MoboSafe workspace administration provides organisation settings, team invitations, scoped user access, custom roles, company policies, notifications, and module configuration. Administrators can manage security and privacy preferences, review activity, monitor subscription usage, and define which teams can view, change, approve, or export information.
Capabilities at a glance
Match data access to team responsibilities.
A single platform should not give every user the same access. A depot operator, fuel manager, accountant, and HR lead each need a different view. MoboSafe combines organisation and data scope with action-level permissions so shared software can still reflect separate responsibilities.
Organisation structure
Maintain company details, timezone, currency, financial year, business hours, and sub-organisations. Configure reporting and data access across business units.
Roles and invitations
Invite team members and assign predefined or custom roles. Scope view, create, edit, delete, approval, export, and settings permissions.
Policies and notifications
Publish company policies, track acknowledgement, and configure alert, reminder, and report recipients across available notification channels.
Security and data settings
Manage two-factor authentication, active sessions, password settings, access logs, retention, export, deletion requests, and consent records.
Define branches, assign roles and review access.
One workspace. The right view for everyone.
Define the structure
Create the organisation and branch structure, set business defaults, and decide how access should work between teams and locations.
Assign the permissions
Invite users, choose roles, and preview the intended access. Test both allowed actions and restricted records before inviting the wider team.
Review as you grow
Check active users, sessions, activity logs, module settings, and usage. Deactivate departed users and review roles when responsibilities change.
Define the structure
Create the organisation and branch structure, set business defaults, and decide how access should work between teams and locations.
Assign the permissions
Invite users, choose roles, and preview the intended access. Test both allowed actions and restricted records before inviting the wider team.
Review as you grow
Check active users, sessions, activity logs, module settings, and usage. Deactivate departed users and review roles when responsibilities change.
User activity and access administration records.
- Role and user activity records
- Policy acknowledgement history
- Data export and retention settings
- Subscription usage views
Evaluate branch and role permissions.
- Choose this for people and organisation access
- Define what dispatchers, fuel approvers, accounts and HR users can view and do in their assigned scope. Organisation structure, branches, vehicle groups and roles work together. Machine credentials and connected-system access are evaluated in the API integrations workflow.
- Test allowed and restricted work
- Prepare a role list with the records, approvals and exports each team needs. Test an allowed action and a record outside that user’s scope. Include an offboarding review: deactivation removes active access while preserving history, and permissions should be revisited when responsibilities change.
Identify the administrator and owners of finance, workforce, fleet, and fuel data. Document the permissions each role needs, confirm retention requirements, and configure notifications by responsibility. Account controls support, but do not independently establish, regulatory compliance.
Module access, vehicle and storage limits, hardware, and supported integrations depend on your subscription and configuration. Scope your quote around the required workflows, including any third-party charges.
Validate our branch and role permissionsUser scope, approvals and offboarding questions.
Can we make a custom fuel-manager role?
Yes. Custom roles can select module-level and action-level permissions, such as viewing fuel records and approving indents without granting unrelated administrative access.
Can an account be disabled without losing its history?
Yes. Team-member deactivation removes active access while preserving the account’s data and history. The documented workflow also supports reactivation.
Can branch data and payroll access be scoped separately?
Organisation scope, branch or depot assignments, vehicle groups and role permissions control data visibility and actions. Custom roles cover individual modules, approvals and exports. Configure the intended finance and HR access, then test both permitted records and restricted cross-branch records during onboarding.
Connect the next part.
Begin
Ready to connect your whole operation?
Explore tracking, trips, assets, fuel, inventory, accounting, and payroll with the MoboSafe team. Build a rollout around the workflows your fleet needs.