Standard Roles:
- Guest: Limited access, receives notifications and travel documents.
- User: Basic access, manages own profile and trips.
- Selfbooker: Books and manages own trips, similar to User with booking capabilities.
- Arranger: Books trips for others within their company (configurable).
- Approver: Approves or rejects trip requests.
- Fallback Approver: Approves or rejects any trip request within the company.
- Client Administrator: Manages user profiles, travel policies, etc., for their company.
- TMC Agent: Similar to Arranger, but manages trips for clients of the Travel Management Company
- TMC Administrator: Manages user profiles, travel policies, etc., for the TMC.
- GO Agent (deprecated): Had full access (replaced by GTMS Admin with limited access).
- GTMS Administrator: Full access to the Goelett system configuration.
Default Access Scope:
- Each role has a predefined level of access to data and functionalities.
- Access typically aligns with the user’s responsibilities within the company or TMC.
Standard Extensions/Amendments:
- For larger organizations, additional configurations might be needed for Arranger and Fallback Approver roles.
- This includes defining specific users or business units they can manage trips for.
- Client Administrator roles can also be extended to manage specific business units.
- Nominated Approver can appear as an exeption.
Company wide vs own business unit and business unit below in hierarchy.
These 2 most popular options for arranger and fallback approver could also be implemented as 2 separate privileges: - canArrange (with potential BU selection or nominated arrangers) and canArrangeForAll (no options),
- canFallbackApprove and canFallbackApproveForAll.
