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
| Setting | Description |
|---|---|
| Company logo | Upload a logo displayed in email headers (JPG, JPEG, or PNG, up to 5 MB) |
| Brand color | Set a primary color for headers and visual elements, either through the color picker or a hex code |
| Email header | Customize the top section of notification emails using a block-based editor |
| Email footer | Customize the bottom section of notification emails using a block-based editor |
| Footer items | Turn on or off individual footer links and add URLs (see below) |
Footer items available:
| Item | Description |
|---|---|
| Privacy Policy | Link to your organization's privacy policy |
| Terms and Conditions | Link to your terms of service |
| Copyright | Copyright text displayed in the footer |
| Link to your organization's LinkedIn page | |
| Link to your organization's Twitter profile | |
| Link to your organization's Facebook page | |
| Support Email | Support contact email address |
| Support Portal | Link to your support portal |
Sender identity
| Setting | Description |
|---|---|
| Sender name | Display name shown in the email "From" field |
| Sender email | Email address used to send notifications |
| Reply-to email | Address used for responses |
| Domain verification | Validate the sender domain through DNS to improve deliverability |
Notification templates
| Element | Description |
|---|---|
| Subject line | Define how the email appears in the inbox, with support for dynamic tokens |
| Email body | Edit content using a block-based editor with Text, Heading, Divider, and Spacer blocks |
| Placeholders | Insert dynamic values such as {{task_id}}, {{app_name}}, or {{user_name}} by typing {{ |
| Styles | Adjust margin, typography, color, text alignment, and background color for any block |
| Test notification | Send a test email to your inbox before saving changes |
Delivery settings
Control how notifications are delivered to users.
Channels:
- Slack
Step 1: Open notification settings
- Go to Settings → Notifications
- 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
- Select a notification from the Notification Library
- Use the toggle at the top right to turn the notification on or off
- Under Channels, select the delivery channels (Email, Slack)
- Under Email Settings, enter the subject line. Type
{{to insert dynamic tokens - Click the more options (⋮) icon to view additional actions such as reset
Step 3: Edit notification template
- Click Edit Template next to the Email channel
- 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
- Select a block on the canvas to update its properties
- Click Styles to adjust:
- Margin
- Typography (font family, font size)
- Color
- Text align
- Background color
- Click Send test notification to preview changes in your inbox
- Click Save
Step 4: Reset notification
- Open the notification from the Notification Library
- Click the more options (⋮) icon at the top right
- Click Reset to Default
- 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.
- Click Reset Settings to confirm
Step 5: Configure branding
- Go to Settings → Notifications → Branding
- 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
- Click Configure under Email Header or Email Footer
- Add or update blocks on the canvas
- Use the Blocks and Styles panels to adjust content and formatting
- Click Save
Configure footer items
- Under Footer Items, turn on the items you want to show in the email footer
- Click the edit icon next to an item to add or update its URL
- Click Save in the URL dialog
- Click Save at the top right to publish branding changes
Step 6: Configure sender identity
- Go to Settings → Notifications → Email Configuration
- Click Configure
- 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
- Under Trusted Domains, locate the domain you want to verify
- Click View DNS to open the domain authentication modal
- Add the DNS records shown in the modal at your domain provider (see below)
- Click Verify
- 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:
| Type | Purpose | Host | Value |
|---|---|---|---|
| CNAME | Tracking / link branding — makes links in emails appear to come from your domain instead of SendGrid | em3215.acme.com | u19795698.wl199.sendgrid.net |
| CNAME | DKIM record 1 | s1._domainkey.acme.com | s1.domainkey.u19795698.wl199.sendgrid.net |
| CNAME | DKIM record 2 | s2._domainkey.acme.com | s2.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
- DNS propagates across the internet. This typically takes 24 to 48 hours.
- Click Verify in the modal.
- The system checks the DNS records and confirms domain ownership.
- 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:
| State | Meaning |
|---|---|
| In-progress | Verification has been initiated but not yet completed. DNS records may still be propagating. |
| Verified | The system has confirmed domain ownership. The domain is active for sending. |
| Failed | Verification 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
| Scenario | Configuration | Outcome |
|---|---|---|
| Access review notifications | custom domain and template | notifications are recognized and acted on |
| Budget alerts | targeted notification setup | relevant users receive alerts |
| Employee onboarding emails | branded templates and sender identity | notifications appear as internal communication |
| Workflow notifications | customized subject and content | clearer communication |
Error handling
| Scenario | What the user sees |
|---|---|
| Invalid logo format or file size | Validation error with supported formats (JPG, JPEG, PNG) and size limits |
| Domain verification fails | Error message indicating verification failed with option to retry |
| Empty subject or email body | Save or publish is blocked; missing fields are highlighted |
| Channel not configured | Channel option is disabled with a message to contact the admin |
| Unauthorized action | Action is blocked |
| Malformed token syntax | Zluri flags the syntax error. Token names are not validated against a supported list. |
| Reset to default | Configuration is restored to default; this action cannot be undone |
Permissions and access control
| Role | Access | Notes |
|---|---|---|
| Owner / Admin (with permission) | Yes - full access | Can create, edit, and publish all settings |
| End user / Employee | Personal preferences only | Within admin-defined limits |
| Unauthorized role | No | Action 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
Updated 44 minutes ago
