Settings & Help
Organization-level configuration and support resources.
Still have questions?
Can't find the answer you're looking for? Please chat to our friendly team.
Notification Preferences
Organization-wide notifications, delivered by email and/or in-app, that apply across CARO regardless of role.
Account & Security Alerts
New sign-ins, password changes and other account-security events.
Product Updates & Announcements
New features, planned maintenance windows and release notes.
Weekly Summary Digest
A weekly recap of your organization's Address Book and compliance activity. Email-only by nature - there isn't an in-app equivalent of a digest.
Feature notifications
Notifications that belong to a feature are set with that feature: Address Book › Event alerts and Compliance › Notification rules under Feature settings.
Notification rules
When CARO checks licenses in Legisym, when it alerts, how often it reminds partners, and who receives license notifications.
License checks
Automated Legisym checks for all active trading partners.
Default: daily. “Refresh license status” on a partner’s page runs the same check on demand. Every result is logged in the Audit Trail with its trigger (system or user).
License expiry alerts
Advance warning before a partner’s license expires, counted from the expiry date in Legisym.
Shown on the dashboard and sent with the next digest.
Renewal reminders
Recurring reminder to trading partners with an inactive or expired license, sent until the renewal shows in Legisym.
One interval for all renewal reminders. Legisym can’t tell an expired license from one whose renewal is already in progress, so a longer default avoids chasing partners unnecessarily. The same interval is the cooldown: an open item is reported again only when its status changes or the interval has passed.
Recipients & cadence
Who receives license notifications, and how often the email digest is sent.
Picked from each partner’s existing contacts.
For a distribution address, e.g. a licensing department, instead of a single person.
Pending legal review
Emailing your partners on your behalf needs an update to the terms (DPA) and an unsubscribe option. Until Legal signs off, this is shown as designed but not released.
Contact rules
How new contacts from any intake channel are added to the Address Book, and how VRS matches are handled.
Contact Confirmation
Applies to four intake channels: Trusted Partner Network (TPN), Secure Message pull-through, manual invites and XATP inbound requests. VRS interactions always add new contacts automatically; matches with existing contacts are handled below.
VRS Matches
When a VRS interaction belongs to a partner who is already in your Address Book from another channel (same DID or GLN), CARO does not create a second entry. Choose how the match is handled.
Why one setting for four channels
Trusted Partner Network, Secure Message pull-through, manual invites and XATP inbound requests all differ in how a contact is discovered — but the decision of whether that new contact needs a human look before it counts as part of your Address Book is the same decision either way, so it is kept as one setting rather than four. VRS is the exception: new VRS contacts are always added automatically, and only a match with an existing contact can need a confirmation (VRS Matches above).
Event alerts
Verification failures, duplicate merges and ATP status changes (CAR-774 to 777).
Ticket references
This section configures the three event types from the CARO-134 epic (CAR-774): Verification Failures (CAR-776), Duplicate Merge Events (CAR-775) and ATP Status Changes (CAR-777) - built alongside this ticket, CAR-893.
Verification Failures
Immediate alert when a credential or license check fails.
Individual failures still alert immediately (bell icon, top right) regardless of cadence. This only controls the rolled-up email summary sent to Recipients below.
Duplicate Merge Events
Notify when multiple identifiers (GLNs, licenses, credentials) are consolidated into one Address Book entry.
Merges are rarely urgent on their own, so this defaults to a weekly summary rather than daily - individual merges still alert immediately via the bell icon.
ATP Status Changes
Alert when an ATP moves between verification states (e.g. Unverified → Verified, or Revoked).
A Revoked transition always alerts immediately regardless of cadence, since it can block trading with that partner.
Cooldown
Keeps the email digests from repeating the same open item in every cycle.
An open item that has already been in a digest is left out of the following digests until the cooldown ends. If it is still open after that, it is included again. Applies to all three digests above. Immediate alerts (bell icon) are not affected. Default: 3 weeks.
Recipients
Who receives these three alert types, in addition to being shown in the bell icon (top right).
Why internal only
Unlike a license-expiry reminder, these three events are internal data-quality signals about your own Address Book and ATP records, not something a trading partner needs to act on - so, unlike the Notification rules (license expiry and renewal, tab Notification rules), there is no external partner-contact recipient option here.
Organization-level security configuration.
Third-party integrations for your organization.