此页面仅提供英文版本。

Connect your mailboxes to PanLuma

For the person who sets PanLuma up at your company, and for your IT or email administrator. About 15 minutes per mailbox; one Microsoft path adds up to 2 hours of waiting for Exchange.

PanLuma reads the business mail that reaches your team — booking requests, carrier confirmations, shipper’s letters of instruction, proofs of delivery, arrival notices, customer questions — and turns it into draft jobs, documents filed on the right job, and drafted replies for your people to approve. You decide which mailboxes it reads. There are three ways in:

You haveUseWho does it
A person’s own mailbox (Google Workspace or Microsoft 365)Personal mailboxThat person, in two minutes
A team mailbox such as bookings@ or ops@Shared mailboxA PanLuma admin of the module, plus whoever holds the mailbox’s login (Google) or your Exchange administrator (Microsoft)
A mailbox you cannot connect (another provider, a Google Group, a policy that forbids it)Forward to your General InboxWhoever manages that mailbox’s forwarding

Which should you choose? A team mailbox that the whole operations desk works from is best connected as a shared mailbox: its mail is visible to the people you put on its list, and its documents go straight to the team that handles them. A personal mailbox is private to its owner (see What PanLuma reads), so it suits a coordinator who wants their own customer mail filed on jobs without forwarding it.

Before you start (a PanLuma administrator, once)

  1. Make sure the Mail module is on. Admin → General Settings → Module Access → Mail. Without it, the mailbox settings below do not appear.
  2. Allow mailbox reading. Mail → Settings (/inbox/settings) → Policy tab → Mailbox pickup → Allow users to sync their mailbox. It is off by default, and while it is off nobody’s own mailbox is read, even if they connect it. Shared mailboxes do not depend on this switch.
  3. Choose what synced mail may be filed onto, on the same tab: which folders are read (Inbox, Sent, or both) and whether mail may be filed onto contacts, organizations, deals and — through the Import Inbox — documents such as shipment paperwork. People can narrow these for their own mailbox, never widen them.
  4. Add the companies and people you work with — customers, carriers, truckers, overseas agents — with their email addresses (or their email domain on the organization). PanLuma files mail from senders it recognises. Documents from a sender nobody recognises are held for someone to look at, never filed on their own.

Personal mailbox — Google Workspace or Microsoft 365

Each person does this for themselves.

  1. In PanLuma open Mail → Settings → My Mailbox and choose Connect beside Gmail or Microsoft 365.
  2. Sign in with your work account and accept the permissions (listed below).
  3. Back in PanLuma, turn on Sync my inbound mail. A consent screen lists what is picked up, what never is, and who else can see your mail. Nothing is read until you confirm.

PanLuma then checks your mailbox about every 10 minutes, and the first time it also reads a short window of recent mail.

What your account is asked to allow

  • Google: read your mail (gmail.readonly) and send mail as you (gmail.send), plus Google Drive, Docs, Sheets and Calendar access that PanLuma’s other features use. PanLuma’s Google app is verified by Google for these permissions and holds a current CASA Tier 2 security assessment. Disconnecting Gmail in PanLuma removes the whole Google connection, Drive and Calendar included.
  • Microsoft 365: read your mail (Mail.Read) and send as you (Mail.Send), read and change your calendar and OneDrive files (Calendars.ReadWrite, Files.ReadWrite), and stay signed in (User.Read, offline_access). PanLuma never asks for Mail.ReadWrite on your own mailbox: it never marks, moves, labels or deletes your mail. PanLuma is a Microsoft verified publisher, so the sign-in page names PanLuma Inc with a blue verified badge.

If the sign-in page says you need an administrator’s approval, your company restricts which apps people may use. In Microsoft 365 this is the usual case: Microsoft’s default settings do not let an employee approve mail or calendar access for any outside app, so an administrator approves PanLuma once, for everyone, before the first person connects. (Only if your company has changed that setting to let people approve apps from verified publishers can an employee connect without an administrator.) Ask your administrator to allow PanLuma:

  • Google Workspace admin: Admin console → Security → Access and data control → API controls → Manage third-party app access → find PanLuma → Trusted (for everyone, or for the team that uses PanLuma).
  • Microsoft 365 admin: use the approval link PanLuma shows. When Microsoft stops someone with “Need admin approval”, PanLuma’s screen hands them the link to send you; a PanLuma admin of Mail can also get it ahead of time under Mail → Settings → Tenant → Approve PanLuma for your Microsoft 365. Open it signed in as a Global or Cloud Application administrator and choose Accept: Microsoft lists the permissions PanLuma asks for, PanLuma is approved once, for everyone, and every employee can connect without asking again. The Grant admin consent button under Entra admin center → Enterprise applications → PanLuma → Permissions is not enough on its own: it approves only the permissions PanLuma’s registration lists in advance (signing in), not the mail, calendar and file permissions PanLuma asks for when someone connects, so employees are still stopped. If your organisation has turned on the admin consent workflow, an employee’s Request approval lands under Enterprise applications → Admin consent requests instead; without it, Microsoft offers the employee no button at all, only the message to ask an administrator.

