---
title: Notifications
description: See what has happened on your site, and decide what you have read.
sidebar:
  order: 2
---

The Notifications screen lists what has happened on the site selected in the
sidebar, newest first. There are three kinds: somebody filled in a form on your
site, your site's files and its tables have
[stopped matching](#a-table-out-of-step), or one of your pages
[could not be shown](#a-page-that-could-not-be-shown) to a visitor. An
organization's owner is also
told here when a site is handed over to the organization or away from it, and
when the payment for its plan stops or the plan ends.

A form alert here is for any form other than the enquiry form every new site
starts with, and it links to that form's own table under Database. Alerts about
the enquiry form are not on this list at all: they sit on
[Enquiries](/dashboard/enquiries/), beside the message each one is about.

The number beside **Notifications** in the sidebar counts what you have not read
yet on this screen, and **Enquiries** carries its own count for the alerts that
live there. Either disappears when there is nothing, so neither is a zero you
have to dismiss.

## What read means {#read-means-you-saw-it}

Opening this screen marks nothing. Press the tick on an alert's row, or **Mark
all as read** above the list, which covers this list and not the alerts sitting
on Enquiries.

Marking a form alert read says you have seen it. It says nothing about the
message behind it: nothing here changes an enquiry, and deleting the message
on the Enquiries screen is still the only thing that removes one.

If your site has more than one person on it, each of you has your own list and
your own count. Reading an alert is yours alone.

## When a table and your site's files stop matching {#a-table-out-of-step}

Your site's files name the tables and fields they read. Your tables are files
of the site too, so a table and the pages that read it change on the same
branch, are checked together, and go live in the same merge. The two can
still stop matching after an update to Vizitka that reads your live files
more strictly than before. Your site's pages are then shown as they last
worked where that is possible; otherwise they do not open until the two match
again. Its forms cannot be sent either
way. Open your site to see which it is.

The alert says so, and what to ask your coding agent: to make the files and
the tables match again. The alert links to
[Database](/dashboard/database/), where you can see the table as it is now,
and to [Branches](/dashboard/branches/), where you merge a change to the
files to put it live.

The alert stays on this screen: there is no email and no Telegram message.
You are not told again while you hold it unread, and putting a change live
marks it read for every member.

## When a page cannot be shown {#a-page-that-could-not-be-shown}

A page of your site can fail to show for a visitor because of something in
your site's files or in the rows it reads. That visitor got an error instead
of the page. It can be one address that fails or the whole page, so open the
page yourself: if it fails for you too, it fails for everyone until it is
fixed. The rest of your site stays up.

The alert names the page and gives a short reference. Ask your coding agent
to look at that page, and pass the reference on. When the agent has changed
the files, merge the change on [Branches](/dashboard/branches/) to put it
live.

The first one also reaches your inbox, and Telegram if you
[get alerts there](#in-telegram), with the page's address, the reference and a
link to this screen. Nothing more about your site's pages is sent until you
read your alerts here or put a change live.
You are not told again about the same page and reference while you hold the
alert unread, and putting a change live marks it read for every member.

## One site at a time

Notifications follow the site selector at the top of the sidebar, like every
other screen here. If your account has two sites, switch between them to see
each one's alerts.

## An email as well

A form submission also reaches your inbox, one email per submission, sent as
soon as it arrives. If more than one person is on the site, each of you gets
your own copy.

The email names the site and the form, says when the message came in, and has
a button through to the screen where you read it. It does not quote what the
visitor wrote. The email links to your dashboard to read the visitor’s answers. Replies to it are not
read.

Of the rows on your site, only a visitor's submission is worth an email. A row
you add yourself under Database, or one a connected coding agent writes, tells
nobody.

If your account has no email address of its own, which happens when you signed
up with Telegram, or with an Instagram account that does not share one, there
is nowhere to write to and the email is skipped. The alert on this screen still
arrives, every time, and [Account](/dashboard/account/) says so on the row
where your address would be.

## In Telegram

Connect Telegram on [Account](/dashboard/account/) and allow messages to receive
form submissions there too. Every member chooses for themselves, without a separate approval from the owner. Alerts include
the site, form, time and the visitor's answers, with a dashboard link. Long
answers are shortened. A [page that could not be shown](#a-page-that-could-not-be-shown)
is sent there too. The messages are in English.

Turn alerts off on Account to stop them without losing Telegram sign-in. If a
message cannot reach you, Account asks you to reconnect. Deleting a submission
here does not delete messages already sent to Telegram; delete them there too.

## What does not arrive yet

Everything else worth telling you about (a domain going live, an Instagram
connection lapsing, storage filling up) is still to come, on this screen and
in your inbox both.