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

# Mailbox

> Let Luca read along in a Microsoft 365 mailbox and pick out the invoices.

Most invoices arrive in a mailbox that nobody wants to rewire. Connect that mailbox to Glimps and Luca reads along, decides what is an invoice, and brings it in.

Set it up under **Settings > Email**. You need a Microsoft 365 account, and your IT admin may have to grant consent once.

## Watch first, import later

The mailbox starts in **watch only**. Luca reads, judges, and shows what it found, and imports nothing. You import with one click.

Switch to **automatic** when you trust what you see. Luca then brings found invoices in by itself.

<Tip>
  Leave it on watch only for a week. The [Mailbox](https://platform.useglimps.com/mailbox) page shows exactly what Luca would have done, at no risk.
</Tip>

## An extra brake, just for this mailbox

Imported invoices follow your normal rules. You can make them stricter for this mailbox alone:

| Choice | What happens |
| - | - |
| Just like your other invoices | No extra brake. Recommended. |
| Only book with a PO match | Only a confirmed purchase order match goes through by itself. |
| Always ask me first | Every invoice is prepared as a draft. You do the booking. |

This choice can only be stricter than your normal setup, never looser.

<h2 id="folders">
  Folders
</h2>

By default Luca reads the inbox. You can point it at other folders too, and each folder has a job:

* **Judge first**: Luca reads along and picks the invoices out, the same as the inbox.
* **Import everything**: anything you drag into this folder is imported, with no second opinion.

A drop folder is the fastest route for invoices you already recognised yourself. Drag the mail in, and the invoice is in Glimps a few minutes later.

<Warning>
  A folder that already holds mail imports that mail too. Glimps warns you and tells you how many messages are in there before you add it.
</Warning>

## Senders Glimps skips

Newsletters, bank alerts, and the colleague who forwards the weather. Add them to the exclusion list and Luca stops reading their mail.

Exclude one address, or a whole domain by starting with an at sign. Excluding a sender also clears what is still open from them.

You can also exclude a sender straight from a mail in the Mailbox page.

## The Mailbox page

Open **Mailbox** in the sidebar to see what Luca found.

* **Invoices**: what Luca reads as an invoice. Import it, or mark it as already done.
* **Other mail**: everything else, sorted by why. Needs a look, money but not an invoice, other mail, and ignored.

Every mail shows the document on one side and the mail itself on the other. Luca says how it read the mail: invoice, credit note, reminder, order confirmation, statement, quotation, and so on.

<Note>
  Luca sometimes gets it wrong. Both directions are one click. You can import from **Other mail**, and you can mark an invoice as already handled so Luca leaves it alone.
</Note>

## What Luca flags

| Flag | Meaning |
| - | - |
| Already in Glimps | The same invoice is here, found by number, file name, or an identical file |
| Forwarded invoice | A colleague forwarded it, so the sender is not the supplier |
| Invoice with a question | The mail asks something as well. Read it before you import |
| Suspicious | The mail failed a sender check, or it mentions changed bank details |

<Warning>
  A mail that mentions new bank details deserves a phone call to a number you already had. Glimps flags it, but only a person can confirm it. See [the bank account check](/invoices/checks#bank-account).
</Warning>

## After an invoice is processed

Glimps can mark the mail in Microsoft 365 once it is done: add a category, move it to a folder, or both. Your mailbox stays tidy without a rule of your own.

## Connecting several mailboxes

You can connect more than one. Add a shared mailbox by filling in its address when you connect, as long as your Microsoft account already has access to it.


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