Platforms and providers

Platform, provider, and integration

This reference explains platform, provider, and integration terms so you can choose a source with a clear purpose and read its visible status accurately.

Platform and provider are different

A platform is the product or environment where a task, record, message, or file lives. It describes the surrounding service, not what Lithi can currently do there.

A provider is the named service or source represented by a connection choice. A provider name does not grant access or describe which records a particular person may use.

An integration is a bounded connection between Lithi and a source for an approved purpose. It includes the account, selected resources, permissions, local state, and workflow that may use the result. Each account or scope is a separate decision.

Read the catalogue carefully

The integrations catalogue groups sources by category and describes the resource types a connection may concern. It helps you understand a source before connecting it.

The catalogue is not a live directory of every connection available to every customer. A row can describe an intended source boundary without confirming that your account, permissions, or selected resources are ready.

For setup, read connecting and managing integrations. Choose a source, review its scope, and follow the visible next action.

Read status and evidence

The catalogue status is an information signal, not a runtime health check. Evidence required means the relevant behavior still needs a reviewable proof before a stronger statement is appropriate.

Useful evidence says what was checked, on which bounded surface, with what account and resource scope, when, and with what result. A badge or status word cannot replace those details.

Runtime state belongs to one connection on one Mac. It may be waiting, ready, unavailable, revoked, or unable to proceed. Treat the visible local state and next action as the authority for that connection.

Keep the Mac connection scoped

Lithi for Mac hosts connected-account setup and local work. Start authorization from the Mac, review the permission screen, and select only the resources your workflow needs. The source remains the authority for the account and permissions.

Keep credentials and local authorization material in the app's connection controls. Never paste a token, secret, private message, or private record into a support request. A portal label does not broaden what the local connection can read or use.

Disconnecting, narrowing resources, or revoking authorization changes the connection decision. Recheck the resulting state before relying on a task. If permission is missing, pause and complete the requested authorization step rather than treating an earlier success as continuing permission.

Choose your next check

Use the catalogue to find a source and category. Use Trust: integrations for data and authorization boundaries.

When a local state needs attention, follow Help: integrations. Share only visible status, time, and next action.