Settings

• Group similar services together
• Filter services in your library
• Quick navigation and search

• Tag suppliers with categories they provide
• Filter suppliers by category when assigning to services

• Create category-specific custom fields
• Different data for accommodation vs. activities

• Configure mandatory fields per category
• Accommodation POs can require different fields than activity POs

• Map categories to AXUS reservation types
• Required for external integrations

• Rename the seeded categories to match your own language before adding new ones
• Check the Services column — categories with no services are candidates to remove

• Don’t create too many empty categories upfront
• Add new categories when you have 10+ services for them

• Plural vs. singular (choose one approach)
• Clear, descriptive names
• Avoid overly specific categories

• Don’t create “Hotel”, “Lodge”, “Resort” as separate categories
• Use “Accommodation” category with “Hotel”, “Lodge”, “Resort” tags

• Enables interactive maps on Journeys showing trip destinations
• Helps travellers visualize the geographical scope of their journey
• Maps automatically display all mapped areas from services in the Journey
• Areas without Google Maps mapping won’t appear on Journey maps

• Filter services by area in service library
• Find services available in specific destinations

• Tag suppliers with areas they operate in
• Filter suppliers by location when assigning to services
• Example: Find all accommodation suppliers in Paris

• Add services from specific destinations
• Filter by area while building trips

• Areas appear on Journeys
• Travellers see which destinations are included
• Example: “3 nights in Paris, 2 nights in Lyon”

• Understand service coverage across destinations
• Identify gaps in service portfolio

• “Paris” not “France” (too broad)
• “Bangkok” not “Thailand” (too general)
• Use names travellers will recognize
• Remember: Areas appear on confirmed Journeys that travellers see

• Use specific areas, not entire countries
• Services can have multiple areas if they span regions
• Example: Multi-day tour might include “Paris + Lyon + Marseille”

• Use official place names
• Be consistent with spelling
• Decide on naming convention (e.g., “Cape Town” vs. “Cape Town, Western Cape”)

• Add areas as you offer services there
• Don’t create areas with no services yet
• Organize by actual destinations you serve

• Use countries to organize areas
• All areas must belong to a country
• Countries themselves aren’t used for filtering

• An image added to a service
• A Journey cover image
• A travel agency or supplier logo

• Tag name - The tag label
• Usage count - How many services use this tag
• Created date - When the tag was first created

• Use the search bar to find specific tags
• Tags are sortable by name or usage

1. Find the tag in the list
2. Select the tag using the checkbox
3. Click “Delete selected”
4. Confirm deletion

1. Select multiple tags using checkboxes
2. Click “Delete X selected”
3. Confirm deletion

• Tag is removed from all services that use it
• Tag no longer appears in tag dropdown
• Historical data is preserved (services retain other tags)

• Click Add Currency
• Select from the provided list of currencies
• Multiple currencies supported

• Use the bin icon on the currency row
• You cannot remove a currency while it is the Selling Default or the Cost Default — set a different default first

• The Selling Default and Cost Default apply across your whole account
• Every service added to a Journey is created with those two currencies

• Each service carries two independent currencies: one on Cost and one on Selling price
• Both are editable in the service’s price dialog inside the Journey, each with its own selector next to the amount
• They do not have to match — a service can cost you USD and sell in EUR, and Odia converts between them using your exchange rates to work out the margin
• Mix currencies across services within the same Journey whenever you need to
• Example: EUR for a Paris hotel, USD for international flights

• In Journey preview, open Currency, choose a currency, review Total, and choose Use with the currency code
• The list uses your organization’s configured currencies; choosing one leaves the original service prices and currencies unchanged
• A missing exchange rate blocks confirmation and identifies the required pair
• Publish updates the public Journey; published versions keep their saved currency and exchange rates
• Keep the account defaults for your normal pricing; choose a single Journey’s display currency in its preview

• Public Journeys (unless white-label mode is enabled)
• Confirmed Journey pages
• Purchase orders
• Communications

• High-resolution recommended
• Transparent background preferred (PNG)
• Supports PNG, JPG, SVG formats

• When enabled on Journeys, your logo is hidden
• Only agency logo shows
• Use for B2B relationships where agent owns client

1. Go to Settings > Organization > General Settings and find Branded public links
2. Enter the subdomain you want (lowercase letters, numbers, and hyphens only)
3. Click Request subdomain
4. Odia configures and activates it — typically within a few hours during business hours

• New public links keep using your current address (or the default odia.app domain if you don’t have one yet)
• Any links you’ve already shared keep working without interruption

