Sign in and your Cahaves account

Cloud keeps no password of its own. You sign in with GitHub or Google, through your Cahaves account, which the Cahaves sign-in service keeps. Cloud receives your name, email address, picture and sign-in methods from it, and keeps its own session in your browser.

Your account is one person: you. It holds your organizations, each with its own projects and its own bill, and what stays yours in all of them: your SSH keys, git providers, notification channels and backup destinations. Organizations covers them.

Open https://cloud.cahaves.com. The sign-in screen offers two buttons, Continue with GitHub and Continue with Google.

Each press goes to that provider, even when you are already signed in to your Cahaves account, so the account you end up in is always the one the provider confirms. Once it does, you land on the Dashboard, or on Name your organization while you have no organization yet. Opening the sign-in screen while already signed in takes you straight to the Dashboard.

The first press of either button creates your Cahaves account and your Cloud account together. The console then asks you to name your first organization, on Name your organization, with your name filled in: keep it or type another, and press Create organization. Cloud prepares the organization's workspace, and the console says "Your workspace is still being prepared." until it is ready. Each later sign-in asks Cloud to finish a preparation that did not complete, in each of your organizations. The workspace is still being prepared covers a wait that does not end.

The provider has to give Cloud a verified email address. If your GitHub or Google account has none, the sign-in screen says "The provider has not verified your email address. Verify it there, then start again." or "The provider did not share an email address, and your account needs one." Verify the address with the provider, or make it visible to applications you sign in to, then press the button again.

A Cahaves account is found by the sign-in method, not by the email address. If you created your account with GitHub and later press Continue with Google with the same email address, the sign-in is refused:

An account already uses that email address. Sign in the way you did before, or connect this provider from your Cahaves account screen first.

To use both:

1. Sign in the way you did before

   Press the button you used the first time. You are signed in to Cloud and to your Cahaves account.

2. Open your Cahaves account screen

   In the same browser, open the account screen of the Cahaves sign-in service. It lists your Sign-in methods: Password, and each provider as Connected or Not connected.

3. Connect the other provider

   Press Connect beside it and confirm with that provider. From then on, either button on Cloud's sign-in screen opens the same account.

A GitHub or Google account that is already connected to another Cahaves account is refused with "That account is already connected to another Cahaves account." It is never moved from one account to another. Removing a method on the account screen takes that way in away at once, and the last method cannot be removed while no password is set.

The account screen's Your products section has a tile for Cloud. Opening it signs you in to Cloud as that account, with no button to press. This is the way in for a Cahaves account that signs in with a password and has no GitHub or Google connected, because Cloud's own screen has no password field.

If your Cahaves session has ended by the time the tile is opened, Cloud's sign-in screen says "Your Cahaves session has ended. Continue with GitHub or Google to sign in again."

Settings, General (or Profile in the account menu) shows Account details: your picture, "Signs in with" followed by your sign-in methods, your Name and your Email address. They are read only in Cloud. Change them on your Cahaves account screen; Cloud reads them again each time you sign in.

A Cloud session lasts 30 days from the moment you sign in. Using the console does not extend it. When it ends, the next screen you open is the sign-in screen, and nothing you made is affected.

Open the account menu at the top right and press Sign out. It ends Cloud's session in this browser and returns you to the sign-in screen. It also forgets which organization the console was in, so the next sign-in in this browser opens your oldest. If it cannot reach Cloud, a message at the bottom of the window says so and you stay signed in.

Sign out does not sign you out of your Cahaves account screen, of GitHub or of Google. Opening Cloud's tile on the account screen afterwards signs you straight back in. To end those sessions as well, sign out on the account screen and with the provider.

A failed sign-in returns to the sign-in screen with one sentence in red, such as "That sign-in expired before it finished. Start again." or "Sign-in is unavailable right now. Try again in a minute." Sign-in problems lists every sentence, what causes it and what to do.

• Members. A Cloud account is one person. It can hold several organizations, but an organization has no members, invitations or roles yet: you are the only one who signs in to yours.

• API keys. The API accepts only the session your browser holds. Authentication has the details.

• Closing an account. The console has no control that closes an account, or that deletes an organization. You can delete your services and projects yourself; for anything else, see Support.