Obsi Drive · Support

Know what happens to your files.

Start with product documentation and service status, then bring the affected feature and approximate time when account-specific help is needed.

Obsi Drive
supportOne canonical file layerSource-aware · protected when chosen · governed automation

Use Features, Integrations, and Developers for supported workflows, provider behavior, API endpoints, SDK usage, and current capabilities.

Check service status and provider configuration availability before troubleshooting an account-specific issue.

Sign in first for account or workspace issues so the correct application and workspace context is available.

When escalating a problem, include the affected feature and approximate time—but never send passwords, API keys, OAuth tokens, or access tokens.

Public response-time commitments are deployment-specific unless a commercial agreement explicitly defines them.

Obsi Drive

One library. Every source still visible.

OverviewBook a call →