Overview of the Ibiris Travel Web Platform
The Ibiris travel web platform is a modern, enterprise‑grade solution designed to streamline business travel management. Built for web development teams, it combines a user‑friendly front‑end with a robust back‑end that supports multiple deployment options. This course breaks down the core concepts tested in the platform specification quiz, providing developers, product owners, and administrators with the knowledge they need to configure, extend, and maintain the system effectively.
User Roles and Permissions
Understanding who can do what is fundamental to any enterprise application. Ibiris defines a clear hierarchy of roles, each with specific capabilities that align with corporate travel policies.
Demandeur – The Travel Request Creator
The Demandeur (or Requester) is the only role that can create travel requests in the Enterprise space without having approval authority. This role is typically assigned to employees who need to book trips for business purposes. While the Demandeur can fill out forms, attach supporting documents, and submit the request, they cannot validate or approve it. This separation of duties ensures compliance and reduces the risk of unauthorized travel spending.
Manager – Validation and Approval
Managers (sometimes labeled as Validateur/Manager) receive notifications when a request exceeds policy limits or requires additional scrutiny. They have the authority to approve, reject, or forward requests to higher‑level administrators. The platform’s workflow automatically routes requests to the appropriate manager based on organizational hierarchy and policy rules.
Admin Enterprise and Superviseur
Both Admin Entreprise and Superviseur roles possess broader administrative privileges, such as configuring policy thresholds, managing user accounts, and generating enterprise‑wide reports. However, they do not replace the Demandeur’s ability to initiate a request; they focus on oversight and system configuration.
Enterprise Workflow and Policy Enforcement
When a travel request is submitted, the platform evaluates it against the company’s predefined policy limits. If the request exceeds those limits, the workflow does not reject the request outright. Instead, an alert is sent to the Manager for validation. This step allows the manager to either approve an exception, request additional justification, or reject the request based on business needs. By routing exceptions to a manager rather than an automatic rejection, Ibiris maintains flexibility while still enforcing fiscal discipline.
Key workflow stages include:
- Request creation by the Demandeur.
- Automatic policy check.
- Manager notification for out‑of‑policy items.
- Manager decision (approve, reject, or request clarification).
- Final status update visible to the requester and relevant stakeholders.
Notification Channels and Default Settings
Ibiris supports multiple notification channels to keep users informed in real time. The default options include email, Push PWA (Progressive Web App notifications), and WhatsApp. Notably, Telegram is not listed as a default channel. Organizations can extend the notification system via webhooks or custom integrations, but the out‑of‑the‑box experience focuses on the three most widely adopted communication tools in corporate environments.
Document Management: Upload Limits and Best Practices
Travel requests often require supporting documentation such as visas, itineraries, or expense receipts. To balance performance with usability, Ibiris enforces a maximum upload size of 20 MB per document. This limit ensures that files are large enough to retain necessary detail while preventing excessive bandwidth consumption and storage bloat.
Best practices for document handling include:
- Compress PDFs or images before upload.
- Use descriptive file names (e.g., Visa_JohnDoe_2024.pdf).
- Validate file types on the client side to avoid unsupported formats.
- Leverage the platform’s preview feature to confirm successful uploads.
Key Performance Indicators (KPIs) for the Enterprise Dashboard
The Enterprise dashboard provides actionable insights through a set of predefined KPIs. These metrics help travel managers monitor cost efficiency, compliance, and operational speed. The platform explicitly tracks:
- Monthly expenses – total spend per calendar month.
- Number of open requests – pending approvals or actions.
- Average response time (SLA) – time taken by managers to validate requests.
One KPI that is not explicitly mentioned is the Total number of travelers. While this metric can be derived from existing data, it is not a default dashboard widget, allowing organizations to customize reports if that insight is required.
MVP (V1) Roadmap and Future Enhancements
The Minimum Viable Product (MVP) for Ibiris focuses on core travel request functionality, enterprise workflow, and basic reporting. Certain features are deliberately deferred to later releases to ensure a stable launch. Among the postponed items, online payment and multi‑currency support are slated for future phases. This decision reflects a strategic choice to first validate the request creation and approval process before adding complex financial integrations.
Other features that are part of the initial MVP include:
- Enterprise request creation workflow.
- PDF generation of invoices (available in V1).
- Public site with ticket listings (also part of the first release).
Technology Stack Options for Back‑End Development
Flexibility in back‑end technology is a hallmark of the Ibiris platform. The specification offers two primary options:
- Laravel (PHP)
- Node.js
Both stacks provide robust RESTful API capabilities, ORM support, and easy integration with front‑end frameworks such as React or Vue.js. While other frameworks like Django, ASP.NET Core, or Ruby on Rails are popular, they are not listed as official options for this project, allowing development teams to choose the stack that best aligns with existing expertise and infrastructure.
Request Types: Visa vs. Other Travel Requests
Ibiris categorizes travel requests by type, each with a tailored creation flow. When a user selects the "Visa" request type, the platform guides them through a specific set of steps:
- Choosing the request type (Visa).
- Filling a dedicated visa application form.
- Uploading supporting documents such as passport scans and invitation letters.
The step that is not part of the standard Visa workflow is selecting a payment method. Visa requests typically involve external processing by consular services, so payment handling is managed outside the Ibiris platform. In contrast, other request types like "Flight" or "Hotel" may include payment selection as a required step.
Conclusion and Next Steps
By mastering the concepts outlined above—role‑based permissions, policy‑driven workflow, notification channels, document limits, KPI tracking, MVP planning, back‑end stack choices, and request‑type specifics—developers and administrators can confidently configure the Ibiris travel web platform for their organization. The next practical steps include:
- Setting up user roles in the admin console and testing the Demandeur‑to‑Manager approval flow.
- Customizing notification preferences to match corporate communication policies.
- Implementing the chosen back‑end stack (Laravel or Node.js) and integrating with existing identity providers.
- Running a pilot with a small group of travelers to validate document upload limits and KPI dashboards.
Continuous feedback loops and iterative releases will ensure that the platform evolves from the MVP to a fully featured travel management solution, eventually incorporating advanced features like multi‑currency payments and AI‑driven policy recommendations.
