> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tripmazer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Mazer for Teams

> Your company's travel desk: people ask Mazer for work trips in chat or search on the desk, Mazer checks each one against your policy, a manager approves with one tap, and the trip is booked, watched and claimed in one place.

Mazer for Teams gives your company its own travel desk. Your people ask Mazer for a work trip on WhatsApp, Telegram, Slack or the TripMazer app, or search for one on the desk. Mazer prices flights and hotels, checks each against the traveller's policy and sends their pick to the right approver. Once it's approved, it's booked through TripMazer, and Mazer watches the flights until the traveller lands. After the trip, they claim their expenses in one go and finance pays them back.

It works in two places:

* **In chat:** the same Mazer each person already uses. Their personal trips, chats and memories stay theirs; the company sees only the work trips they ask for.
* **On the desk**, at [tripmazer.com/teams/desk](https://tripmazer.com/teams/desk): where people book, approvers decide, travel admins book approved trips and run the policy, and finance pays claims.

## Who does what

The desk shows each person what their role needs. Your role is under your name at the foot of the menu.

| Role | What they do |
| - | - |
| **Traveller** | Asks for work trips, books on **Book**, adds expenses and claims them. Sees their own trips and their policy |
| **Approver** | A traveller's manager, or anyone the approval chain names: a department head, a budget's or a project's owner. Approves or declines on WhatsApp, Telegram, Slack, the email or on **Approvals**, and sees their team's trips |
| **Travel admin** | Runs the desk: people, policy and settings. Books approved trips with the company card, can decide any trip, and sees **Who's where** and **Reports**. The owner makes someone a travel admin on **People** |
| **Finance** | Anyone a travel admin marks as finance on **People**. Sees every trip and claim, decides and pays claims and advances, and makes the payroll file |
| **Owner** | The person who set up the desk. A travel admin who also chooses the plan and who else is a travel admin |

## The desk, page by page

The menu has two groups: **My travel**, for everyone, and **Company**, for anyone who approves, books, pays or runs the desk.

| Page | What it's for |
| - | - |
| **Book** | Search flights and hotels already checked against your policy, and send a trip. See [Booking work trips](https://docs.tripmazer.com/teams/booking-trips.md) |
| **Trips** | Your trips, and the ones you asked for colleagues. Called **My trips** for approvers |
| **Expenses** | What you paid yourself on work trips, your claims and advances. Approvers decide claims here, and finance works the claims queue. See [Expenses and claims](https://docs.tripmazer.com/teams/expenses-and-claims.md) |
| **Your policy** | What your grade may book, and what needs approval |
| **Your details** | Your name as on your ID, passport, preferences, emergency contact and your dates away |
| **Overview** | The year on one screen: spend month by month against last year, where it went, what the desk saved and how, the carbon of your flights, and how the desk is used (travel admins and finance, who land here). See [The Overview](https://docs.tripmazer.com/teams/reports-and-books.md#the-overview) |
| **Approvals** | Trip requests waiting for a decision, one card at a time (approvers) |
| **Events** | Offsites and conferences: one approval covers everyone's travel that fits, with who's coming and arrivals. See [Events and guests](https://docs.tripmazer.com/teams/events-and-guests.md) |
| **All trips** | Every trip you can see, and the approved ones waiting to be booked |
| **Who's where** | Who's on a work trip today, this week or in the next 30 days, on a list and a map (travel admins and finance) |
| **Reports** | Spend by person, team and city, what went outside the policy, rewards, and your books (travel admins and finance). See [Reports and books](https://docs.tripmazer.com/teams/reports-and-books.md) |
| **People** | Your team in one list, with their grades, managers and roles. Travel admins invite people, share the join link and edit anyone from the list |
| **Policy** | Grades, approvals, payments and expenses, and your own rules (travel admins). See [Policy and approvals](https://docs.tripmazer.com/teams/policy-and-approvals.md) |
| **Settings** | **General** (country, currency and time zone, the desk's look, logo and colour), **Plan and bookings**, **Connections** (Slack and the staff list), **Structure** (departments, cost centres, projects, offices and legal entities) and **Trip fields and codes** (travel admins) |

On a phone, the main pages are tabs along the bottom and the rest are under **More**. **Ask Mazer** (**⌘K**, or **Ctrl K** on Windows) opens Mazer beside any page. See [Mazer and Slack](https://docs.tripmazer.com/teams/slack-and-mazer.md).

## Companies outside India

The desk works for companies outside India too. A company picks its country, currency and time zone when it starts: money on the desk shows in its currency, reminders and digests keep its clock, and trips are priced from its country. See [Country, currency and time zone](https://docs.tripmazer.com/teams/getting-started.md#country-currency-and-time-zone).

## Start here

> [card] [Getting started](https://docs.tripmazer.com/teams/getting-started.md)
>
> Set up your company, invite your people and choose who approves.

> [card] [Policy and approvals](https://docs.tripmazer.com/teams/policy-and-approvals.md)
>
> Grades, hotel caps, the daily allowance, approval chains and budgets.

> [card] [Booking work trips](https://docs.tripmazer.com/teams/booking-trips.md)
>
> Ask in chat or search on Book, then approvals, booking and the trip watcher.

> [card] [Expenses and claims](https://docs.tripmazer.com/teams/expenses-and-claims.md)
>
> Bills read from photos, claims, advances and the finance queue.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.