> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trusset.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Investor Profiles

> Your compliance policy as configuration, applied on every onboarding path and enforced on-chain

This page is for the compliance lead or operator who decides who may onboard and invest through an instance. After reading it you will know what an investor profile controls, where it applies, and how it gates lending markets and vaults.

An investor profile turns your onboarding policy into configuration. It decides who may onboard, which documents they provide, which countries you refuse, and how each customer is classified. Every onboarding path of your instance applies the same profile. The result is recorded on-chain, where a token, a lending market or a vault checks it before anything moves.

## What a profile controls

<CardGroup cols={2}>
  <Card title="Investor classification" icon="scale-balanced">
    Retail, professional or eligible counterparty, applied to every customer the profile verifies
  </Card>

  <Card title="Who may onboard" icon="building">
    Natural persons through KYC or legal entities through KYB, optionally professional clients only
  </Card>

  <Card title="Required documents" icon="id-card">
    The identity, liveness, residence, questionnaire and company documents the check collects
  </Card>

  <Card title="Blocked countries" icon="ban">
    Countries refused on every onboarding path of the profile
  </Card>

  <Card title="Re-verification period" icon="clock-rotate-left">
    How long a verification stays valid, from 30 days to five years, or without a limit
  </Card>

  <Card title="Eligibility register" icon="shield-check">
    An on-chain register that holds exactly the wallets admitted under the profile
  </Card>
</CardGroup>

The identity check runs through Sumsub, on the level you name for each profile. On the Trusset ID Register the investor type is written on-chain with the identity. An ERC-3643 identity registry carries no investor type, so there it stays on the customer record.

## Start from a preset

Every instance starts with three presets:

| Profile | Classifies as | Admits | Documents |
| - | - | - | - |
| Retail | Retail | Natural persons | Government ID, selfie and liveness |
| Professional | Professional | Natural persons, professional clients only | Government ID, selfie and liveness, proof of address |
| Eligible Counterparty | Eligible counterparty | Legal entities, professional clients only | Government ID, selfie and liveness, proof of address, company documents |

The presets cannot be deleted, and their name, classification and professional-client rule are fixed. Their documents, level and blocked countries can be adjusted. When your policy differs, add a custom profile, for example a professional profile for one jurisdiction with its own blocked countries, or a KYB profile for corporate clients. A custom profile works everywhere a preset does.

## Apply one policy everywhere

A profile is the policy for every path a customer can take into your instance:

* **ID links:** a hosted verification link issued under a profile runs that profile's check, with its documents and its applicant type. The link keeps the classification it was issued with.
* **Customer records:** a customer created or updated under a profile is checked against its blocked countries.
* **On-chain verification:** a wallet registered on your identity register under a profile receives its investor type and is checked against its blocked countries.
* **Pending approvals:** an approved check waits until your wallet signs the registration, and the profile is applied again at that point.

Adding a country to a profile's blocked list also queues the removal of every admitted wallet whose customer comes from that country. Nothing is written to a register until your wallet signs.

## Change a profile safely

A profile in use carries real customers, so changes to it are controlled:

* **Reclassification needs confirmation.** Changing the classification, the professional-client rule or the applicant type of a profile in use must be confirmed before it applies. The change is written to the audit log with the customers it affects.
* **Disable instead of delete.** A disabled profile takes no new links, customers or wallets, while customers already under it keep working. A profile in use cannot be deleted, and its key cannot change.
* **Every admission keeps its requirements.** Each admission records a hash of the requirements it was made under. When the requirements change, admissions made under the earlier ones are flagged.

## Gate lending and vaults on a profile

Give a profile an eligibility register and it becomes a gate. The register holds exactly the wallets admitted under the profile. A lending market gated on it lends only to that profile's customers, and a vault takes deposits only from them.

Admissions and removals are queued for you. A customer who passes an ID link review with a wallet is queued for admission. A revocation, a rejected review, a country added to the blocked list or an expired re-verification period queues a removal. On a register deployed for the profile, your wallet signs each change before it reaches the register.

A lending market priced from a live market price lends to professional borrowers only. Its borrower gate must be the eligibility register of a profile limited to professional clients. See [Professional borrowers](/endpoints/lending/set-identity-gates#professional-borrowers).

A register is deployed for a profile in the Issuer Platform, or an existing register is bound to it. Eligibility registers are available on Ethereum instances only.

## Set up a profile

<Steps>
  <Step title="Open the profiles">
    In the [Issuer Platform](https://issuers.trusset.org/), open Customers, then Configure. The three presets are already there.
  </Step>

  <Step title="Define the policy">
    Adjust a preset, or add a custom investor type. Set its on-chain type, who may onboard, the professional-client rule and the re-verification period. Then choose the Sumsub level, the required documents and the blocked countries.
  </Step>

  <Step title="Onboard customers">
    Issue [ID links](/endpoints/customers/create-id-link) under the profile, or name its key when you verify a wallet through the API.
  </Step>

  <Step title="Gate markets and vaults">
    Deploy an eligibility register for the profile, then choose the profile as the gate of a lending market or vault.
  </Step>
</Steps>

<Note>
  Investor profiles are in beta. They are created and edited in the Issuer Platform. The API reads them with [List Verification Profiles](/endpoints/customers/list-verification-profiles), where they are called verification profiles.
</Note>

<CardGroup cols={2}>
  <Card title="Verification Profiles" icon="list-check" href="/endpoints/customers/list-verification-profiles">
    Read every profile and its eligibility register through the API
  </Card>

  <Card title="Eligibility Registers" icon="shield-check" href="/endpoints/customers/introduction#eligibility-registers">
    Admit and remove wallets on a profile's register
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.