Fix a desktop sync local-permission error

Fix a desktop sync local-permission error is easier to verify when you use one controlled item and confirm the account, workspace, source, and destination at each step. This guide follows the current Dosya workflow and identifies the result you should see.

Before you start

• Open Issues and Activity in the Dosya desktop app in the current released client.
• Confirm the active account and workspace, then identify issue naming a local file or folder that cannot be read or written.
• Use a small non-confidential test item and record its current state before changing it.
• Keep passwords, API keys, recovery keys, private links, personal data, and confidential file contents out of screenshots and support messages.

Steps: fix a desktop sync local-permission error

1. Open Issues and Activity in the Dosya desktop app and confirm the active account and workspace.
2. Locate issue naming a local file or folder that cannot be read or written and verify its name or identifying details.
3. Close applications holding the item, check operating-system permissions, and retry the single entry.
4. Read the displayed warning, permission, progress, or confirmation state before leaving the screen.
5. Confirm that the desktop app can access the local path.
6. Refresh, fetch, or reopen the relevant view once to verify the result persisted.

Expected result

The controlled workflow completes and the desktop app can access the local path. The result remains visible after a refresh, reconnect, or return to the relevant screen.

Limits and important details

• Available controls depend on the current client version, account plan, workspace role, policy, and selected integration surface.
• Processing, indexing, background transfer, provider authorization, or storage accounting can delay a visible result.
• For destructive, access-changing, or automated actions, validate with disposable data before applying the workflow to important files.

Troubleshooting

The expected control is missing. Return to Issues and Activity in the Dosya desktop app, confirm the active workspace, and check that your role and client version support the action.

The operation is rejected or stalls. Read the exact message and check permissions, locks, storage, network state, source availability, and any third-party authorization before retrying.

The result is still unclear. Repeat with one small test item, then contact support with the time, client version, workspace, and a nonsecret error, delivery, or request identifier.

Related guides

• Diagnose sync issues
• Resolve conflicts