Search from the correct mobile scope

Search from the correct mobile scope 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 the Dosya mobile file browser and search in the current released client.
• Confirm the active account and workspace, then identify known file and its expected workspace or folder.
• Use a small non-confidential test item and record its current state before changing it.
• Keep passwords, API keys, recovery codes, private links, personal data, and confidential file contents out of screenshots and support messages.

Steps: search from the correct mobile scope

1. Open the Dosya mobile file browser and search and confirm the active account and workspace.
2. Locate known file and its expected workspace or folder and verify its name or identifying details.
3. Confirm the current scope, enter a distinctive name, and inspect folder context in each result.
4. Read the displayed warning, permission, progress, or confirmation state before leaving the screen.
5. Confirm that the search result identifies the file in its intended location.
6. Refresh, fetch, or reopen the relevant view once to verify the result persisted.

Expected result

The controlled workflow completes and the search result identifies the file in its intended location. 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 the Dosya mobile file browser and search, 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

• Browse files on mobile
• Switch mobile accounts