iGrant.io individuals (Consent BB admin Individual API)

When to use

When your app onboards a user, create a matching individual in the iGrant.io Consent Building Block and store the returned individualId against your own userId. That mapping is what later lets igrantio-consent-records record and manage consents for the right person.

The mapping (the important part)

your users table          Consent BB
+----------+-------------+          +---------------------------+
| user_id  | individual  | <──────► | individual { id, ... }    |
|  u_123   |  6541...cd  |          | externalId = "u_123"      |
+----------+-------------+          +---------------------------+

Persist individualId in YOUR database keyed by your userId. The reference uses externalId = your userId so the individual is also recoverable from OWS if the local mapping is ever lost.