Agate-Tempo is the leave and absence management application used by CNRS agents. The tool, accessible online, centralizes requests for paid leave, RTT, and exceptional absences for all personnel referenced in the Réséda database. Successfully connecting to Agate Congés CNRS requires understanding the authentication process, technical prerequisites, and common blocking points, aspects that are rarely detailed in internal guides.
Agate-Tempo Authentication: What the Janus Portal Involves
Access to Agate-Tempo goes through the Janus authentication system, the CNRS federated identity service. This portal centralizes identifiers for most internal applications (Agate-Tempo, Ariane, CNRS intranet). Specifically, the agent uses the same username/password combination as for their other CNRS tools.
The procedure for connecting to Agate Congés CNRS relies on this Janus component, meaning that an identifier issue on Janus blocks access to all services, not just leave. An expired password or an inactive Janus account prevents any attempts.
All personnel registered in Réséda appear in Agate-Tempo, whether they are permanent or contractual. Agents from partner establishments hosted in a CNRS laboratory may also be included, but their affiliation depends on local configuration. Field feedback varies on this point: some mixed units include all their personnel, while others reserve the tool for CNRS agents only.
Agate-Tempo Connection Issues: Identifying the Source of the Blockage
Connection difficulties with Agate-Tempo fall into a few recurring categories. Before contacting support, it is useful to check several elements on your own.
- Inactive or expired Janus account: new arrivals must activate their Janus account before they can access Agate-Tempo. An HR manager or the IT service of the regional delegation provides activation instructions upon starting work.
- Incorrect or expired password: the Janus portal requires periodic renewal. If the connection fails without an explicit error message, resetting the Janus password is the first reflex to have.
- Incompatible browser or full cache: Agate-Tempo operates via a web browser. Clearing the cache, disabling ad-blocking extensions, or testing another browser resolves a significant portion of display blockages.
- Administrative attachment issue: if the agent does not appear in Agate-Tempo despite a functional Janus account, the problem lies with the Réséda database. The unit manager must verify that the agent is properly referenced there.
The available data does not confirm whether CNRS has implemented multi-factor authentication for Agate-Tempo. In case of doubt, the IT department of the regional delegation remains the most reliable point of contact.
Role of the Manager and Validator in Agate-Tempo Leave
Connecting to Agate-Tempo is not limited to the individual access of the agent. The application relies on a validation workflow involving several profiles: the user (the agent submitting their request), the validator (often the team leader), and the manager (the administrative service of the unit).
Each profile has specific rights. The manager sets the reasons for absence, the rules for acquiring paid leave and RTT, and supervises the overall schedule. The validator approves or rejects requests. A delay in validation blocks the agent’s counter, which can complicate the opening of a time savings account (CET).
Local Configuration and Disparities Between Units
The leave module of Agate-Tempo offers customization options: activation of day donation, management of childcare days, telework configuration. These features are activated or not based on the choices of the local administrator. Therefore, the user experience can vary significantly from one unit to another.
An agent changing laboratories within CNRS may find that some reasons for absence available in their old unit do not exist in the new one. This is not a bug: it is a consequence of the decentralized configuration of Agate-Tempo.
Non-CNRS Agents in Mixed Units: Access and Limits of Agate-Tempo
CNRS laboratories often operate in mixed research units with universities or other organizations. The staff of these partner establishments do not always have access to Agate-Tempo. Some use applications specific to their employer (oHRis for the University of Strasbourg, for example).
For non-CNRS agents who still appear in Agate-Tempo, submitting leave requests in the tool allows the administrative service to have a consolidated absence schedule at the laboratory level. This visibility is useful for organizing meetings or managing shared spaces, even if the legal obligation to submit requests only concerns CNRS agents.
CNRS contractual staff generally have the same access rights to Agate-Tempo as permanent staff, with a leave entitlement that includes vacation days and RTT. The legal obligation to take a minimum number of leave days per year applies to everyone.
What to Do When Agate-Tempo Support Does Not Respond
Official guides generally refer to the IT department or the HR manager of the unit. In practice, response times vary according to regional delegations. Here are some concrete suggestions to unblock the situation:
- Contact the unit manager directly, who often has administrator access and can verify the attachment in Réséda.
- Use the CNRS intranet to access IT support request forms, rather than sending a generic email.
- Check the laboratory’s resource pages (often accessible without authentication) for any specific instructions for Agate-Tempo.
Submitting leave requests in Agate-Tempo remains mandatory for CNRS agents, especially to benefit from the opening of a time savings account. A prolonged blockage of access to the application therefore has direct consequences on the management of leave rights. Quickly resolving a connection issue, by targeting the correct source of the blockage, prevents a technical difficulty from turning into an administrative deadlock.
