Codity Accounts
Codity accounts let teams use Codity with email-based accounts instead of signing in through GitHub, GitLab, Azure DevOps, or Bitbucket.
This is useful for teams that want CLI access, seat management, and usage analytics without tying dashboard login to a VCS provider.
Admin Sign-In
Organization admins can sign in with an email code:
- Open the Codity sign-in page.
- Choose the Codity email sign-in option.
- Enter your email address.
- Enter the 6-digit code sent to your inbox.
After verification, Codity opens your organization dashboard.
Inviting Members
Admins can invite members from the Subscription page:
- Go to Subscription.
- Open Add Developer.
- Enter the member's email address.
- Click Send Invite.
Codity emails an invite link to the member. The dashboard also shows the invite link so you can copy it if needed.
Invite links expire after 72 hours.
Accepting an Invite
When a member opens an invite link, Codity asks them to set up their account:
- Confirm the invited email address and organization.
- Enter a full name.
- Create a password with at least 8 characters.
- Confirm the password.
- Submit the form.
After the account is created, the member can sign in to the CLI with email and password.
CLI Login for Codity Accounts
Members who use a Codity email account should sign in from the terminal with:
codity login --email
The CLI prompts for email and password, then stores the workspace credentials locally.
After account setup, Codity may show a ready page with the install guide and a copyable codity login --email command. Use that command from the terminal where you want to run Codity.
After login, run:
codity doctor
to confirm the CLI can reach Codity services.
Roles
Codity accounts use two organization roles:
| Role | What they can do |
|---|---|
| Admin | Manage subscription, seats, member invites, and CLI analytics. |
| Member | Use the CLI features enabled for their seat. |
At least one admin should remain in the organization so the team can manage subscription and member access.
Seat Access
Members need an active seat before they can use paid Codity services from the CLI. If a subscription is inactive, at its seat limit, or pending payment, Codity may block new member access until an admin updates the subscription.
See Managing Seats for seat management.