• New public Journey links use your branded address
• You can request a replacement subdomain later the same way; your current address stays active until the new one is configured

• Heading font — used for day titles, section headers, and service names
• Body font — used for descriptions, details, and supporting text

• Save — applies all current settings (colors, toggles, fonts, layout) to your organization.
• Reset — reverts every field to the system defaults: Primary #0F172A, Accent #64748B, Lora for headings, Manrope for body, the Flow page layout, and both toggles off. This does not save automatically — you must choose Save after resetting for the defaults to persist.

• Use for: Names, descriptions, notes, IDs, addresses
• Example: “Passport number”, “Dietary restrictions”, “Internal notes”, “Preferred room type”
• Character limit: Unlimited text

• Use for: Quantities, measurements, counts, amounts
• Example: “Group size”, “Room number”, “Age”, “Net rate”
• Supports: Whole numbers and decimals

• Use for: Binary options, flags, true/false conditions
• Example: “VIP client”, “Requires wheelchair access”, “Vegetarian”, “Confirmed”
• Display: Checkbox (checked = yes, unchecked = no)

• Use for: Dates, deadlines, anniversaries, expiry dates
• Example: “Passport expiry date”, “Contract expiry”, “Anniversary date”, “Date of birth”
• Format: Standard date picker interface

• Use for: Categories, classifications, selections from fixed list
• Example: “Industry type” (Finance, Tourism, Corporate), “Service tier” (Bronze, Silver, Gold), “Meal preference” (Vegetarian, Vegan, Pescatarian, Omnivore)
• Requires: Define all dropdown options when creating field
• Selection: Single selection from dropdown

• Use for: Relationships between entities, lookups
• Example: Link service to a contact, reference another Journey, connect to specific organization
• Requires: Specify which entity type to reference
• Advanced feature: Creates data relationships

• Target specific contact subtypes (e.g., “Traveller”, “Travel Agent”, “Supplier Contact”)
• Field only shows for contacts of that subtype
• Example: “Passport number” field only for Traveller subtype
• Different fields for different contact types

• Target organization subtypes (e.g., “Travel Agency”, “Supplier”)
• Scope fields to specific organization types
• Example: “Commission rate” field only for Travel Agency subtype
• “Net rate structure” field only for Supplier subtype

• Target specific service categories (e.g., “Accommodation”, “Transportation”, “Activities”)
• Field only appears in purchase orders for services in that category
• Example: “Room type” field only for Accommodation purchase orders
• “Vehicle type” field only for Transportation purchase orders

• Cleaner interfaces (only relevant fields show)
• Category-specific data collection
• Flexibility for different use cases

• Passport Number (Text)
• Passport Expiry Date (Date)
• Dietary Restrictions (Multi-Option: Vegetarian, Vegan, Halal, Kosher, None)
• Wheelchair Accessible (Boolean)
• Loyalty Program Number (Text)
• Emergency Contact Name (Text)
• Emergency Contact Phone (Text)

• Agent ID (Text)
• Preferred Contact Method (Multi-Option: Email, WhatsApp, Phone)
• Languages Spoken (Text)
• Specialization (Multi-Option: Luxury, Adventure, Family, Corporate)

• Net Rate Structure (Text)
• Contract Expiry Date (Date)
• Preferred Payment Terms (Multi-Option: Net 30, Net 60, Prepay, On Completion)
• Supplier Tier (Multi-Option: Preferred, Standard, Backup)
• Commission Rate (Numeric)

• Agency Tier (Multi-Option: Platinum, Gold, Silver)
• Preferred Payment Terms (Text)
• Marketing Fund Contribution (Numeric)

• Room Type (Text)
• Bed Configuration (Multi-Option: Twin, Double, King, Suite)
• View Type (Multi-Option: Ocean, Garden, Mountain, City)
• Floor Preference (Text)
• Special Requests (Text)

• Difficulty Level (Multi-Option: Easy, Moderate, Difficult, Extreme)
• Activity Duration (Numeric - hours)
• Minimum Age (Numeric)
• Equipment Provided (Boolean)

​

Service Management

​

Settings Access

​

CRM & Contacts

​

Common Features (All Roles)

• View services
• Basic navigation
• Message access (WhatsApp, Inbox)
• Task management
• View travellers
• Basic Journey creation
• View confirmed Journeys

• Complete system control
• Billing and subscription management
• Can transfer ownership
• All permissions

• Configure all settings
• Manage users and permissions
• Create categories, areas, custom fields
• Manage integrations
• Cannot access billing

