Reference translation
This page is a courtesy translation. The Spanish version is the authoritative reference.
Notifications
RegistroViajero keeps you informed about activity on your registrations and team. You're notified on all your devices: on each one, the system (push) notification appears only when you don't have the app open and in front of you on that device; if the app is in front of you, the alert shows in the bell instead. Your unread count stays in sync across devices.
Notification types
Registrations and guests
| Type | When it fires |
|---|---|
| Registration created | A new registration was created manually. |
| Guest completed check-in | A guest has finished every step and signed. |
| Guest re-opened their data | A guest has clicked Edit my information after completing — the registration goes back to Awaiting guests. |
Ministry
| Type | When it fires |
|---|---|
| Ministry confirmation | The Ministry has accepted the submission. |
| Ministry error | The Ministry has rejected the submission. |
| A submission to the Ministry needs review | A submission reached the Ministry but couldn't be fully recorded. Review it: the registration stays Sent to Ministry awaiting reconciliation. |
| SES credentials rejected | The Ministry stopped accepting a property's SES credentials. Update them in Settings before a submission fails. |
| Registration not sent | A guest report couldn't be sent because something still needs resolving (for example, the accommodation has no SES credential, or a guest hasn't signed). Open the registration: it shows exactly what is missing, with a link to fix it. See When a registration cannot be sent. |
Calendars (iCal)
| Type | When it fires |
|---|---|
| Booking removed from calendar | An unsent registration disappeared from the platform's calendar and was archived automatically. |
| Booking reactivated from calendar | A registration you had archived by hand reappeared in the calendar with different dates. RegistroViajero reactivates it with the new dates (Awaiting guests state) and keeps it linked to the calendar. |
| Calendar dates changed | The platform changed the dates of an already-imported registration. Review the stay before submitting. |
| Calendar sync failed | A calendar could not be read (URL expired, platform down…). The sync retries on its own. |
| Needs annulment | A registration already sent or confirmed with the Ministry disappeared from the calendar. It is not archived automatically: review it and, if the stay was cancelled, annul it (BAJA). |
Team
| Type | When it fires |
|---|---|
| New team member | Someone has accepted a team invitation. |
Exports
Only the person who requested the export gets these, not the whole team. The alert is individual, but the file is not: anyone in your agency can download it from Exports. See Exports.
| Type | When it fires |
|---|---|
| Export ready | The export you requested has finished and can be downloaded from Exports. |
| Export failed | The export could not be generated. Request it again; if it keeps failing, get in touch. |
Alerts that don't repeat
Some alerts describe a persistent situation that's re-checked periodically (for example, Calendar dates changed, Needs annulment or SES credentials rejected). To avoid flooding the bell, they're notified once while the situation lasts, not on every check. If the situation is resolved and later recurs (for example, credentials that get fixed and then fail again), the alert fires again.
Channels
Inside the app
Shown in the bell icon of the admin panel. Distinct events appear as separate entries; each one is marked as read individually or all at once with Mark all as read.
OS push
If you install the app on your device (see Install the app), you can receive operating-system push notifications when you don't have the app in front of you on that device. On iOS, push only works once the app is installed to the home screen.
Brave blocks push
Push notifications do not work in Brave because of its privacy restrictions. Use Chrome, Safari or Edge if you need push.
How delivery works
Alerts reach all your devices at once. On each device, the system only shows a pop-up notification when you don't have the app open and in front of you there; if you're using it, the alert appears in the bell, without duplicating the banner on the screen you're already looking at. So if you're working in the app on your computer, your phone still alerts you; and if your browser tab is in the background, you get a desktop notification. The unread count stays in sync across all your devices.
Alerts that don't pile up
A persistent event that recurs won't flood the bell with duplicates: if the same situation happens again on the same registration, the recent alert supersedes the previous one instead of adding a new entry (for example, when a guest who had re-opened their data signs again, the "is editing" alert disappears and only the completed-check-in one remains). Distinct events — such as several guests on the same registration signing — appear as separate entries.
There is a third case: alerts about a situation that remains unresolved — such as Registration not sent or Needs annulment — are raised once and stay until you resolve them, rather than repeating every morning. In the bell they are distinguishable because, instead of the alert's age, they read Unresolved. They clear themselves when the problem goes away: when the guest report is sent (by hand or automatically), or when you archive the registration or hand it back to the guest.
Preferences
In Settings → Preferences you can toggle each notification type independently. Disabling Guest completed check-in does not affect Guest re-opened their data or any other type. New types are enabled by default when introduced.
Each user manages their own preferences — they are not agency-wide.
Alerts tied to a legal deadline
Registration not sent and Needs annulment tell you a legal obligation is outstanding. You can silence them, but we ask you to confirm first: if you turn them off we stop warning you, and the deadline remains your responsibility.
Automatic cleanup
- Notifications are automatically deleted after 30 days.
- OS push subscriptions that have not been used for 90 days are removed from the server.
This cleanup runs in the background; no action is required.