Communications History

Esta página aún no está disponible en tu idioma.

MakerVera keeps a record of every notification your makerspace sends. You can see that record in three places:

Where	Who can see it	What it shows
Communications tab on a member’s profile	Admins who manage notification settings	Everything sent to that member, why a message failed, and what it said
Communications tab on your own profile	Every member	Everything your makerspace has sent to you, and what it said
Notification bell in the header	Every signed-in member	Your 5 most recent notifications, with a dot when something new arrives

Click any row on either Communications tab to open its details: the full message, who it went to, and, if it wasn’t delivered, what went wrong and how to fix it.

Viewing a member’s communications (admins)

Go to People → Users and click on the member.
Open the Communications tab.

Each row shows the notification’s name, the channel (Email, SMS, Push or Webhook), its status and when it was sent. The newest messages are at the top. Click Load more at the bottom to see older messages.

You only see this tab if your role can manage notification settings. You can only view members of your own makerspace. If you open a link to someone outside it, you’ll see a message that the member isn’t part of your makerspace.

Opening a message’s details (admins)

Click a row, or move to it with Tab and press Enter or Space, to open the details panel. On a phone, it opens as a full-screen sheet. The panel shows:

Field	What it tells you
Name and channel	Which notification this was, and whether it went by email, text or push.
Status	Sent, Failed, Suppressed or Deduplicated.
Sent	When it was sent, in your time zone.
Recipient	The email address or phone number it went to, as recorded at the time. Push notifications have no address, and older messages may show Not recorded.
What went wrong	For failed and suppressed messages: the cause, the fix, and who can fix it.
Message content	The exact message the member received. See Seeing what was sent.

Close the panel with the close button or Escape. Your place in the list is kept, so you can move straight to the next row.

Why a message wasn’t delivered

The What went wrong block explains the problem in plain language and says who can fix it:

Label	Who can fix it	Examples
You can fix this	You, as an admin	The template uses a variable that wasn’t provided; the member has no email address or phone number on file; the phone number is invalid; the email bounced.
The member can fix this	Only the member	They opted out of this kind of message, haven’t agreed to receive texts, marked an earlier email as spam, or have no device set up for push.
MakerVera support can fix this	Our support team	Email or texting isn’t set up for your makerspace, the sending account is paused, or the provider rejected the sending settings.

When the fix is yours, the block includes a button that takes you straight to it:

Open template editor opens the template that caused the problem, ready to edit. For a missing variable, the block names the variables the template expected.
Open member profile opens the member’s profile so you can check their contact details or correct their phone number. A member’s sign-in email address can’t be changed; see Your Sign-In Email for what to do when a member has a new address.

Seeing what was sent

The Message content section shows the message exactly as your makerspace sent it:

Email: the subject, plus the message in a preview. Switch between the HTML view (how it looked in the inbox) and the Text view (the plain-text version).
Text message (SMS): the full text.
Push notification: the title and the message.

The unsubscribe link at the bottom of an email is replaced with [unsubscribe link]. Every email gets its own link (it works for 90 days and turns off only that email’s type), and MakerVera doesn’t keep it.

Sometimes there’s a message instead of content:

Message	What it means
This message could not be built, so no content exists.	The template had a problem, so nothing was sent. The What went wrong block explains it.
This message was not sent, so no content exists.	The message was stopped before it was written, for example because the member opted out or an identical message had just gone out.
Content wasn’t saved for this message.	The message was sent before this feature was released, or its content was removed when the member’s account was deleted.
This message was very long, so only the beginning was saved.	Shown above the content when a very large message was cut short.

An announcement is saved once and shared by everyone who received it, so every recipient’s details show the same content.

The content shown is what your makerspace wrote. For emails sent from MakerVera’s address, members also saw a “Sent by Your Makerspace via MakerVera” line, and links to other websites went through a “You’re leaving MakerVera” page. Those changes aren’t shown here. See Email Content Rules.

Sensitive details

Some messages carry details that give access to something: a temporary password in an invitation, a gift card code, or a verification code. MakerVera never shows these in the message preview. They appear as ••••••, and a note lists what’s hidden, for example “Some details are hidden: Temporary password.”

Revealing sensitive details (admins)

Admins with the View sensitive message details permission see a Show sensitive details button on messages that have them.

Open the message’s details.
Click Show sensitive details.
The values appear in a separate Sensitive details list. The preview itself stays masked.
Click Hide when you’re done. The values also disappear when you close the panel or open another message.

Every reveal is recorded in the audit log, with who revealed what and when. The values themselves are never written to the log.

Some hidden items, such as password reset links and unsubscribe links, are never kept, because anyone holding them could act as the member. Those show the note “These stay hidden because they are not kept”, instead of a value.

Who can reveal them

By default, only the Admin role has View sensitive message details. You can give it to another role in role management, where it’s listed under Notifications. It works together with the permission to manage notification settings, so a role needs both.

This is a system permission: it can be added to roles only, never to designations. See User Roles.

