Vigicap
Connector
Atera
Outbound PSA integration: Vigicap files tickets into it.
Your actions go into Atera as tickets, with their title and description: the action plan stops being a list to re-key into the tool your technicians already work in. No ReCyF level is proposed. Pushing a ticket does not measure a client's posture.
Beta01
What to create in the tool
The access is created in Atera, not in Vigicap. Vigicap never asks for an administrator's password: it expects an API credential that you create, that you can see, and that you can revoke without us.
Where to generate it
Atera → Admin → API: generate your API key. The client ID comes from the customer record (Customer ID).
Minimum role
Clé d'API Atera. ÉCRITURE : la clé Atera n'est pas cloisonnable en lecture seule — elle porte les droits du compte qui l'a créée. LECTURE : la même clé relit le ticket ; aucune portée distincte n'existe, ce qui est précisément pourquoi la phrase précédente est écrite telle quelle.
Taken from the vendor's own role model, and checked before publication.
02
What to enter in Vigicap
The exact fields of the connection form, in the order they appear. Values marked “secret” never travel back to the browser: they are encrypted at rest and deleted on disconnection.
The form starts with the instance address, entered separately from the fields below. The public catalogue does not yet publish whether this connector needs one, or what it looks like — so this list is exact about everything else, and silent about that first field.
- API keysecret
03
Per-client routing
These fields are filled in client by client: they say which PSA account the ticket must land under. A wrong value does not fail the push — it succeeds against someone else, which is why Vigicap checks them the moment you type them.
- Contact ID (EndUserID)
Atera contact ID (End User) tickets are attached to — the client is inferred from it.
e.g. 12
04
What it does, and what it does not do
ReCyF objectives it pre-fills
This connector feeds no ReCyF objective, and that is not a gap: it does not measure a client's posture.
What goes out to the tool
This connector WRITES: it creates a ticket from an action in the plan.
What comes back
The state of an already-created ticket comes back: its status, its closing date, its last activity. A closed ticket becomes a PROPOSAL a consultant confirms — never an action closed of its own accord. An agency that closes its own ticket must not be able to mark its own homework in the document an auditor reads.
What is read, what is kept, for how long and with which rights: the same register, connector by connector, in the data inventory.
Verification
This connector was written from the vendor's documented API and has not yet been run against a real instance. It is marked “Beta” everywhere it appears.
The trademarks and logos mentioned belong to their respective owners and identify the tools Vigicap is compatible with — see the legal notice.