Sign-in protection
Security settings include authenticator-based two-factor setup and passkeys. Review the available options for your account and keep recovery information safe.
Security & data
Office roles decide who sees passenger and commercial details. Check how access is organised, and what to ask, before you bring your team into 4fleet.
Explore the controlsOffice experience
Different people need different parts of the operation. Set up individual access and review responsibilities when a person joins, changes role or leaves.
Security settings include authenticator-based two-factor setup and passkeys. Review the available options for your account and keep recovery information safe.
Office roles define access to areas and actions. Owner and administrative responsibilities differ from day-to-day driver, partner and client access.
Review active sessions in Security settings. Company login activity is available to authorised administrative roles.
Company context
Company identity and permissions are part of the application’s access model. Public links and external portals have their own purpose and scope.
When you evaluate access, test the actual role and workflow your team will use. A shared sign-in cannot express who should do what.
Connected services
4fleet uses service providers for parts of the product. Some connections are specific to the features your workspace enables.
See integration detailsTell us which controls, data locations, retention terms or independent evidence your organisation requires. Confirm those requirements before making a purchasing decision.
Contact 4fleetThe operational database is hosted in the EU. Connected services such as payments, maps, email and AI have their own processing arrangements, and some may process data outside the EU. Review the Privacy Policy and contact us with your specific residency or procurement requirements.
No. Office roles decide which areas and actions each person can use. Drivers, clients and partners each see only their own view.
Yes. Turn on authenticator-based two-factor authentication or passkeys in Security settings, and review active sessions there regularly.
AI features need relevant information to perform the requested task, which may be processed by an AI service. Review the enabled features, current data-processing terms and any restrictions your clients place on their information. Keep human review in the workflow.
Send your procurement questions through Contact. Specify the controls, processing locations and contractual documents you need, including a data processing agreement and subprocessor information. We can address your requirements against the current setup.
Use support@4fleet.io for account and data questions. The privacy policy explains the relevant contact and handling information. Never include passwords, verification codes or payment-card details in a message.