Configure calibration notifications

The organisation notification policy controls which calibration reminders Obsidian Metra creates and which available channels it uses. Notifications are reminders of the current calibration schedule; they do not calculate or change requirement due status.

Prerequisites

• Select the organisation whose policy you want to change.
• Ensure sites have the correct timezone and active requirements have accurate due dates.
• Assign responsible members to requirements where individual ownership is expected.
• Have notification policy management permission. Organisation owners, organisation administrators, and quality managers normally have this permission.
• If email will be enabled, confirm that email delivery has been configured for the deployment and that intended recipients have usable account email addresses.

Open the organisation policy

1. Open Notifications for the selected organisation.
2. Select Notification settings.
3. Review the policy and the displayed email availability state.

Each organisation has one versioned policy. Saving a change creates an audited update and advances its version. If another manager changes the policy while you have it open, your save may be rejected to prevent their update being overwritten. Reload the settings, review the newer values, and apply your change again.

Choose reminder types

The policy can enable or disable notifications as a whole and can control these reminder types:

1. Use the main notification switch to control whether new reminder occurrences are created.
2. Enable or disable due-soon reminders.
3. Enable or disable due-today reminders.
4. Enable or disable overdue reminders.
5. Set the overdue repeat interval from 1 to 90 days.
6. Set the site-local evaluation hour from 0 to 23.

Disabling notifications or one reminder type prevents new occurrences under that setting. It does not remove existing notification or delivery history.

Suspended, retired, and archived requirements do not generate new due reminders. Changing a requirement's next due date starts a new due-date episode; it does not rewrite notifications already created for the earlier date.

Choose channels

The policy controls the organisation's available reminder channels:

• In-app creates durable items in each recipient's notification centre.
• Email requests transactional email delivery when email transport is configured and available.

Keep in-app notifications enabled when members should have a retained reminder history inside Obsidian Metra. Email can be enabled only as an additional channel; email failure or unavailability does not change requirement state or prevent in-app notifications from being used.

Enabling email does not guarantee receipt. Delivery can be affected by deployment configuration, recipient account data, mail-provider processing, spam filtering, mailbox rules, or temporary failures. Use the Dashboard and notification centre as operational sources alongside email.

Email presentation is controlled by the deployment's approved notification template. The organisation, equipment, requirement, due date, due state, site timezone, and destination link still come from the reminder's delivery snapshot; changing the template cannot change those records or their status.

Understand recipients

Recipients are resolved when a reminder is created:

• The active responsible organisation member assigned to the requirement receives its reminders when they can read calibration requirements.
• Active members with notification oversight permission receive reminders for unassigned requirements and overdue work when they can also read calibration requirements.

Invited, suspended, revoked, or otherwise inactive memberships do not receive new reminders. A user who belongs to several organisations receives separate notifications under each organisation membership.

Assigning a responsible member after a reminder episode has begun may produce the current actionable reminder for that person. It does not replay every historical reminder they missed.

Set the evaluation time

The evaluation hour is interpreted separately in each equipment site's timezone. After that local hour is reached, the scheduled notification process can evaluate the site's active requirements for that local calendar date.

The setting is not an exact delivery appointment. Actual appearance and email timing also depend on when the scheduled notification process next runs and whether a channel needs another delivery attempt. Daylight-saving changes and sites in different timezones can therefore produce different UTC processing times while retaining the intended site-local evaluation hour.

Save the policy

1. Review the main switch, reminder types, channels, repeat interval, and evaluation hour.
2. Select Save notification policy.
3. Confirm that the updated settings are displayed.

Expected result

Future reminder evaluations use the new version of the organisation policy. Existing in-app notifications, read states, and delivery history remain unchanged.

Permission caveats

Policy management is separate from permission to read personal notifications. A manager may be able to configure the policy without being able to inspect another member's notifications or delivery details. The Metra enforces the organisation boundary, exact effective permission, current policy version, and allowed field ranges.

Next steps

• Use the notification centre
• Troubleshoot calibration notifications
• Create a calibration requirement
• Calibration work overview