Notifications Customization

Overview

Zluri allows users to customize notification templates, branding, and sender identity.

By default, system-generated notifications may appear generic or originate from external sender domains. Customization ensures notifications are recognizable and aligned with the organization's communication standards.

What this feature enables

  • Custom templates: define subject lines and email content for each existing notification. New notifications cannot be created, customization applies only to the notifications available in the Notification Library.
  • Custom sender identity: send emails from the organization's domain
  • Branded emails: apply logo, colors, header, and footer to all notifications
  • Controlled delivery: manage how notifications are sent across available channels

Why customize notifications

Organizations may face:

  • low engagement due to unfamiliar sender domains
  • emails marked as spam
  • inconsistent branding across communications
  • notification fatigue from high-volume alerts

Customization helps:

  • improve recognition and trust in notifications
  • align notifications with internal branding policies
  • improve response to workflow actions

What can be configured

Branding

SettingDescription
Company logoUpload a logo displayed in email headers (JPG, JPEG, or PNG, up to 5 MB)
Brand colorSet a primary color for headers and visual elements, either through the color picker or a hex code
Email headerCustomize the top section of notification emails using a block-based editor
Email footerCustomize the bottom section of notification emails using a block-based editor
Footer itemsTurn on or off individual footer links and add URLs (see below)

Footer items available:

ItemDescription
Privacy PolicyLink to your organization's privacy policy
Terms and ConditionsLink to your terms of service
CopyrightCopyright text displayed in the footer
LinkedInLink to your organization's LinkedIn page
TwitterLink to your organization's Twitter profile
FacebookLink to your organization's Facebook page
Support EmailSupport contact email address
Support PortalLink to your support portal

Sender identity

SettingDescription
Sender nameDisplay name shown in the email "From" field
Sender emailEmail address used to send notifications
Reply-to emailAddress used for responses
Domain verificationValidate the sender domain through DNS to improve deliverability

Notification templates

