On a a Monday morning, you open your browser to request three days off on Agate-Tempo, and the page refuses to load. Before reaching out to IT support, it’s better to understand where the blockage is coming from. Access to Agate CNRS leave relies on a few technical prerequisites that most agents discover when they stop working.
Agate-Tempo connection impossible: distinguishing outage, inactive account, and credential error
When the login page is unresponsive or returns an error, three situations often get mixed up. Knowing how to differentiate them saves time.
An individual access problem is not resolved in the same way as a service outage. If the platform displays a maintenance message or if several colleagues report the same blockage at the same time, it is the infrastructure that is at fault. In this case, one can only wait for the service to resume.
On the other hand, if other agents in the laboratory are connecting normally, the problem lies with the personal account. Two avenues to check as a priority:
- Is the Janus account (the CNRS authentication system) active? A newly assigned agent or one whose contract has been renewed may not yet appear in the Réséda database, preventing any appearance in Agate-Tempo.
- Has the Janus password expired? The periodic password renewal policy blocks access to all related CNRS applications, including Agate-Tempo.
- Is the browser retaining an old session cookie? Clearing the cache and cookies associated with the domain cnrs.fr is sometimes enough to restore the connection.
If none of these checks resolve the blockage, contact the laboratory’s HR manager, who can verify the account status in Réséda and, if necessary, request its reactivation. To better understand the process of accessing Agate CNRS leave, the manager remains the first point of contact to consult.
Agate-Tempo CNRS: who has access and under what conditions
All personnel listed in the Réséda database automatically appear in Agate-Tempo. This includes permanent agents as well as contractors, whether they are researchers, engineers, or technicians.
Personnel whose employer is not CNRS (such as academics in mixed units) may also appear, but their presence depends on the laboratory’s policy. Some units encourage all their members to submit their absences to feed a collective team schedule, useful for organizing meetings or managing shared offices.
First connection and the role of the HR manager
During the first connection, you log in via the Janus portal with your CNRS credentials. The laboratory’s HR manager guides the agent on the initial setup: attachment to the correct team, identification of the leave validator, and checking balances.
One point to remember: submitting leave in Agate-Tempo is mandatory for CNRS agents. This obligation is particularly linked to the opening of a time savings account (CET). An agent who never submits their leave via the platform would miss out on this possibility.
Types of absences managed in the Agate-Tempo leave module
The Agate-Tempo absence module is not limited to annual leave. Several categories of requests can be submitted, each following its own validation circuit.
Annual leave and RTT days constitute the primary usage. The personal calendar displays remaining balances, credits, and the history of past requests. One can submit a request either directly from the calendar (by selecting the dates) or via the dedicated “New request” form.
Exceptional absences and remote work
Some exceptional leaves (marriage, PACS, death of a close relative, administrative summons) are managed differently. The agent sends an email to the HR manager, who records the absence in Agate-Tempo. A supporting document is then submitted to validate the request.
For remote work, initial requests are submitted on the Ariane platform, while floating remote work days (non-regular) are entered in Agate-Tempo. Confusing the two applications is a common mistake among newcomers.
Tracking requests and the role of the validator in Agate-Tempo
Once the request is submitted, it goes through a validation circuit. The validator (usually the team leader or unit director) receives a notification and can accept or reject the absence.
From the agent’s side, they can track the status of their request directly from the homepage. Three possible statuses: pending, validated, rejected. If the validator delays, one can add a comment afterward to indicate urgency.
Useful functions for validators
The validator has additional functionalities in Agate-Tempo:
- View absences and balances for their entire team on a customizable collective schedule.
- Submit an absence on behalf of a colleague (useful in case of sick leave declared by phone).
- Define one or more delegates to ensure validation in case of their own absence.
A validator absent without a delegate blocks all requests from their team. Configuring delegation as soon as they take office avoids this bottleneck.
Last operational tip: Agate-Tempo allows you to synchronize your absence calendar with your email agenda. This way, you avoid duplicate entries and oversights when planning meetings. This synchronization can be set up from the shortcuts on the homepage, in just a few clicks.
