Skip to content

Sign-in & Accounts

The DCS portal gives you a few ways to sign in and a single Account page where you can review the companies and sites you can reach, manage passkeys, and request deletion of your data. This page explains each sign-in method and what your account controls.

Ways to sign in

Sign in with Google is always available on the portal login screen. It is the primary way in, and some flows (such as authorizing the command-line tools) require a Google sign-in specifically.

Two more provider buttons appear only when your portal enables them:

  • Microsoft — shown when Microsoft sign-in is turned on.
  • GitHub — shown when GitHub sign-in is turned on.

If you do not see the Microsoft or GitHub buttons, they are not enabled for your portal, and you can sign in with Google instead.

Passkeys

The portal supports passkeys — a passwordless sign-in backed by your device's built-in authentication (fingerprint, face, or device PIN) using the WebAuthn standard. On the login screen you can choose to sign in with a saved passkey.

You add passkeys from your Account page after signing in. If no passkey is available on the device you are using, sign in another way first, then add one from Account. Your original sign-in provider always remains as a recovery path, so adding a passkey never locks you out.

The Account page

Your Account page is the single place to see everything your identity has access to:

  • Companies — the company workspaces you belong to, with your role in each.
  • Site access — the sites within your selected company and your permission level on each.
  • Session details — when your current session was issued and when it expires.

Adding a passkey

From Account, choose to add a passkey and complete your device's prompt. Once added, the passkey is available the next time you sign in to the portal.

Requesting data deletion

The Account page includes a right-to-delete workflow. Requesting deletion revokes your portal access and flags your data for cleanup; you receive a confirmation once the cleanup is complete.

Authorizing the command-line tools

If you use the DCS command-line tools, you authorize them through a short device-code flow in the portal:

  1. Run dcs login in your terminal. It shows an 8-character code.
  2. Open the CLI authorization page in the portal (/cli-auth), signing in with Google if you are not already.
  3. Enter the code from your terminal and confirm.
  4. Return to your terminal — you are signed in.

Authorizing the CLI grants full account authority

Authorizing a device gives it the full authority of your portal account across every site you can access — including reading contact and resume submissions, which may contain personal information, through the CLI, the API, and any AI-agent integrations acting on your behalf. Only continue if the code came from a terminal you control.

Next steps