Vigicap
Connector
HaloPSA
A single agency-level credential, for the whole portfolio.
Your PSA already knows the list of your clients: this connector imports it, then reports for each one the asset inventory, their identification and their technical owner. It proposes no ReCyF level. HaloPSA records no security measurement on assets.
01
What to create in the tool
The access is created in HaloPSA, 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
HaloPSA > Configuration > Integrations > Halo API : créez une application « Client Credentials », puis, sur son onglet « Permissions », cochez uniquement « read:customers » et « read:assets ». Si la même application sert aussi à la remontée de tickets, ajoutez-y « read:tickets » et « edit:tickets ».
Minimum role
Application API « Client Credentials » portant exactement deux permissions, toutes deux en lecture : « read:customers » (GET /Client, la liste des clients) et « read:assets » (GET /Asset, l'inventaire). Aucune permission d'écriture, et pas le scope « all ».
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.
- Client ID
- Client Secretsecret
- URL du serveur d'authentificationoptionalURL
Uniquement si votre installation sépare l'authentification de l'API. Sinon, laissez vide.
03
Per-client routing
The credential itself is not repeated: one, entered once at agency level, covers the whole portfolio — the difference you feel with forty clients rather than four.
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.
- Halo client ID
Client identifier in HaloPSA tickets are created under.
e.g. 42
- Ticket type IDoptional
Optional — Halo ticket type (default: the instance's default type).
e.g. 1
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.
Read-only
The reads are read-only: Vigicap writes nothing into the tool while reading it.
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.
Scopes requested
The exact scopes requested at authorisation, named as the vendor names them.
- read:customers
- read:assets
- read:tickets
- edit:tickets
Verification
This connector has been run end to end against a real instance of the tool, not merely tested against a mock.
The trademarks and logos mentioned belong to their respective owners and identify the tools Vigicap is compatible with — see the legal notice.