Audecius
Clarity
Download
What’s newFeaturesStudentsTeachersFamiliesPricingShopSupportDeveloper CenterMy Clarity

Developer Documentation · Integrations

Public status documentation

An integration starts with its real status.

Native access, manual import, Private Preview and unavailable are different technical contracts. The canonical public matrix therefore states the path, read boundary, write boundary and release — not merely a provider logo.

Open canonical matrixDocumentation index

Canonical source

One status. One public matrix.

/en/integrations is the authoritative public overview. This Developer page explains the semantics and lifecycle without duplicating a divergent connector list.

View status matrix

Current registry state

Four states. No silent reinterpretation.

The counts come from the existing public catalogue. They are not a usage, partnership or availability SLA.

3Natively available
2Manual path
1Private Preview
2Unavailable
Not evidence of a partnership

Provider names identify a technical path. Their appearance proves neither a commercial partnership nor data access beyond the matrix.

Status semantics

A connector and an import are not the same.

Natively available
An existing system path with the stated system permission. The status promises no additional read or write permission.
Manual path
The person chooses a file, content or source. There is no permanently connected external account.
Private Preview
The path is not publicly released. Open OAuth, security or registry prerequisites remain part of the description.
Unavailable
Clarity does not offer the connector in the current public release.
integration-status-contract.txt
status: live        → existing, bounded system path
status: manual      → person-initiated transfer
status: preview     → no public release
status: unavailable → no public data path

status ≠ partnership
read permission ≠ write permission

Lifecycle

From trigger to revocation.

  1. 01Trigger

    System permission or a manually started selection.

  2. 02Source

    Only the stated system path or selected content.

  3. 03Transfer

    Mapping into Clarity context without a silent external account.

  4. 04Action

    Access does not remove preview and consent boundaries.

  5. 05Revocation

    System permission or source remains revocable where the path supports it.

Public boundaries

What does not follow today.

  • There is no published external connector API through which third parties can register an integration themselves.
  • Approved members can create expiring sandbox API keys for the nine documented Developer operations. Production API keys, other people's account data, OAuth client credentials and public SDK packages remain closed.
  • A manual status must not be described as a synchronised account, background access or write-back.
  • Private Preview is not a waiting-list promise or guaranteed release.
  • Technical decisions follow the current entries in the public matrix, not marketing copy or a provider logo.
Clarity integrations — availability kept distinct