Administrator guide
Emails and notifications
The ten emails Warde sends, what it leaves to your existing catalog notifications, and how to brand them.
Warde does not send its own emails about requests or approvals. Your instance's existing service catalog notifications describe a requested item and its approvals, and two emails for one request would be one too many. Warde sends ten emails of its own, for things the platform has no notification for.
All of them need outbound email switched on (glide.email.smtp.active). Guided Setup step 10 warns when it is off.
The emails Warde sends
Access reviews
| Notification | Subject | Sent to | When |
|---|---|---|---|
| Warde UAR: review assigned | Access review assigned to you: campaign | Each reviewer, once per campaign | A campaign starts, or a whole review is reassigned to them |
| Warde UAR: review reminder | Reminder: access review due for campaign | The reviewer | The days before the due date set in Guided Setup step 11 |
| Warde UAR: review escalated | Escalation: overdue access review for campaign | The reviewer's manager | The days after the due date set in Guided Setup step 11 |
Expiring access
| Notification | Subject | Sent to | When |
|---|---|---|---|
| Warde expiry: access due to expire | Some of your access is due to expire | The person, one email listing everything due | 14 days before (x_66256_warde.expiry.notify_holder_days; 0 turns it off) |
| Warde expiry: final warning before removal | Access is about to expire and will be removed | The person and their manager | 3 days before (x_66256_warde.expiry.notify_manager_days) |
Access bundles
| Notification | Subject | Sent to |
|---|---|---|
| Warde access bundle: items waiting for approval | Access bundle items waiting for your approval: bundle | Each entitlement owner asked to pre-approve |
| Warde access bundle: item rejected | An item in your access bundle was rejected: bundle | The bundle owner, and the administrators who review bundles if the owner is not one |
| Warde access bundle: item approved on a live bundle | An item was approved for your access bundle: bundle | The bundle owner, unless they approved it |
| Warde access bundle: people on an older version | Some people have an older version of bundle | The bundle owner, and the administrators who review bundles if the owner is not one |
| Warde access bundle: ready to activate | Your access bundle is ready to activate: bundle | The bundle owner, and the administrators who review bundles if the owner is not one |
Each is an ordinary notification under System Notification > Email > Notifications, so you can switch off any one of them.
What Warde writes for your own notifications
Because requesters and approvers hear about a request through your notifications, Warde writes what they need onto the records those notifications read:
- Approvers: a comment on the approval record headed Warde: before you approve, with important approval information, separation of duties findings and access being replaced. Add
${comments}to your approval notification, for example Requested item approval assigned, so the email carries it. - Requesters: comments on the requested item, such as the promised date, a refusal, or what finished and what did not. Your requested item notifications and the portal ticket page show them.
- Important information: to put a collection's important information in a requested item email, add
${sc_req_item.variables.important_information}to that notification.
Guided Setup step 10 checks whether any of your approval notifications quotes ${comments}.
Branding
In Guided Setup step 10, under The emails Warde sends:
| Setting | Property | What it does |
|---|---|---|
| Header | x_66256_warde.notifications.header_html | HTML placed at the top of every Warde email, such as your logo |
| Footer | x_66256_warde.notifications.footer_html | HTML placed at the bottom of every Warde email |
| Email styling | x_66256_warde.notifications.css | CSS for every Warde email. Restore the example puts the shipped styles back. |
Warde's email markup uses fixed class names for your CSS to target: .warde-email, .warde-table, .warde-th, .warde-td, .warde-link, .warde-panel and .warde-panel-heading.
Preview this email shows any of the ten emails with example records in the page. Nothing is sent.
Links in emails
Links in Warde's emails open My Access in the portal named in Reviews open in (Guided Setup step 11, default esc). They are built from the instance's glide.servlet.uri. If that property is empty, Warde leaves the links out and logs a warning.