ElementDescription
Subject lineDefine how the email appears in the inbox, with support for dynamic tokens
Email bodyEdit content using a block-based editor with Text, Heading, Divider, and Spacer blocks
PlaceholdersInsert dynamic values such as {{task_id}}, {{app_name}}, or {{user_name}} by typing {{
StylesAdjust margin, typography, color, text alignment, and background color for any block
Test notificationSend a test email to your inbox before saving changes

Delivery settings

Control how notifications are delivered to users.

Channels:

  • Email
  • Slack

Step 1: Open notification settings

  1. Go to Settings → Notifications
  2. Click Manage Notifications under the Notification Library section

The Notification Library lists all notifications supported across modules, grouped by category (for example, Access Requests Approval Actions Updates, Access Reviews Admin Alerts and Updates). For the full list of notification categories and types, see Alerts & Notifications.

Step 2: Select a notification

  1. Select a notification from the Notification Library
  2. Use the toggle at the top right to turn the notification on or off
  3. Under Channels, select the delivery channels (Email, Slack)
  4. Under Email Settings, enter the subject line. Type {{ to insert dynamic tokens
  5. Click the more options (⋮) icon to view additional actions such as reset

Step 3: Edit notification template

  1. Click Edit Template next to the Email channel
  2. Add or update content using blocks from the right panel:
    • Text for paragraphs and body copy
    • Heading for titles and section headers
    • Divider to separate sections
    • Spacer to add vertical space
  3. Select a block on the canvas to update its properties
  4. Click Styles to adjust:
    • Margin
    • Typography (font family, font size)
    • Color
    • Text align
    • Background color
  5. Click Send test notification to preview changes in your inbox
  6. Click Save

Step 4: Reset notification

  1. Open the notification from the Notification Library
  2. Click the more options (⋮) icon at the top right
  3. Click Reset to Default
  4. Review the confirmation dialog. Reset restores all settings for the notification, including channels, recipients, delivery mode, reminder rules, and template customizations. This action cannot be undone.
  5. Click Reset Settings to confirm

Step 5: Configure branding

  1. Go to Settings → Notifications → Branding
  2. Click Configure

Update logo and color

  • Upload logo (JPG, JPEG, PNG, up to 5 MB)
  • Set brand color using the color picker or enter a hex code (for example, #9b63af)

Customize header and footer

  1. Click Configure under Email Header or Email Footer
  2. Add or update blocks on the canvas
  3. Use the Blocks and Styles panels to adjust content and formatting
  4. Click Save

Configure footer items

  1. Under Footer Items, turn on the items you want to show in the email footer
  2. Click the edit icon next to an item to add or update its URL
  3. Click Save in the URL dialog
  4. Click Save at the top right to publish branding changes

Step 6: Configure sender identity

  1. Go to Settings → Notifications → Email Configuration
  2. Click Configure
  3. Under Sender Identity, enter:
    • Sender name — the display name recipients see (for example, IT Team)
    • Sender email — the address notifications are sent from
    • Reply to email — the address where replies are directed
  4. Under Trusted Domains, locate the domain you want to verify
  5. Click View DNS to open the domain authentication modal
  6. Add the DNS records shown in the modal at your domain provider (see below)
  7. Click Verify
  8. Click Save

Domain authentication (DNS verification)

When a custom sender domain is configured (for example, acme.com), DNS authentication ensures emails sent from the platform are trusted and less likely to land in spam.

When you click View DNS, a modal opens with three CNAME records to add at your domain provider:

TypePurposeHostValue
CNAMETracking / link branding — makes links in emails appear to come from your domain instead of SendGridem3215.acme.comu19795698.wl199.sendgrid.net
CNAMEDKIM record 1s1._domainkey.acme.coms1.domainkey.u19795698.wl199.sendgrid.net
CNAMEDKIM record 2s2._domainkey.acme.coms2.domainkey.u19795698.wl199.sendgrid.net

The host and value shown above are examples. Use the values displayed in your modal, which are generated for your specific domain.

Why DNS verification is required

DNS verification enables:

  • DKIM authentication — proves emails are legitimately sent from your domain
  • Domain alignment — improves email deliverability
  • Spam reduction — helps avoid Gmail and Outlook flagging emails as spam

What happens after adding the records

  1. DNS propagates across the internet. This typically takes 24 to 48 hours.
  2. Click Verify in the modal.
  3. The system checks the DNS records and confirms domain ownership.
  4. Once verified, the domain is activated for sending.

Verification states

The domain can be in one of three states, shown in the Verification column of the Trusted Domains table:

StateMeaning
In-progressVerification has been initiated but not yet completed. DNS records may still be propagating.
VerifiedThe system has confirmed domain ownership. The domain is active for sending.
FailedVerification could not be completed. An error message appears: Domain verification failed. Check your DNS records. Review your DNS configuration and click Verify again.

Best practices

Branding

  • Use consistent logo and colors across all templates
  • Avoid overly complex designs that affect readability

Content

  • Keep messaging clear and action-oriented
  • Use recognizable subject lines (e.g., "Action Required: Access Review")

Sender Identity

  • Always configure a trusted domain to avoid spam filtering
  • Use recognizable sender names (e.g., "IT Team", "Security Team")

Example use cases

ScenarioConfigurationOutcome
Access review notificationscustom domain and templatenotifications are recognized and acted on
Budget alertstargeted notification setuprelevant users receive alerts
Employee onboarding emailsbranded templates and sender identitynotifications appear as internal communication
Workflow notificationscustomized subject and contentclearer communication

Error handling

ScenarioWhat the user sees
Invalid logo format or file sizeValidation error with supported formats (JPG, JPEG, PNG) and size limits
Domain verification failsError message indicating verification failed with option to retry
Empty subject or email bodySave or publish is blocked; missing fields are highlighted
Channel not configuredChannel option is disabled with a message to contact the admin
Unauthorized actionAction is blocked
Malformed token syntaxZluri flags the syntax error. Token names are not validated against a supported list.
Reset to defaultConfiguration is restored to default; this action cannot be undone

Permissions and access control

RoleAccessNotes
Owner / Admin (with permission)Yes - full accessCan create, edit, and publish all settings
End user / EmployeePersonal preferences onlyWithin admin-defined limits
Unauthorized roleNoAction blocked; RBAC violation alert shown

Key outcome

With notification customization:

  • Employees recognize and trust communications
  • Critical workflows (access reviews, approvals) see higher completion rates
  • Organizations maintain compliance and audit traceability