Setup has seven steps in Smart Banners › Setup, and only the first two are required. At the end, Smart Banners analyses the emails your users receive and adds a warning banner to the suspicious ones. You will have tested it on your own mailbox, checked which senders would trigger banners, and activated your users.
Who should run it?
An administrator of the LibraCyber console whose role includes the Smart Banners permission. They work with an administrator of your mail tenant, who grants the API access in Step 2: API Access Setup: a Global Administrator on Microsoft 365, a super administrator on Google Workspace.
How long does it take?
The setup itself has no waiting time once your mail tenant administrator is available. After you activate the first user, the first analysed emails usually arrive within about a minute on Microsoft 365, and within about ten minutes on Google Workspace. Rolling Smart Banners out to most of the company with Auto Engage typically takes about two weeks.
Two waits to plan for: the historical analysis (Step 4: Run historical analysis) takes several minutes, and Auto Engage (Step 7: Engage Company) starts activating users the next morning, then once a day.
What are the steps?
The Setup Checklist tab of Smart Banners › Setup proposes these steps, in this order. Steps 1 and 2 are required; the others are optional but recommended.
- Company Setup
- API Access Setup (A · Microsoft 365 / B · Google Workspace)
- Test Deployment
- Run historical analysis
- Define your safe lists
- Send sample emails
- Engage Company
The steps are the same for Microsoft 365 and Google Workspace, except step 2, which has two sub-flows: A · Microsoft 365 and B · Google Workspace.
Then: Rolling it out to users, Turning it off and offboarding and Setup troubleshooting.
What Smart Banners is, what the banners look like and what is not covered: Overview.
Prerequisites
You need Smart Banners activated by LibraCyber, a console role with the Smart Banners permission, and your users provisioned in the console. You also need an administrator of your mail tenant: a Global Administrator on Microsoft 365, a super administrator on Google Workspace.
Supported providers: Microsoft 365 and Google Workspace. Mail clients, mailboxes and emails that are not covered are listed in Overview › What is not covered.
| Requirement | Why it is needed | How to check it |
|---|---|---|
| Smart Banners activated for your company by LibraCyber | Until it is activated, every Smart Banners section shows a presentation page instead of the console | Open Smart Banners › Setup: you see the Setup Checklist tab, not the presentation page |
| A console administrator role that includes the Smart Banners permission | The Smart Banners menu (Dashboard, Users, Setup) and every action in it require this permission | The Smart Banners menu is visible. Roles and their permissions are set in General Settings › Admins |
| Your users provisioned in the console | Smart Banners can only protect the mailboxes of users known to the console. Synchronise the Microsoft 365 or Google Workspace groups that contain them in General Settings › Office Users Provisioning (or Google Users Provisioning), or import them by CSV | Your users are listed in Smart Banners › Users |
| Recommended: Enable daily user provisioning ticked on the same tab | New employees are then added to the console every night, and Auto Engage (Step 7: Engage Company) activates them the next day | The box is ticked in General Settings › Office Users Provisioning (or Google Users Provisioning) |
| Test and sample emails can reach your users (Step 3: Test Deployment and Step 6: Send sample emails) | They are delivered like every other email the platform sends your company, such as phishing simulations and notifications: by API or by SMTP. With SMTP, your mail filtering must let them through, as for phishing simulations | Your phishing simulation emails already reach your users' inboxes |
| A CEO in General Settings › Company Scan › Key People (only for the CEO scenario of Step 6: Send sample emails) | That sample email imitates your CEO | The CEO is filled in and linked to a provisioned email address |
Smart Banners not activated yet: every section shows this presentation page instead of the console
Microsoft 365
- A Global Administrator of your tenant. The consent of step 2A is a tenant-wide admin consent, and the console asks for a Global admin account. Check that the person who will grant the consent can sign in to the Microsoft Entra admin center as Global Administrator.
- Every mailbox to protect hosted in Exchange Online. Smart Banners works on cloud mailboxes. Users synchronised from an on-premises Active Directory to Microsoft Entra ID are supported, as long as their mailbox is in Exchange Online. A mailbox still on an on-premises Exchange server shows Access error once activated.
-
The Smart Banners consent granted before you open the checklist. Without it, Smart Banners › Setup shows Unable to load banner setup. See Step 2: API Access Setup › A · Microsoft 365.
Microsoft 365 without the Smart Banners consent: Unable to load banner setup, with the link to the provisioning settings
-
CSV import only: each user's Microsoft 365 user ID in the optional
external_idcolumn of the file. Without it, Smart Banners cannot find the user's mailbox. Check that no user shows Can't be activated with the reason Missing Microsoft 365 ID in Smart Banners › Users. - API delivery of test and sample emails needs Grant Direct Message Injection Consent to LibraCyber.
Google Workspace
- A super administrator of your Google Admin console. Step 2B authorises a service account through domain-wide delegation, which only a super administrator can configure. Check that the person who will follow Step 2: API Access Setup › B · Google Workspace can open Security › Access and data control › API controls in the Google Admin console.
Setup steps
Open Smart Banners › Setup and stay on the Setup Checklist tab. Select a step in the list on the left to open it. A tick shows that the step is complete, a red cross that it needs your action, an orange warning that something is missing.