Configuration

To create new announcements a user should be in the Announcements Managers group. When your user has such permissions, this is the way to create an announcement:

1. Go to Discuss > Announcements
2. Create a new one and define a title. This title will be shown in the announcement header.
3. Define the announcement scope:
   • Specific users: manually select which users will see the announcement.
   • User groups: users from the selected groups will be the ones to see the announcement.
4. Define the announcement body. You can use rich formatting and event paste your own html (editor in debug mode).
5. By default, the announcement will be archived. This is to prevent the announcement to show up before time.
6. Once the announcement is ready, unarchive it going to the Actions menu an choosing the Unarchive option.
7. Optionally you can set an announcement date to schedule the announcement. The announcement won’t show up until that date.
8. If the announcement doesn’t make sense once a date is passed, you can set a due date. From that date, the announcement won’t be shown to anyone.

Usage

When a user in the scope of active announcements logs in, those will popup. The user has to mark them as read to continue working. If the announcement is set during the user session, the announcement will be eventually prompted in the top bar on the right part. The user click on the unread announcements icon (a speaker) and the announcements will popup for the user to check them.

Users can go Discuss > Announcements to check current and past announcements. Announcement managers can also track which users have read the announcement.

Known issues / Roadmap

• It could be integrated in Discuss app to review past announcements.
• Log other information like geolocation, IP, browser agent, etc when marking announcement as read.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Maintainers

This module is maintained by the OCA.

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

This module is part of the OCA/server-ux project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.