For the complete documentation index, see llms.txt. This page is also available as Markdown.

Sign in & get access

Sign in to the desktop app with your work email, how your organization is created, and what to do when you see nothing.

Drizz signs you in with Google SSO on your work email domain and places you in your company's organization automatically.

Sign-in method

Google SSO, work email domain only

Personal addresses

Blocked

Your organization

Created automatically by the first person from your domain

Trials

Enabled by Drizz after your first sign-in, not instantly

Watch out

Signed in but no apps or files is an access problem, not data loss. Don't reinstall

Prerequisites

  • Drizz desktop app installed in /Applications

  • A Google account on your company's email domain

  • For trials: an instance enabled by your Drizz contact

Sign in

  1. Launch Drizz Desktop from /Applications.

  2. Click Sign in with Google.

  3. Select your work account in the browser window that opens.

  4. Return to the app.

  5. Confirm you land on the Connect Device screen.

Tokens are stored in the macOS keychain. Signing out clears them.

Account requirements

Requirement
Detail

Email domain

Your company's work domain. Personal domains are blocked at sign-in

Domain mismatch

If your company signs in to Google with a different domain than the one on your business cards, use the Google one

Account type

Organization accounts only. There is no personal tier

How your organization is created

The first person from an email domain to sign in creates the organization. Everyone from that domain who signs in afterwards joins it. No configuration is required.

Everything is org-scoped and shared with colleagues in the same organization:

  • Tests, modules and folders

  • Datasets

  • Memory — app context and blocker rules

  • Registered apps and test plans

  • Reports

  • Your token wallet

Trials need approval

On a trial, Drizz enables your instance after your first sign-in. Sign-in succeeding is not the same as access being live. The first-day sequence is: install, sign in, then wait for your Drizz contact to confirm the instance is enabled.

Signed in but you see nothing

An empty app after a successful sign-in is an access problem, not data loss. Files are not stored in the app, and reinstalling changes nothing.

What you're seeing
Cause
Fix

No apps and no files, first day

Trial not yet enabled

Contact your Drizz representative

Sign-in completes but the app doesn't log in

Known issue

Quit and relaunch. If it persists, use Report an issue

Common mistakes

What you do
What happens

Sign in with a personal address

Blocked. There's no personal tier

Reinstall the app when you see an empty file list

Nothing changes. The list is empty because of access, not the install

Assume your account is live the moment sign-in succeeds

On a trial, access is enabled separately. Check with your Drizz contact

Share one account across the team

Everyone is in the same org anyway — sign in with your own email so reports and runs are attributable

Next


Last updated: 6 August 2026

Last updated

Was this helpful?