When creating a new account on hex.pm and running mix hex.user auth, there is no mention of the verification email in the CLI feedback. For example:

ᐅ mix hex.user auth
Username: my-username-here
Account password:
Generating keys...
You have authenticated on Hex using your account password. However, Hex requires you to have a local password that applies only to this machine for security purposes. Please enter it.
Local password:
Local password (confirm):

This feedback leads me to believe that I can readily be added to organizations and then download their dependencies, for example:

mix hex.organization auth my-organization-here

But when running mix deps.get against a project in said organization, I get a failure with the message:

This could be because the package does not exist, it was spelled incorrectly or you don't have permissions to it

Debugging, using mix hex.user whoami reveals the problem:

ᐅ mix hex.user whoami
Failed to auth
email not verified

It would be helpful for new users coming to the platform to make this email verification step more transparent through the CLI by doing one or both:

• During mix hex.user auth and on mix deps.get failures, provide clear messaging about verification step
• Bail out at username/pass entry if email is unverified

Even if the second one were implemented, the first would still be helpful in instances where an email address was changed and needed to be re-verified.