Clarity integrations
An appointment in your calendar. A task in Clarity. See both in one day and decide which source you want to show. You can try that view right here.
Example data. A real connection always starts with your permission.
Calendar + timetable
Lessons, your own appointments and a free afternoon all belong to the same day. Clarity brings them together, with identifiable sources you can show or hide individually.
A Wednesday in your life
4 events shown
Hide a source. The day stays the same.
An appointment has a time. A lesson has a room. Together, they make a day you can plan around.
Apple Calendar connects with your permission. Hiding a calendar does not delete it or disconnect it.
Calendar gives you an overview. Today brings you back to the events and tasks of the current day.
Source by source
Select a route and trace what enters Clarity, what can go back and which permission starts the process.
Explicit system permission; events connect through Apple's calendar framework.
This native route is listed in the public product catalogue. Whether data appears depends on your permission.
Read-only website example. Selecting a route does not connect an account, grant permission or start an import.
Four technical states
Clarity uses provider names only to identify a technical route. They imply neither a partnership nor broader permission.
An existing system route with the permission shown for it.
You start a capture or add a source yourself; this is not a permanently connected third-party account.
This route is not publicly released. Outstanding requirements are stated on the entry.
Clarity does not offer this connector in the current public release.
Public status matrix
Where the current product contract confirms no write scope, the matrix promises none. Preview and not available have no public data route.
| Integration | Route | Read | Write | Approval boundary | Status |
|---|---|---|---|---|---|
| Apple CalendarExplicit system permission; events connect through Apple's calendar framework. | Native | Only after system permission | No public write scope promised | Explicit system permission | Natively available |
| Apple RemindersExplicit system permission; a functional path for system reminders. | Native | Only after system permission | No public write scope promised | Explicit system permission | Natively available |
| Share to ClarityPass content to Clarity from the iOS share sheet. | Native | Only the content actively shared | Passed to Clarity; no write-back | You initiate every handover | Natively available |
| Files, photo and textManual import paths; no permanently connected third-party account. | Import | Only manually selected content | Imported into Clarity; no third-party account | You initiate every import | Manual route |
| ICS and WebUntisA calendar feed or manual school-calendar and timetable paths. | Import | Selected feed or import | No write-back promised | Added by you | Manual route |
| Microsoft OutlookOAuth configuration and security review remain outstanding. | Private Preview | Not publicly released | Not publicly released | OAuth and security review outstanding | Private Preview |
| Google WorkspaceRestricted Scopes and the required Security Assessment are not complete. | Not offered | Not available | Not available | Restricted Scopes and assessment outstanding | Not available |
| Apple HealthThe current registry state is not ready for marketing. | Not approved as a connector | Not available | Not available | Registry state not approved | Not available |
How to read the matrix
Read permission applies only to the named system route or the content you select yourself. It is not silent access to an entire third-party account.
Permission to read does not automatically allow write-back. The current public matrix promises no external write scope that the specification does not confirm.
Native routes begin with explicit system permission. Manual routes begin only when you start the specific handover or source yourself.
After the source
Even an approved source may not jump directly to a consequential change. When Clarity prepares a next step from a signal, the consequence class, preview and, depending on impact, your explicit approval still apply.
View action safeguardsThe current state remains separately verifiable in the specification and Developer Center.
