Connects to the tools your organization already uses
Bantusign works with your existing directory, identity and HR infrastructure, not around it.
The Gmail API writes each employee's signature into their Gmail settings, used on new messages in Gmail on the web. Needs domain-wide delegation granted by a Google super admin. Directory sync of users and groups is included.
Inserts your approved signature when someone starts a new message. Verified on Outlook on the web, and built for new Outlook and Windows and Mac desktop and mobile where Microsoft's add-in platform supports automatic insertion. Installed by an admin. Registered shared mailboxes get their own signature when someone sends from them, and never use a seat; with the Exchange connection (Growth and above) Bantusign also lists the shared mailboxes Exchange Online reports, read only, and registers nothing until you add it.
An Exchange transport rule appends your signature to outbound mail from your organization, whatever device sent it. Setup is guided: a Microsoft admin approves access and assigns the Exchange Administrator role in Entra, then Bantusign checks and creates the rule. Bantusign re-checks it every 6 hours and repairs it. One HTML block: no photos, banners or tracked links, shown after sending and below the thread on replies.
Sync users, groups and attributes (title, department, phone, office and photo) from Entra ID on a schedule, hourly by default, and map groups to departments.
Sync titles, departments, phone numbers and photos from BambooHR on a schedule (hourly by default), so signatures follow your HR records.
Pull names, titles, departments and phone numbers from Workday HCM on a schedule. Workday photos are not available.
Sync employee records (names, titles, departments and phone numbers) from your ServiceNow instance on a schedule.
Import any HR export as a CSV file, or add and edit people by hand.
Sign in with SAML 2.0 or OpenID Connect through your identity provider, with domain verification, optional enforcement and a way back in. People must already exist in Bantusign.
Create API keys, with optional expiry, and read users, signatures and templates over a read-only REST API.
Send signed events, such as a signature drifting, a deployment failing or a directory sync failing, to an https endpoint you choose. An admin sets it up in Settings, with a test button and a delivery log, and you can pause and resume deliveries.
SCIM 2.0 user provisioning and deprovisioning (users, not groups) from Okta, Microsoft Entra ID or any SCIM-compliant identity provider.
Today the Gmail add-on is a compose-window command that each person installs. Installing it for your whole organization through the Google Workspace Marketplace is coming soon.
Connect Salesforce, HubSpot or Microsoft Dynamics 365 to bring contact records into Bantusign.
Ready to get started?