> For the complete documentation index, see [llms.txt](https://smedai.aivd.ch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://smedai.aivd.ch/ressources-humaines/procedure-cartes-de-visite.md).

# Procédure cartes de visite

Les cartes de visites sont destinées aux collaboratrices et collaborateurs qui ont des échanges avec des personnes externes à l’office.

\
1\. Éligibilité

* Chacun·e peut faire une demande de cartes de visite après avoir validé sa période d’essai.

### 2. Demande

* Pour faire la demande, il suffit d’envoyer un mail au Service RH à l’adresse : <servicerh@vd.oai.ch>. Merci de préciser le nombre de cartes de visite souhaité. Les commandes sont traitées par paquet de 150 cartes.

### 3. Conditions de commande

* Les commandes de cartes de visite sont transmises à notre prestataire dès qu’un minimum de 3 demandes est atteint.

### 4. Réception

· Le service RH effectuera la commande des cartes de visite auprès de notre partenaire Polyval. Dès que les cartes sont prêtes, un mail vous sera envoyé pour vous informer que vous pouvez les récupérer au bureau RH.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://smedai.aivd.ch/ressources-humaines/procedure-cartes-de-visite.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.