If Microsoft asks for more information before it signs you in, your organisation requires multi-factor sign-in (Microsoft’s security defaults do, for every new account): set up the Microsoft Authenticator app when asked, then continue. This happens once, on the account’s first sign-in.

If PanLuma shows “Invalid authentication token” when you come back from signing in, the sign-in took longer than ten minutes — usually because a brand-new account was asked to change its password first. Choose Connect again; the second sign-in is quick.

Shared mailbox — Google Workspace

In Google Workspace a “shared mailbox” such as bookings@yourcompany.com is an ordinary account that several people use. PanLuma signs in with that account’s own login, so it reads that mailbox and nothing else, and no employee’s own account is involved. PanLuma does record who connected it: if that person leaves your PanLuma workspace, PanLuma stops reading the mailbox and asks the module’s admins to choose who signs in next.

  1. A PanLuma admin of the module (for freight: Freight Operations): Mail → Settings → Shared mailboxes → Connect a shared mailbox. Enter the address, a display name, Google Workspace, the module its documents go to, your company, who connects it, and who else may read it.
  2. The connector — whoever holds the mailbox’s password — opens the same tab, chooses Connect, and signs in as the shared mailbox, not as themselves. PanLuma refuses a sign-in whose address is not the mailbox’s.
  3. The mailbox shows Connected.

A Google Group or collaborative inbox has no mailbox to sign in to — use forwarding.

PanLuma does not offer Google’s domain-wide delegation: Google cannot limit it to one mailbox, so it would hand PanLuma every mailbox in your domain.

Shared mailbox — Microsoft 365

There are two ways. Choose “Your admin grants access to this mailbox only” unless nobody can run PowerShell.

No person signs in for the mailbox, so it keeps working when people leave. Exchange limits PanLuma to this one address, and PanLuma checks that before it connects.

  1. A PanLuma admin of the module: Shared mailboxes → Connect a shared mailbox, provider Microsoft 365, “How PanLuma opens it” → Your admin grants access to this mailbox only. Save, then choose Set up access. PanLuma shows the exact commands for your mailbox, with its address and PanLuma’s application ID filled in.

  2. Your administrator runs them in PowerShell — a Global administrator, or an Application administrator for the first block (Microsoft Graph) and an Exchange administrator for the rest. They need two Microsoft modules, once per computer:

    Install-Module Microsoft.Graph.Applications -Scope CurrentUser
    Install-Module ExchangeOnlineManagement -Scope CurrentUser

    On a new or small Microsoft 365, Exchange first refuses the scope commands with “The command you tried to run isn’t currently allowed in your organization … first run Enable-OrganizationCustomization”. Run Enable-OrganizationCustomization once, after Connect-ExchangeOnline; Microsoft can take several hours (up to a day) to apply it, after which the commands run.

    If someone at your company has already connected a Microsoft 365 mailbox to PanLuma, PanLuma’s application is already in your directory (Entra admin center → Enterprise applications → PanLuma); the script finds it and does not create it again.

    The commands then:

    1. add PanLuma’s application to your Microsoft 365 if it is not there yet (Connect-MgGraph, New-MgServicePrincipal);
    2. register it with Exchange Online (Connect-ExchangeOnline, New-ServicePrincipal);
    3. create a management scope that matches only this address (New-ManagementScope);
    4. grant “Application Mail.ReadWrite” and “Application Mail.Send” inside that scope only (New-ManagementRoleAssignment … -CustomResourceScope).

    Connecting a second shared mailbox later, New-ServicePrincipal reports that PanLuma is already registered. That is expected — run the remaining commands.

  3. Wait. Exchange can take up to two hours to apply new access.

  4. Back in PanLuma, choose Verify with Microsoft and sign in with a Global or Exchange administrator account of the same Microsoft 365 that has a mailbox of its own (PanLuma proves the grant is limited by checking it cannot open the administrator’s own mailbox, so an account without a mailbox cannot verify). This sign-in only tells PanLuma who you are; nothing from it is stored. PanLuma then checks that it can open this mailbox and cannot open yours.

If verification fails, PanLuma says why: the access is not applied yet (wait and try again), the person signing in is not an administrator, the mailbox belongs to a different Microsoft 365, the grant is not limited to this one mailbox, or the mailbox is already connected to another PanLuma workspace.

PanLuma’s application never needs an organisation-wide mail permission in Entra. If one has been granted, remove it: it would let the application read every mailbox, and PanLuma refuses to connect while it exists.

B. Someone signs in for it