Viewing your own communications (members)

Open your profile and choose the Communications tab. You’ll see the emails, texts and push notifications your makerspace has sent you, newest first. Click Load more to go further back.

If you haven’t received anything yet, the tab says No messages yet.

Opening your own messages

Click a message, or press Enter or Space on it, to open its details. You’ll see:

when it was sent and the address or phone number it went to (Sent to);
the full message, just as it was sent, for messages sent after this feature was released;
if it wasn’t delivered, Why it wasn’t delivered and what you can do about it.

When you can fix the problem yourself, the panel offers a button:

Button	Takes you to
Update your email address / Update your phone number	The Overview tab of your profile
Turn these emails back on / Turn on text messages	The Settings tab of your profile, where you manage your notification choices

For problems only your makerspace can fix, the panel suggests contacting your makerspace if it keeps happening.

Your own sensitive details

If one of your messages contained a temporary password, gift card code or verification code, you can click Show sensitive details to see it again. You don’t need any special permission for your own messages. Each reveal is recorded in the audit log.

The notification bell

Click the bell in the header to see your 5 most recent notifications, each with the date and time it was sent. Click a notification to open it: the Communications tab on your profile opens with that message’s details already showing. Close the details to see the rest of your messages. Click View all to open the Communications tab without opening a message.

An opened message keeps its place in the page address, so reloading the page, or opening the address in a new tab, opens the same message again. If a message can’t be shown to you, for example because it was removed, the panel says This message isn’t available.

The bell always shows your own notifications, even when you’re working in the admin area.

The unread dot

A small dot appears on the bell when something new has arrived since you last opened it. Opening the bell clears the dot. MakerVera checks for new notifications when a page loads and then every 5 minutes while the tab is open.

The dot is remembered in your browser, separately for each makerspace:

Opening the bell in one tab clears the dot in your other open tabs too.
A different browser or device keeps its own record, so the dot may still show there.
If your browser blocks site storage (for example, some private windows), the dot doesn’t appear at all.

There’s no unread count, and individual notifications aren’t marked as read.

What the statuses mean

Status	Meaning
Sent	The message was handed to the email, SMS or push provider.
Failed	The provider couldn’t deliver it. Open the details to see why.
Suppressed	The message wasn’t sent, usually because the member opted out or their address previously bounced. See Understanding Member Opt-Outs.
Deduplicated	An identical message had just been sent, so this copy was skipped. Only admins see these rows.

These are the same statuses you’ll see in the delivery log on the Analytics page.

Notification names

Each row shows the notification’s readable name, such as “Registration confirmed”. If your makerspace has customized a template, you’ll see your custom name. If a template has been renamed, older messages show the new name too. If no name can be found, the row shows the template’s internal key instead.

Announcements show their subject line, in the Communications tabs, the bell and the Analytics delivery log. Announcements sent before this was released show Announcement instead. Long names are shortened. Hover over one, or move to it with the keyboard, to see the full name.

Troubleshooting

A member says they never got an email, but it shows as Sent.

Open the message’s details and check the Recipient address is the one they expect.
Look at the Message content to confirm what was sent.
Ask them to check their spam or junk folder.
If it keeps happening, check Admin → Communications → Analytics for delivery issues on their address.

A message failed with “Template variable missing”.

Open the message’s details. What went wrong names the variables the template expected.
Click Open template editor and remove or rename those variables.
Preview the template before it’s sent again.

A message failed with “Custom HTML blocked”.

The announcement had custom HTML, but when it was sent your makerspace was no longer sending from its own verified domain. Send it again as a plain-text announcement, or ask MakerVera support to verify your sending domain first. See Email Content Rules.

The details panel says “Content wasn’t saved for this message.”

The message was sent before this feature was released, or the member’s account was deleted. Content can’t be recovered for these messages.

I don’t see “Show sensitive details”.

Check the message has hidden details. The content section lists them as “Some details are hidden”.
Check your role has View sensitive message details. Ask an owner or admin to add it.
The button only appears when a value was actually kept. Messages sent before this feature was released, and messages whose value couldn’t be stored securely at the time, have nothing to reveal.

The unread dot doesn’t appear, or won’t go away.

Open the bell once. That records the newest message as seen.
The dot is stored per browser. Opening the bell on your phone doesn’t clear it on your laptop.
If your browser blocks site data for MakerVera, the dot can’t be shown.

A message link says “This message isn’t available”.

A message link only opens for the person the message was sent to, in the makerspace that sent it.

Check you’re signed in to the account the message was sent to.
If you’re a member of more than one makerspace, open the link from the makerspace that sent the message.
If it still doesn’t open, the message is no longer available. Close the panel to see your other messages.

The Communications tab says it couldn’t load.

Refresh the page.
If the message persists, try again in a few minutes. This is different from an empty tab, which means nothing has been sent yet.

I don’t see the Communications tab on a member’s profile.

Your role needs permission to manage notification settings. Ask an owner or admin to update your role.