• Create and edit services
• Manage Journeys
• Create suppliers and agencies
• Limited settings access
• Cannot manage users or critical settings

• View and use services
• Create Journeys (limited)
• View own confirmed Journeys
• Basic CRM access
• No settings access

• Send and receive messages
• Share images and documents
• Voice messages
• Real-time chat

• See contact information in sidebar
• Link WhatsApp contacts to CRM contacts
• View traveller’s confirmed Journeys while chatting
• Access Journey history

• Create WhatsApp groups for trips
• Manage group participants
• Group messaging for travel parties

• Connect multiple WhatsApp Business numbers
• Switch between accounts
• Team members can use different numbers

• Use {{RECIPIENT_NAME}} in your intro to insert the name of whoever the message is going to.
• The button above the box inserts it for you.

• The panel on the right shows the intro, sample service details, your closing and the signature together, and updates as you type.

• Connect more than one WhatsApp Business number — each gets its own card.
• Team members can message from different numbers, and switch between them when messaging.
• Use Sync Notification Users in a card’s ⋮ menu so everyone currently on the team is notified of incoming messages on that number. It runs once when you press it, so repeat it after someone joins the team.

• Emails linked to the relevant Journey
• Team visibility into communications on a shared mailbox
• Purchase orders and reminders send from a real address your suppliers recognise

• Google and Outlook accounts show a Reconnect button on the row. Use the same address; a different one creates a second account instead of repairing this one.
• IMAP accounts have no Reconnect button. Disconnect the account and connect it again.

• Map each Odia service category to an AXUS reservation type
• Required for proper data synchronization
• Unmapped categories cannot be pushed to AXUS
• Click on each category to select the corresponding AXUS type

• View all confirmed Journeys pushed to AXUS
• See push timestamps and status
• Track successful and failed pushes
• Review push details

• AXUS requires specific reservation type codes
• Each Odia category must map to an AXUS type
• Services with unmapped categories are excluded from push
• Proper mapping ensures data accuracy in AXUS

• Accommodation → Hotel/Resort
• Transportation → Transfer/Car Rental
• Activities → Tour/Activity
• Dining → Restaurant
• Tours & Guides → Guided Tour

1. Go to Settings → Organization → General Settings.
2. Open Invoicing, then select Payment Instructions.
3. Select Add payment instructions.
4. Name the profile and enter the details exactly as they should appear to the client.
5. Set the profile as the default if it should be selected automatically on new invoices.
6. Select Save Changes.

1. Go to Settings > Organization > General Settings and open the Invoicing tab
2. Find the Line Item Defaults section
3. Enter your preferred default description text
4. Save changes

• When you add a new line item to an invoice, the description field auto-populates with your default text
• You can still edit the description for individual line items
• Useful for standardizing invoice terminology across your organization

• Consistent service descriptions across all invoices
• Pre-filled terms or conditions per line item
• Standard formatting for professional invoices

• Full system control - Only one Owner per organization
• Transfer ownership to another user
• All permissions of Admin role
• Complete access to all features and settings

• Settings & Configuration:
  • Configure all settings (categories, areas, branding, custom fields, purchase orders)
  • Manage users and assign roles
  • Access all financial settings
• Operations:
  • Create and edit services
  • Create Journeys
  • Create and manage suppliers, travel agencies, and all contacts
  • Send purchase orders
  • View all organization data

• Content Management:
  • Create and edit services
  • Create Journeys
  • Create and manage suppliers, travel agencies, and all contacts
  • Send purchase orders
• Limitations:
  • Cannot manage users or assign roles
  • Cannot configure organization settings

• What Users can do:
  • View services (cannot create or edit)
  • Create Journeys
  • Create and manage suppliers, travel agencies, and all contacts
  • Send purchase orders
• Limitations:
  • Cannot create or edit services
  • Cannot manage users or assign roles
  • Cannot configure organization settings

• Create/Edit Services
• Delete Services
• Manage Tags
• View Services

• Categories & Areas
• Currencies
• Branding
• Custom Fields
• Integrations
• Team Management

• Create Organizations (Suppliers, Agencies)
• Edit Organizations
• Create Contacts
• Edit Contacts
• View All vs Own Only

• View Invoices
• Create Invoices
• Manage Pricing

• Create Journeys
• Edit Journeys
• Confirm Journeys
• View All vs Own Only

• Decide their role based on responsibilities
• Ensure email domain matches organization
• Plan their training and access needs