The connector signs in with their own Microsoft 365 account, which Exchange already grants Full Access on the shared mailbox (and Send As, to reply from it). PanLuma asks for Mail.ReadWrite.Shared and Mail.Send.Shared. Exchange can take up to an hour to apply a new Full Access grant; until then PanLuma says the account can’t open this shared mailbox — wait, then choose Connect again. If that person leaves, PanLuma stops reading the mailbox and asks the module’s admins to choose a new connector.

Fallback — forward to your General Inbox

Every PanLuma user has a General Inbox address, shown under Settings → Email Addresses and on the Shared mailboxes tab — for example inbox.ana.3f9c2a@mail.panluma.ai. Mail forwarded there goes through the same intake.

  • Gmail: Settings → Forwarding and POP/IMAP → Add a forwarding address. Google first sends a confirmation message to that address, which arrives in that person’s PanLuma Mail. A Workspace administrator can instead add the address as an extra recipient under Admin console → Apps → Gmail → Routing, which needs no confirmation.

  • Microsoft 365: Outlook → Settings → Mail → Rules → Redirect to (or a mail-flow rule your administrator sets). Use Redirect, not Forward: a redirected message keeps its original sender, which is how PanLuma recognises the customer or carrier; a forwarded one comes from the mailbox itself. Microsoft 365 blocks automatic forwarding to outside addresses by default, in two separate places, and your administrator must open both — otherwise the redirected copy is dropped without any bounce, and nothing tells the sender or you:

    1. Microsoft Defender → Policies → Anti-spam → Outbound policy → Automatic forwarding rules → On, for this mailbox or its group.
    2. Exchange admin center → Mail flow → Remote domains → Add a remote domain for mail.panluma.ai only, with Allow automatic forwarding ticked. Leave the Default remote domain as it is, so forwarding stays closed to every other outside address.

    The mailbox doing the redirecting must be one of yours: a PanLuma user’s own work address (not an Outlook.com or Hotmail address), or an address on a domain your administrator has verified under Email Settings → Sending domains (for a shared mailbox such as bookings@). Microsoft’s redirect breaks the original sender’s signature, so PanLuma instead checks the sealed record Microsoft adds when it redirects — and that record only proves the sender when the redirect came from your own mailbox. Mail redirected from any other mailbox is still shown in Mail, but its documents are not read; when its sender is one of your users or a customer, vendor or partner you have added, it is marked sender not verified so you can see why.

PanLuma acts on forwarded mail only when it can tell who sent it: one of your own users, or a customer, vendor or partner you have added. From anyone else the message is still delivered, but its documents are held unread until one of your people releases or discards them.

What PanLuma reads, and what it never reads

  • Nothing until both switches are on. A person’s own mailbox is read only when your workspace allows it and that person turns sync on.
  • Headers first. For each message PanLuma first reads only its headers and the short preview your mail provider gives. Mail only between colleagues, newsletters without an attachment, and mail with a sensitive subject (medical, salary, a job offer…) is declined right there — its body and attachments are never downloaded or stored.
  • Unknown senders. For a message with no attachment from a sender nobody at your company knows, an AI model reads only that short preview to decide whether to show it to the mailbox owner. This is on by default; an administrator can turn it off (Mail → Settings → Policy → Screen unknown senders’ mail with AI), and then such mail is not picked up. Documents from unknown senders are always held unread for a person to release.
  • Your rules win. “Never” rules (a sender, a domain, a label or folder) apply before anything else. Put the label PanLuma: private (your administrator can rename it) on a Gmail thread, or that category on an Outlook message, and it is never read. Mail you mark Not business — forget it is deleted and its sender is not read again.
  • Private by default. Mail from a person’s own mailbox is visible only to that person — not to colleagues, and not to your PanLuma administrators — until it is filed on a record others can open (a job, an order, a deal) because it plainly belongs there (it replies to mail your team sent, or cites one of your job or document numbers), or the person shares it.
  • Shared mailboxes are shared. Mail in a team mailbox is visible to the people on its access list, and its documents go to its module’s team.
  • PanLuma does not change your mailbox. It does not mark mail read, move it, label it or delete it there. It sends only when one of your people sends a reply from PanLuma.
  • Disconnecting stops reading at once. Disconnect on the same settings tab, or remove PanLuma from your Google account or Microsoft 365 at any time.

After connecting: what to expect

  • A booking request from a customer becomes a proposed draft job in the Import Inbox, with the customer, places, cargo and dates read from the email for you to check.
  • Carrier booking confirmations, SLIs, proofs of delivery and arrival notices are matched to the job they name — by our job number, the carrier booking number, a container or bill of lading number — and filed in its Documents tab, ticking its document checklist. When PanLuma is not sure which job, it asks rather than guessing.
  • Nothing is applied on its own at first. For each kind of message, once your team has approved enough drafts without needing to correct them, an administrator may let PanLuma apply that kind automatically.