dosya.dev Help

Authenticate the Dosya CLI

Sign the CLI in with the supported interactive flow or a dedicated secret, then verify the selected account without printing credentials.

Last reviewed

Authenticate only after confirming the CLI binary and account. Automation should use a separately revocable least-privilege credential.

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: authenticate the dosya cli

  1. Open the CLI authentication help.
  2. Choose the supported interactive or automation method.
  3. Complete sign-in without placing a secret in shell history.
  4. Run the account or status command.
  5. Confirm the expected account and active workspace.
  6. Revoke the test credential when it is no longer needed.
Dosya API-key list showing named technical credentials that can be identified and revoked independently.
Name each credential for the client and task it serves. Open full-size screenshot.

Expected result

The authenticate the dosya cli 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.

Continue with another task

Was this helpful?

Loading helpfulness results…

Voting saves a necessary ballot cookie for up to 180 days so you can change your answer.

About views and your privacy

Views count page openings, not reading or task completion.

View measurement is off by default. If you enable it, a separate 30-minute cookie prevents repeat openings from increasing the count. We do not use fingerprinting or connect this session to uploads or shares.

Questions and replies

Ask about the steps in this guide. Questions are reviewed before publication.

Keep account details, credentials and private files out of public questions. Use private support for those.

Loading questions…

    Sign in to your Dosya account to ask a question.