Since Notifuse 34, your team can sign in with single sign-on, through OpenID Connect and the identity provider you already use, such as Google Workspace, Okta, Microsoft Entra ID or Keycloak. Since Notifuse 41, audit logs show who did what in a workspace: who invited a member, created an API key, edited an integration or scheduled a broadcast, from which address, and whether it was allowed.

Single sign-on

When SSO is on, the sign-in page shows a Sign in with SSO button under the email form. The button sends the person to your identity provider, which applies its MFA and policies, and brings them back signed in. Login codes by email keep working. SSO is a second way into the same account, so nobody is locked out when the provider is down.

Setup

SSO is switched on for the whole deployment, not per workspace. Set the OIDC_* environment variables (OIDC_ENABLED, OIDC_ISSUER_URL, OIDC_CLIENT_ID, OIDC_CLIENT_SECRET), fill in the SSO step of the setup wizard, or open System Settings from the workspace list as the root user. The client secret is stored encrypted. At your provider, register /api/user.oidc.callback on your Notifuse domain as the redirect URI.

Some providers, Microsoft Entra ID among them, never send the email_verified claim. For those, set OIDC_ALLOW_UNVERIFIED_EMAIL=true. A claim that says false is always refused.

Who gets in

By default, SSO only signs in people who already have a Notifuse account or have an invitation waiting. Their first SSO sign-in links the account to the provider's identity, on a verified address. After that, Notifuse recognises them by the provider's issuer and subject rather than by email, so a renamed address keeps the same account.

To create accounts on first sign-in instead, set OIDC_AUTO_CREATE_USERS=true with OIDC_ALLOWED_DOMAINS=yourcompany.com. Someone outside that list is told so on the sign-in page. A new account still sees no workspace until someone invites it, because signing in never grants access by itself.

Invitees

Someone you invite doesn't have to open the emailed link first. Their first SSO sign-in creates their account, in the default mode too and even outside OIDC_ALLOWED_DOMAINS, and the workspace list shows the invitation with a Join button. They only join when they click it.

This works only when the provider vouches for the address: email_verified set to true; from Google, only for a Gmail address or a Google Workspace account; from Entra ID, the optional xms_edov claim for a member of your tenant. OIDC_ALLOW_UNVERIFIED_EMAIL doesn't count here. Otherwise SSO creates no account for an invited address, even with auto-create on, and the invitee has to open the emailed link once. If that email got lost, Resend invitation in Settings → Team & API keys sends a fresh link for the same invitation.

Offboarding

When someone leaves and you disable them in your identity provider, SSO stops letting them in. They still have two ways in: a session already open lasts up to 30 days, and a login code still reaches their mailbox if it is active. Remove them in Settings → Team & API keys as well. Their next request to the workspace is then refused, and the audit log records who removed them.

Audit logs

Open Logs → Audit log in a workspace. Each entry reads as a sentence, such as "Invited ann@example.com", and says who acted (a person or an API key, with its email and name, or the system), what they did and to what, when, from which IP address and browser, and whether it ended in success, failure or denied.

What is recorded

  • Members: invitations, joins from the workspace list, removals and permission changes.

  • Access: API keys created, Zapier connected, integrations added, edited or removed, webhook subscriptions and their secrets.

  • Content: templates, broadcasts, automations, lists, segments, transactional notifications and the blog.

  • Contacts: deletions, imports and exports, but not everyday updates.

  • The workspace's settings.

A request refused by a permission check is recorded as denied, with the permission it lacked. Changes to permissions, integrations and settings carry a before and after, with passwords, secrets and keys shown as [redacted], so you see that the SMTP password changed but not the password itself. Sends, contact upserts, tracking and reads are not recorded.

Two lookups

To find who changed the welcome email, filter on the templates.update action and search for the template's ID. Each save shows who made it, when and from where.

To find out why sending stopped, filter on the integration actions. The last edit shows who made it and which fields changed, with the request ID the API returned in its X-Request-ID header.

Who sees it

Workspace owners always see it. A member or an API key needs the Audit Logs read permission, granted in Settings → Team & API keys. Full access doesn't include it, since reading colleagues' addresses and refused actions is a separate grant, though the members list still shows such a member as Full access, with the extra grant shown when you point at it.

A root user can set the tab's View to Whole deployment, which covers every workspace plus the licence, the system settings and the sign-ins, each sign-in saying whether it came by login code or SSO. Failed sign-ins are there too, with the reason the sign-in page doesn't give: an unknown address, or a wrong or expired code.

Export and retention

The tab filters by period, actor, resource, action and outcome, searches by actor email, target ID or IP address, keeps its filters in the link, and exports the current filter as CSV or NDJSON, up to 100,000 rows. Each export is recorded in the log too. A SIEM can pull the same entries with auditLogs.list.

Entries are kept 365 days by default. An owner sets the workspace's retention in Settings → Audit log: 0 keeps everything, otherwise 30 to 3650 days. A root user sets the deployment default in System Settings.

Append-only

Entries live in the system database, so deleting a workspace doesn't delete its history. A database trigger refuses every update, and every delete except the retention purge. The database owner can still disable that trigger, so keep a backup elsewhere if an auditor needs more.

Licence

Both features need an Enterprise licence key. Without one, the SSO button isn't shown and everyone signs in with a login code. Audit logs then record nothing, though the tab and the export stay available for what was recorded under a key.

Not yet

  • Only OpenID Connect is supported, with one identity provider per deployment and no SAML.

  • Nothing syncs from the provider. Disabling someone there doesn't remove their Notifuse account or end their sessions, and login codes can't be turned off for them.

  • Some invitees still need the link: when the provider doesn't vouch for an address, the invitee accepts the emailed invitation before SSO works for them.

  • With several API servers, sessions must be sticky, because an SSO sign-in has to end on the server that started it.

  • There is no content diff. For templates, broadcasts and automations, the log says who saved, not what changed.

Getting started

Create an OpenID Connect client at your provider and give its details to Notifuse. Then set the retention in Settings → Audit log. The single sign-on documentation covers Google Workspace and Keycloak, the audit logs documentation lists every recorded action, and the licence page shows how to install a key.