doc/administration/broadcast_messages.md
{{< details >}}
{{< /details >}}
GitLab can display two types of broadcast messages to users of a GitLab instance:
Broadcast messages can be managed using the broadcast messages API.
[!warning] Broadcast messages are publicly accessible through the API regardless of targeting settings. Do not include sensitive or confidential information, and do not use broadcast messages to communicate private information to specific groups or projects.
Banners are shown on the top of a page, and optionally in the command line as a Git remote response.
$ git push
...
remote:
remote: **Welcome to GitLab** :wave:
remote:
...
If more than one banner is active at one time, they are displayed at the top of the page in order of creation. In the command line, only the latest banner is shown.
A banner can only be dismissed if you configure the banner to be dismissable.
GitLab shows notifications on the bottom right of a page. They can contain placeholders, which are replaced with the attributes of the current user:
{{name}}, would you like to give us feedback?
<a href="example.com">Take our survey!</a>
If more than one notification is active at one time, only the newest is shown.
Notifications support these placeholders:
{{email}}{{name}}{{user_id}}{{username}}{{instance_id}}If the user is not signed in, user-related values are empty.
You must have administrator access.
To display messages to users on your GitLab instance, add a broadcast message.
[!warning] Broadcast messages are publicly accessible through the API regardless of targeting settings. Do not include sensitive or confidential information, and do not use broadcast messages to communicate private information to specific groups or projects.
To add a broadcast message:
a and br HTML tags.br tag inserts a line break.a HTML tag accepts class and style attributes with the following CSS properties:
colorborderbackgroundpaddingmargintext-decorationbanner or notification.indigo.* to match multiple URLs and specify paths, for example:
*/-/milestones for any group or project's Milestones index page.*/-/milestones/* for individual milestone pages only.*/-/milestones* for both index and individual milestone pages.When a broadcast message expires, it no longer displays in the user interface, but is still listed in the list of broadcast messages.
If you must make changes to a broadcast message, you can edit it.
To edit a broadcast message:
Expired messages can be made active again by changing their end date.
If you no longer require a broadcast message, you can delete it. You can delete a broadcast message while it's active.
To delete a broadcast message:
When a broadcast message is deleted, it's removed from the list of broadcast messages.