MOQO Portal - Rights and Roles Control
Customize Access: Let's draft a "Team Admin Light" based on your needs
Host: Nils Reißig
(Co-Host: Torsten Schönebaum)
Right now, the Team Admin role in the MOQO portal does everything. It was built to cover many different situations — and that means it gives people more access than they actually need.
A fleet manager at a large company needs to see who is allowed to drive and manage cost centers. A service team lead needs to assign drivers to vehicles and track field tasks. An external partner needs to see just enough to do their job — nothing more. Today, all of them get the same set of rights. That is not good for security, and it makes the portal harder to use.
In this session, we want to change that. We will show you what the Team Admin role can do today and where the problems are. Then we will work together to define smaller, focused "rights packages" that fit real jobs — not just system roles.
Let’s give it the working title "Team Admin Light." The idea is simple: every person who works with the portal gets exactly the access they need — no more, no less.
In the second part of the session, we want your input. We will present two starting personas and ask you to help us define a third one based on your own operations.
If you manage people who work with the MOQO portal, this session is for you.
Summary of workshop
After a brief introduction to the actions a team admin can perform, we split into groups and discussed different personas that currently exist and work with the team admin.
Structure / agenda
Different personas / roles with different rights were discovered, e.g. “B2B Fleetmanager”, “External B2B analyst”, “Travel agent”, “Booker”, “Accountant”, “Municipality Admin”. There was an overlap especially in the field of “Driver Management” and “Bookings” which would be sufficient to perform tasks needed. The groups favored a flexible and simple set-up of roles by provider admins and assignment to certain users / user groups.
Presentation and other material
Next steps
As a quick win, editing the “Settings” section as a team admin can be restricted by provider admins
In the long run the results will be considered for the solution design of the updated rights and role concept: "By introducing configurable, domain-scoped permission clusters, MOQO enables providers to grant users precisely the access they need — reducing over-privilege risk, meeting enterprise compliance requirements, and unlocking safer delegation to employees, partners, and third-party integrations."
Workshop: Asset protection measures for private offers
Protect your revenue: How MOQO keeps your fleet safe today — and what comes next
Host: Nils Reißig
(Co-Host: Valerie Casco)
Drivers who don't pay. Drivers who behave badly. Fake accounts. Every operator knows these problems — and they cost real money.
In this session, we explain what MOQO does automatically to protect your fleet: which checks run when a new driver signs up, what happens when a payment fails, and how a fraud report triggers a block.
We will also be honest about improvement potential. Today, providers sometimes have to contact MOQO support to block or unblock a driver. Drivers sometimes do not know why they cannot book and have no way to fix it themselves. We want to change this.
In the second part of the session, we want your input. Which problems cost you the most time? Where do you want more control? What information should drivers see — and what should stay hidden?
Bring your real examples. Your feedback will directly shape what we build next.
Summary of workshop
After a brief introduction to the reasons why driver records are blocked during the onboarding process and afterwards, we briefly dived into MOQO’s fraud prevention mechanisms. Afterwards we split into groups and discussed mainly opportunities related to Transparency and Self Service for drivers and providers.
We discovered the problem statements presented and potential solutions were matching with the operational needs in most of the cases.
A major success was that providers could openly exchange information and experiences of their day-to-day activities.
Photos and further material
Next steps
There were no quick wins identified.
It is a priority to deliver solutions that support the following outcome: "By giving drivers clear, actionable blocking reasons upfront and equipping providers with self-service visibility and control over driver eligibility, MOQO eliminates unnecessary support escalations and puts asset protection management in the hands of providers.”
Customer Support Engine
Master your daily operations: Understanding the new support features and shaping future developments
Workshop Host: Luisa Mangen
(Co-Host: Markus Harmsen)
In this workshop, we present the latest updates and significant enhancements to the MOQO Customer Support Engine, focusing on the integration of Intercom and the newly developed Resolution Center.
Participants will receive a deep dive into the new functionalities and a clear explanation of how these tools streamline the communication flow between providers and end-users. Additionally, we will use this opportunity to receive feedback from providers to enhance these features further.
Workshop summary
The workshop outlined the transition to the new support system. It demonstrated how Fin AI Age resolves inquiries independently and how complex cases (e.g., flat tires) are systematically escalated to service providers. Together, we identified the service providers’ FAQs and determined the limits of automation.
Workshop structure
Review: Support status 6 months ago.
Live Demo: Exemplary reimbursement process in case of a defect.
Theory: Request categorization process (Information vs. Decision).
Data & Facts: Analysis of top topics (Booking, Car, Payment) and performance metrics.
Interactive Part: Discussion on the limits of automation.
Outcomes
The limits of automation vary significantly from provider to provider.
Providers' FAQs.
AI is well-received / has a high adoption rate.
Identification of the most important support topics.
Learning: KI ist besonders stark bei Informationsanfragen (z. B. „Wo ist mein Fahrzeug?“), während Entscheidungsanfragen (z. B. Erstattungen) oft eine menschliche Prüfung oder klare Prozessvorgaben für den Anbieter erfordern.
Workshop materials
Next steps
We will analyse the feedback and use it to determine to what extent we can further automate FIN and what new content we will feed into FIN.
API for absolute beginners (Graph API)
Unlock your data: Understand and use the Graph API without any technical background
This workshop is designed specifically for non-technical users who have never worked with the Graph API before. We will break down the technical barriers and show you exactly how to fetch valuable data from the MOQO platform.
You will leave with a clear understanding of how to seamlessly integrate API data into your regular daily workflow to make better, data-driven decisions.
Structure of the workshop
● Types of Requests
● Target Audiences and Use Cases
● Required Tools
● Overview of the Tools
● Data Extraction Demo
● Basics
● Processing User Data
● Using Discount Codes
● Hands-On Session
● Practical Exercise on Using the API
● Q&A and Discussion
Learnings
● Understanding the basic functions of the Graphiti API
● Knowledge of different types of API requests
Overview of the necessary tools and their applications
● Understanding the data extraction process
● Insight into the processing of user data and discount codes
● Hands-on experience through exercises and demo scenarios
Outcomes
● Participants will be able to use the Graphiti API independently
● Ability to implement simple data extraction processes
● Confidence in using the most important tools and features
● Understanding of practical applications for the API
● Preparation for integrating the API into real-world workflows or projects
● Open questions and challenges were addressed together
Photos, videos, slides or other material
From MOQO to Accounting System: API-Driven Financial Data Integration
Transform complexity into clarity: Overcoming technical hurdles in third-party tool connections - claims management
Integrating financial data into your accounting system doesn't have to be a headache. In this session, Deutsche Bahn Connect (DBC) will showcase a first-hand use case of their SAP BRIM Claims Management integration.
We will explain the relevant endpoints, discuss the difficulties they encountered, and share exactly how they successfully overcame them. Join us to learn how to streamline your accounting connections and transform technical complexity into clear, automated processes.
Workshop summary
The workshop focused on the integration between MOQO, SAP BRIM, and the accounting system. The main focus was on replacing WinLine as the subsidiary ledger system with an API-driven solution. Data flows, interfaces, and requirements for financial data provision were discussed. In addition, open technical and business questions were addressed.
Workshop structure
Introduction and Objectives of the Workshop
Overview of the Existing System Landscape
Replacement of WinLine as the Subsidiary Ledger System
Role of SAP BRIM in the Future Architecture
Integration via MOQO’s Graphiti API
Relevant Data Flows and Financial Data Supply
Requirements for Interfaces and Automation
Open Technical and Business Questions
Learning
Which endpoints are required and for what type of accounting this data extraction is suitable. Description of the endpoints and customizations for the subsidiary ledger system
Outcomes
A shared understanding of the target architecture between MOQO, SAP BRIM, and the accounting system has been established
Requirements for API integration and data flows have been identified
Outstanding technical and business issues have been identified and resolved
Workshop materials
carvaloo Inside MOQO
Practical Experience from Day-to-Day Carsharing Operations
This workshop is an open exchange on how carvaloo’s AI-based damage detection, fully integrated into the MOQO platform, is used in day-to-day carsharing operations. We walk through real workflows, share operational learnings, and explore where full automation creates the most value for operators.
Structure of the workshop
Short Intro
Explaining the problem the carvaloo x MOQO integration addresses
Effort Providers experience
Friction Drivers experience
Presenting what carvaloo does to resolve the problems
Sensor technology
Motion- and Image-AI technology
Driver reporting UI
Claims-ready report with valuable data (timestamp, images, new/old damage comparison, …)
Open discussion
Attendees placing their questions and uncertainties and getting instant answers
Demonstration of example case (impressed attendees)
Learnings
A major benefit of integrating with MOQO is that customers only need to install the necessary hardware in their vehicles; no further action is required from their side. The carvaloo technology does the rest until the claims-ready report.
Workshop materials
Next steps
carvaloo was asked by a bunch of providers for new pilots. They plan to start new pilots soon.
If questions about the workshop come in or providers are interested in carvaloo, they can reach out to Alexander Rothkamm ([email protected]).
ryd - the payment operating system for fleets
Europe's leading payment operating system for fleets and vehicles
Marco Weber introduced the group to ryd fueling and charging in general. A prototype of the current implementation process (MOQO App + ryd) and the ryd Portal which will be made available to those that chose ryd were shown. After introducing the ordering flow (request in MOQO portal, contract with ryd, enable feature per vehicle) a Q&A session started.
The workshop confirmed the core refueling journey as technically feasible for a Q2 2026 go-live (end of June at the latest), with pre-authorization amounts, session control, parallel fueling prevention, and all anti-fraud guardrails treated as mandatory scope before launch — lower-priority features like vouchers and consumption analytics, and alarm logic are explicitly deferred post-launch.
The EV-charging journey still requires dedicated discovery before the testing phase kicks off.
Workshop material
Next steps
MOQO and ryd will finalize implementation and start testing, so that the feature “In App fueling & charging” can be opened for production users asap.
fresh for finance - Your External Insurance Department
fresh for finance transforms the complex world of insurance into a seamless digital experience. With their concept "fresh Carsharing", they provide a specialized portal that handles fleet management, registration, and claims processing with absolute transparency. Their approach is built on the "Collective Principle": by pooling risks across a large community of carsharing providers, they can offer competitive premiums that individual operators could rarely achieve on their own. They don't just process claims; they actively manage them to protect the fleet's profitability.
About fresh for finance
Starting as a classic insurance broker, fresh for finance has evolved into a key digital partner for the shared mobility sector. Their expertise runs deep – they acquired industry pioneer stadtmobil as a client in 2007 and cambio in 2009. Today, they act as an external insurance department for operators, combining personal consultation with a cloud-based platform to reduce bureaucratic hurdles and ensure financial security.
Workshop summary
At the Summit, David Dominguez Pozo led an interactive session in which pressing issues related to fleet insurance, digital claims management, and the “freshCARsharing” concept were presented and discussed.
Further information
Contact
If you’re interested or have open questions, feel free to reach out to David Dominguez Pozo directly via [email protected]