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

# Owner onboarding

> How a tenant becomes a verified owner and lists a property.

Becoming an owner on NKAMA is **two independent checks** — verify the person once, verify the
right to list each property. This guide is the orientation; the exact requests are in the
[API reference](/api-reference).

## The two checks

<CardGroup cols={2}>
  <Card title="Owner-KYC (once per person)" icon="id-card">
    Prove who you are with an identity document. Approval grants the `OWNER` role.
  </Card>

  <Card title="Property proof (once per property)" icon="house">
    Prove your right to list a specific property. Approval publishes it.
  </Card>
</CardGroup>

## Becoming an owner (KYC)

<Steps>
  <Step title="Apply">
    `POST /api/v1/verification/kyc` opens a request (any signed-in user).
  </Step>

  <Step title="Attach your ID">
    Upload the document via the media endpoints, then attach it with role `SELF_ID`
    (`POST /api/v1/verification/kyc/{id}/documents`). Capture its expiry date — an expired ID
    is rejected at submit.
  </Step>

  <Step title="Submit">
    `POST /api/v1/verification/kyc/{id}/submit` puts it in the review queue.
  </Step>

  <Step title="Admin approves">
    An administrator approves it. You are granted the `OWNER` role and your own organization;
    **sign in again** to get a token carrying the new role and `org_id`.
  </Step>
</Steps>

## Listing a property

Once you are an `OWNER`:

<Steps>
  <Step title="Register the property">
    `POST /api/v1/properties` creates it in `DRAFT` (not yet visible to tenants).
  </Step>

  <Step title="Open a right-to-list proof">
    `POST /api/v1/verification/property-proofs` with the `propertyId` and a `proofType`:
    `OWNERSHIP` (you own it — attach an attestation) or `MANDATE` (you manage it for the
    owner — attach the signed mandate + the owner's ID).
  </Step>

  <Step title="Submit and get reviewed">
    Submit it; a manager or administrator approves. On approval the property flips to
    `PUBLISHED` automatically.
  </Step>
</Steps>

## Reviews, decisions and revocation

* Reviewers can **approve**, **reject**, or **request more information** (you resubmit).
* Owner-KYC is decided by `ADMIN`; property proofs by `MANAGER` or `ADMIN`.
* An administrator can **revoke** an approval later (fraud): revoking owner-KYC strips the
  `OWNER` role and withdraws the owner's published properties; revoking a property proof
  withdraws that property.

Every decision is recorded and the applicant is notified. The full design rationale lives in
the backend repo (`docs/06-owner-onboarding-and-verification.md`); this page is the API-user
view.