1. Disconnect Asana in Seedling
Local deletion proceeds even if Asana token revocation is unavailable. Transient provider failures never trigger destructive absence deletion.
- Sign in to the Seedling workspace as a workspace administrator.
- Open Apps or Connections, select Asana, and choose Disconnect.
- Confirm the request. Seedling stops new work, revokes the managed OAuth refresh token when present, and starts a durable purge.
- Wait for the disconnect operation to report completion before reconnecting or changing credential ownership.
2. Deauthorize in Asana
For the Seedling-managed app, remove the authorization from your Asana app settings. Seedling’s periodic token introspection detects confirmed deauthorization, stops work, revokes the installation route, and starts the same local purge.
For a customer-managed PAT, delete or reset the token in Asana and also disconnect in Seedling. Revoking a PAT alone stops provider access but does not provide Seedling an immediate provider-removal event.
3. Request deletion without workspace access
Email privacy@tryseedling.ai from an address associated with your organization. Include the organization name, Seedling workspace name, Asana workspace GID, and your authority to request deletion. Never include a PAT, OAuth token, or customer content.
Seedling verifies the requester before acting and will explain any information needed to locate the tenant safely.
4. What the purge removes
Disconnecting does not delete or modify original information in Asana. Approved Seedling configuration may retain a bounded approval record, but its Asana evidence and source-derived content are removed or redacted.
- Encrypted Asana credentials and the tenant connection record.
- The Asana source, provider staging rows, synchronized source objects, chunks, embeddings, and source entitlements.
- Source-linked exploration, chat, activity, fieldwork, verification evidence, and other derived data owned by the integration.
5. What may remain
- Backups
- Deleted information may remain in encrypted, access-restricted backups until expiry, ordinarily within 35 days. It is deleted again if a backup is restored.
- Lifecycle audit
- Seedling may retain identifiers, action, outcome, bounded reason codes, and timestamps needed to demonstrate deletion. These records contain no credentials or native payloads.
- Legal and security records
- Limited records may be retained longer when required for security, fraud prevention, disputes, accounting, or law.