1. Overview
Seedling plans to connect Okta as a source of operating context. This page records the intended product boundary while the provider-specific authorization, synchronization, and deletion contracts are still being designed.
Do not create or send Okta credentials for Seedling yet. Seedling support will never ask for a token, password, private key, export, or customer content by email.
2. Current availability
- Status
- Planned. There is no generally available customer connection flow for this catalog entry.
- Credentials
- Seedling does not currently ask customers to store authentication material for this planned connector.
- Synchronization
- Ordinary customer workspaces do not currently ingest Okta data under this integration kind.
3. Anticipated data coverage
The initial pipeline is expected to evaluate the following categories. Exact objects, history windows, filters, attachments, and change handling will be documented only after implementation and replay testing.
- organizations and applications
- users, groups, and assignments
- policies, logs, and authentication events
4. Intended permission contract
- Prefer provider-managed OAuth, service identities, or other revocable authorization over shared human credentials.
- Request only the read permissions needed for the documented object population.
- Preserve the exact connection identity and provider-native resource boundaries through synchronization, revocation, and purge.
- Fail closed when the provider cannot supply reliable audience evidence; administrator status will not create a content-access bypass.
- Do not request permission to create, edit, send, publish, or delete Okta records unless a future product change is separately reviewed and documented.
5. Security before launch
- No public Okta connector means no ordinary customer credential or synchronized provider payload should exist for this catalog entry.
- Any future preview must use workspace-scoped credentials, tenant-scoped storage, non-secret queue payloads, and deterministic connection-owned purge behavior.
- Generated output will remain subject to Seedling's human review, verification, and approval gates.
6. Retention and deletion before launch
Because the public Okta connector is not available, there is normally no connector-owned Okta data or credential to retain or delete. Preview or test participants should use the deletion procedure on this guide and identify the exact workspace and test connection.