Skip to main content
Built for the first thing a member reads after logging in. Replaces a launch email nobody reopens. The welcome message sits at the top of the dashboard. It is rich text with images and personalization placeholders. Every organization has one general message, and organizations that use user types can add more, each aimed at specific types. Settings → Customization → Dashboard Welcome
Requires the Orgo administrator flag. The page is headed Welcome Messages by User Type. The same screen is one click away from the dashboard itself: an administrator sees a pencil on the welcome card.

Writing the message

Welcome Messages by User Type, with the Hidden and One message mode buttons at the top, Create New Message beside them, and the organisation's default message open in the editor below An organization that has no message yet sees Your members currently see no welcome message, with Orgo’s standard message shown for reference and two buttons: Use this message, which saves the standard text as your general message, and Write my own. Once a general message exists, Restore standard message on its card puts the standard text back in place (after a confirmation), without ever leaving members with nothing.
1

Open the message card and click edit

An organization with a single message opens it in edit mode automatically.
2

Write the content

The editor supports headings, bold, italic, links, lists and pasted or uploaded images. Images are uploaded when you save, not when you paste them.
3

Add placeholders

Type them inline in curly braces. They resolve per member when the dashboard renders.
4

Add an image URL (optional)

Welcome message Image URL takes the address of an image shown alongside the message. It must be a publicly reachable URL.
5

Assign user types (optional)

On a non-default message, add user types from the dropdown. See targeting below.
6

Save

The message is live immediately. Cancel closes the editor without saving.

Placeholders

Write them exactly as shown, with no spaces inside the braces. The editor’s own hint lists only the two name placeholders, but {organizationName} works as well. Welcome message editor with the rich text area, the placeholder hint, the image URL field and the sticky switch

Targeting by user type

Create New Message (top right, once at least one message exists) starts an extra message. It only reaches anyone when it is assigned user types, so it is useful on organizations that use user types.
  • The Default message is tagged as such and labelled All other users (or All members when you do not use user types). It is the fallback for anyone whose user type has no message of its own. It cannot be deleted.
  • Any other message carries a list of user type tags, added from the Add dropdown in edit mode. Assignment is exclusive: adding a user type to one message removes it from whichever message held it before, so a member is never matched by two.
  • A non-default message with no user types assigned shows Nobody sees this message.

Which message a member sees

The row of buttons at the top of the page chooses what members get: Within One message: a member whose user type has its own message sees that one; a member whose type has none, or any member when user types are not in use, sees the general message; and if no message exists at all, nothing renders.

Sticky and dismissible

Each saved message has a Sticky toggle, and the help text says it plainly: if activated, the message is always visible and cannot be closed by users. A non-sticky message has a close button. Once a member closes it, it stays hidden for them across sessions, and closing one hides every message that is not sticky, not just that one. That preference is per member and is not reset when you edit the text.
Editing a non-sticky message does not bring it back for members who already dismissed it. For an announcement that must be read, make it sticky, or use a notification or the newsletter.

What to put in it

A dated message is worse than none. Either keep it current or write something that does not expire.

Troubleshooting

Check the setting at the top is not Hidden, that a message exists, and that its content is not empty (the card preview shows No content yet when it is). If you use user types, check the reader’s type is either assigned to a message or covered by the default.
Almost always a dismissal. Non-sticky messages stay closed once a member closes them. Turn on Sticky to make it unclosable.
Use single braces with no spaces: {firstName}, not { firstName }. Names are case-sensitive. Only {firstName}, {lastName} and {organizationName} are substituted; anything else is left as typed.
That is intentional. A user type belongs to exactly one message, so adding it here removes it there.
The image URL must be publicly reachable over HTTPS. Test it in a private browser window. Images pasted into the editor itself are uploaded when you save the message, so save before checking those.
Not supported: targeting is by user type only. Either use {organizationName} and keep the message generic, or send local announcements through notifications or a newsletter segmented by local center.
You cannot. Replace its text with Restore standard message, or choose Hidden to suppress all messages at once.