Understand workspace storage region and routing

The workspace region is the durable storage choice made at creation; transfer edges or network routes do not silently migrate stored files.

Before you start

• Use the current released client or web app and sign in to the intended account.
• Select the correct workspace and use non-confidential test data.
• Record the current setting or result before changing it.
• Keep passwords, API keys, recovery keys and private links out of screenshots and support messages.

Steps: understand workspace storage region and routing

1. Open workspace details and record its storage location.
2. Compare it with the region chosen at creation.
3. Treat a nearby transfer route as transport rather than durable storage.
4. Check current region availability before creating another workspace.
5. Plan an explicit verified transfer when location must change.
6. Confirm destination copies before removing originals.

Expected result

The understand workspace storage region and routing workflow completes for the test item and its result remains visible after a refresh or reconnect.

Limits and important details

• Available controls depend on the current client version, plan, role and workspace policy.
• A successful connection does not grant permissions beyond its credential and workspace boundary.
• Verify important results with a harmless test before relying on the workflow.

Troubleshooting

The expected control is missing. Confirm the current client, active workspace and role, then check the relevant settings page.

The operation is rejected. Read the exact error and compare credentials, permissions, quota and workspace policy.

The result is still unclear. Repeat with one small test item and contact private support with the time, client version and nonsecret error.

Related guides

• Create a workspace and choose location
• Switch workspaces