Smart Banners asks your Microsoft 365 or Google Workspace tenant for the access it needs to read each incoming email and add the banner to it. This page lists every permission or scope, what it lets Smart Banners do and why, for the administrator who grants or reviews them.
How to grant, check, limit and revoke them: Setup › Step 2 — API Access Setup. On Google Workspace, the real check is Setup › Step 3 — Test Deployment. Offboarding: Setup › Turning it off and offboarding.
What does Smart Banners request?
-
Microsoft 365: two application permissions,
Mail.ReadWriteandUser.Read.All, for the application LibraCyber Banners. -
Google Workspace: five Gmail scopes for the Smart Banners service account, by domain-wide delegation:
gmail.readonly,gmail.insert,gmail.modify,gmail.labelsandgmail.settings.basic. - Test and sample emails of the setup: when your company uses API delivery, they use a separate delivery access, shared with the rest of the platform.
Each permission, what it lets Smart Banners do and why it is needed, by provider:
Microsoft 365
Application LibraCyber Banners, consent Grant Email Process Consent to LibraCyber
-
Mail.ReadWrite(application): lets Smart Banners read the emails in your users' mailboxes, including the full body and the attachments, and modify them. Needed to analyse each incoming email and write the banner at the top of it. Smart Banners also moves a bannered email into a hidden folder and straight back, so that Outlook displays the updated version. -
User.Read.All(application): lets Smart Banners read the profile of the users of your tenant. Needed to identify the user each mailbox belongs to.
Application LibraCyber Mailer, consent Grant Direct Message Injection Consent to LibraCyber (shared with the rest of the platform)
-
Mail.ReadWrite(application) ·User.Read(delegated): lets the platform place emails directly in your users' mailboxes. Needed to deliver the test email and the sample emails of the setup when your company uses API delivery. The same consent delivers the other platform emails, such as phishing simulations.
Google Workspace
Smart Banners service account, domain-wide delegation
-
gmail.readonly: lets Smart Banners read the content of emails. Needed to analyse each incoming email. -
gmail.insert: lets Smart Banners add an email to a mailbox. Needed because Gmail does not allow an existing email to be changed. Smart Banners therefore adds a copy of each analysed email to the mailbox, carrying the banner when there is one. -
gmail.modify: lets Smart Banners move emails between the Inbox, labels and the Trash. Needed to keep a new email out of the Inbox while it is analysed, and put it back in the Inbox afterwards. It also moves the original of a bannered email to the Trash once its bannered copy is in place. -
gmail.labels: lets Smart Banners create labels in the mailbox. Needed to create the labels Mantra, Mantra/Processing (emails being analysed) and Mantra/Reviewed (emails already analysed), plus a hidden label for emails from outside senders. -
gmail.settings.basic: lets Smart Banners create and delete mail filters. Needed to create the filter that places new incoming emails under Mantra/Processing until they are analysed. The filter is renewed every few minutes and removed when Smart Banners is turned off for the mailbox.
The platform's mail delivery account (shared with the rest of the platform)
-
gmail.insert: lets the platform add an email to a mailbox. Needed to deliver the test email and the sample emails of the setup when your company uses API delivery. The same account delivers the other platform emails, such as phishing simulations: revoking it stops all of them.