• Assign appropriate role immediately
• Provide onboarding documentation
• Set up their preferences (timezone, date format)
• Assign initial tasks or Journeys as needed

• User - Operations team, junior staff
• Supervisor - Senior operations, team leads
• Admin - Management, IT, senior leadership
• Owner - Typically company owner or managing director

• Don’t create every possible category upfront
• Add categories when you have 10+ services for them
• Begin with destinations you actively serve
• Expand as business grows

• Use standard naming conventions
• Be consistent with terminology (remember: areas appear on confirmed Journeys)
• Document decisions in team guidelines
• Train team on standard practices

• Review categories and areas quarterly
• Remove unused items
• Update branding as company evolves
• Review custom fields for relevance
• Check integration status monthly

• What data do you repeatedly add to notes?
• What information is critical for operations?
• Which fields would improve reporting?

• Choose appropriate field types
• Decide on required vs. optional
• Consider subtypes for targeting
• Test with sample data first

• Too many fields overwhelm users
• Start with 3-5 essential fields per entity
• Add more only when proven necessary
• Review usage after 3 months

• Connect early for immediate messaging capability
• Test with team messages first
• Train team on WhatsApp features
• Use appropriate number for customer-facing communications

• Connect all team email accounts
• Ensure team understands email tracking
• Review communication history regularly
• Use for Journey communications

• Complete category mapping before first push
• Test with one Journey first
• Document mapping decisions
• Review push history regularly
• Update mappings as you add categories

• Only connect integrations you’ll actively use
• Secure credentials carefully
• Document integration workflows
• Train team on integration features

• Assign minimum necessary access
• Users don’t need Admin access for daily work
• Reserve Admin for leadership and IT
• Most team members should be Users or Supervisors

• Quarterly access reviews
• Remove departed team members immediately
• Adjust roles as responsibilities change
• Document role assignment decisions

• Train users on features they can access
• Provide role-specific documentation
• Clear escalation paths for access needs
• Regular refresher training

• Categories and Areas
• Custom Fields
• Currencies
• Branding
• Integrations (WhatsApp, Inbox, AXUS)
• Team Management
• Purchase Order configuration

• Personal date/time preferences
• Image gallery (view and search)

• Date/time settings
• Image gallery

1. Go to Services section
2. Filter by the category you want to delete
3. Edit each service one by one
4. Change to a different category
5. Once no services use the category, delete it from Settings

1. Go to Services section
2. Filter by the area you want to delete
3. Edit each service one by one
4. Change to a different area
5. Once no services use the area, delete it from Settings

• All values stored in that field across all records
• Field configuration
• Field visibility

• Export data if you need to keep it
• Confirm the field is truly unused
• Check with team that no one needs the data
• Consider hiding the field instead (mark as optional, don’t require)

• Field name/label
• Required vs. optional status
• Dropdown options (for Multi-Option fields)
• Field visibility settings

• Entity type (Contact, Organization, or Purchase Orders)
• Subtype targeting
• Field type (Text, Numeric, Boolean, etc.)

1. Create a new custom field with correct settings
2. Manually migrate data if needed
3. Delete old field

1. Go to Settings > Communications > WhatsApp
2. Click “Disconnect” for specific phone number
3. Confirm disconnection
4. Connection is immediately revoked

1. Go to Settings > Communications > Connected Inbox
2. Click “Disconnect” button
3. Confirm disconnection
4. Email integration disabled

1. Go to Settings > Integrations > AXUS Travel
2. Delete stored credentials
3. Integration is disabled

• Existing synced data remains unchanged
• No new data will sync
• You can reconnect later without data loss
• Historical records are preserved

• One Owner per organization
• Has access to billing and subscriptions
• Can transfer ownership to another user
• All Admin permissions plus organization-level controls

• Current Owner can transfer to another team member
• Contact support to arrange it — there is no self-service transfer in Settings
• Previous Owner becomes Admin after transfer

• Each service keeps its own cost and selling currencies, separately from the currency chosen in Journey preview
• Each new service is created with your account’s Selling Default and Cost Default
• You can change both on any individual service: the Cost currency and the Selling price currency are independent

• Open the service inside the Journey and open its price dialog
• Each of the Cost and Selling price rows has its own currency selector next to the amount — change either or both, then save

• Journey summaries showing destinations
• Confirmed Journey day headers
• Service location details
• Trip overview sections

• Use recognizable, traveller-friendly names
• “Paris” not “Paris Admin Region”
• “Bangkok” not “BKK”
• Spell correctly - travellers will see these