An agent arriving at a ministry receives their Cerbère credentials, opens their browser, types in the old Mélanie2Web URL, and lands on a redirection page that they do not understand. This scenario repeats every week in the departments. The Mélanie2Web messaging system remains the daily communication tool for tens of thousands of civil servants, but its technical environment has changed recently, and yesterday’s habits do not always work anymore.
Connecting to Mélanie2Web via Bnum: the trap of old URLs
The first concrete blockage for a beginner is not the forgotten password. It is the URL itself. The gradual migration to the Digital Office (Bnum) has changed the entry point: you no longer go directly through the historical Mélanie2Web address, but through a unified portal that then redirects to the messaging system after Cerbère authentication.
In practice, if a colleague sends you a link starting with the old address, you risk encountering a redirection loop or an error page. The right reflex is to bookmark the Bnum portal URL provided by your IT department, not the one you find in an old email.
You can also find InnovoTech’s tips for getting started which detail this transition and the most common navigation errors during the first connections.
Strong authentication while teleworking: what really blocks beginners
Since the recent widespread adoption of two-factor authentication, connecting outside the ministry network requires a temporary code or a certificate in addition to the Cerbère password. This is no longer optional. An agent teleworking who has not activated this second factor finds themselves blocked from the very first attempt.
The activation procedure varies by ministry, but the logic remains the same: you need to anticipate this step before leaving the office. Once at home, without access to the internal network, retrieving the activation elements becomes more complicated.
Here are a few points to address before the first day of telework:
- Check with the IT department that the second authentication factor is indeed activated on your Cerbère account, and test the connection from an external workstation before you need it.
- Install the temporary code application recommended by your ministry on your work phone (or personal phone if local policy allows), and keep the backup QR code in a safe place.
- Never attempt to connect to Mélanie2Web from a public Wi-Fi network (train station, hotel, café): the ministry’s security guidelines explicitly prohibit this, and the connection will be blocked in most configurations anyway.
Feedback varies on the ease of this activation depending on the ministry. Some provide a step-by-step guide as soon as the credentials are issued, while others leave the agent to figure it out. If you haven’t received anything, ask your local IT contact directly.
Server filters on Mélanie2Web: organizing your inbox from day one
A ministerial inbox fills up quickly. Memos, circulars, meeting minutes, automated messages: within a few weeks, you can feel overwhelmed. The most underutilized feature by beginners is the server filter, which sorts messages before they even arrive in the inbox.
The difference with a local filter is significant: the server filter works even when you are not connected. A message filtered on the server side will already be sorted into the correct folder when you log in on Monday morning.
Creating a first useful filter in five minutes
Start with a single filter, targeted at the most voluminous messages: mailing lists. Identify the sending address of the list (often in a format like [email protected]), create a dedicated server folder, and automatically redirect these messages to that folder.
A well-configured filter reduces the noise in the inbox by half. It’s better to have one working filter than ten poorly calibrated rules that move important messages to the wrong place.
For folders, opt for a flat structure: three or four server folders at most to start (for example: Mailing Lists, Ongoing Project, Archives). A structure that is too deep quickly becomes unusable, especially on the web interface of Mélanie2Web, which does not always handle the display of nested subfolders well.
Storage and quota on Mélanie2Web: avoiding a full inbox blockage
The storage quota has been significantly increased in recent years, but it is not unlimited. When the inbox reaches its limit, new incoming messages are rejected without notification to the sender. You will no longer receive anything, and you won’t know it.
The reflex to adopt from the very first weeks:
- Delete large attachments after saving them to the shared storage space of the department, rather than keeping them in the messaging system.
- Regularly empty the trash and the sent messages folder, which count towards the total quota.
- Use the archiving function if it is available in your configuration, which moves old messages out of the active quota.
It is often observed that agents who encounter a quota blockage have never emptied their trash since starting their position. On Mélanie2Web, the trash is not automatically emptied by default in all ministerial configurations.
The transition to the Digital Office has not fundamentally changed storage management. The same quota rules apply, even if the interface for checking used space has been moved to the settings of the Bnum portal. Look for the “Quota” or “Storage Space” section in your account settings to monitor your usage.
Mélanie2Web is not a complex tool in itself, but its access and security specifics systematically trap new agents. Activating strong authentication before the first telework, using the Bnum portal URL instead of old links, setting up a server filter in the first week, and monitoring your quota: these four actions cover the vast majority of issues encountered during the first months of use.
