Skip to main content
Back to the connector catalogue

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.

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

  • 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 account in the ticketing tool 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

Vigicap writes nothing to the tool while reading.

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.

How Vigicap handles your credentials.

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.

What this connector reads, exactly

  • Your client list, as your PSA already holds it — this is the one connector that saves you retyping it.
  • For each client, the asset inventory, how each asset is identified, and its technical owner.

What it does not read

No security measure. HaloPSA does not record any on assets, so there is nothing to read: this connector proposes no ReCyF level, and that is a property of the source, not a limitation of the integration. A client's posture needs a connector that queries the security tool itself.

What these signals do not prove

  • An asset inventory in a PSA reflects what somebody typed into it. It proves neither that the estate is complete, nor that an asset still listed still exists.
  • A technical owner on file says who is designated, not who acts. That is useful for routing an action, not for measuring a practice.
Why does this connector propose no ReCyF level?
Because the source contains none. Deriving a level from an asset inventory would mean inventing a security measurement out of commercial data.
Does it write anything into HaloPSA?
Yes: it is also a ticketing connector, filing your actions as tickets and reading their state back. The inventory read changes nothing.