Organizations

An organization is what your projects and your bill belong to. Your account starts with one. If you run several companies, contact Cahaves to enable additional organizations under the same sign-in. Each has its own projects, its own workspace and its own bill, so what one runs and owes never shows in another.

An organization holds its projects, with every service, deployment, domain, volume and backup in them. The console works in one organization at a time: its lists, its search and its Dashboard show that organization's alone, and the address of a project in another one reads "Nothing in this organization matches this address".

Each organization has its own workspace, its space on the platform that its services run under, prepared when the organization is created.

Each also has its own bill. It pays with its own card, which Paddle keeps, or by the invoices Cahaves agrees to send it, and it has its own monthly limit and its own statement for each month it ran anything billable. A stop for billing is its own too: an organization whose month goes unpaid, or reaches its limit, has its paid services stopped, and your other organizations do not. Billed by invoice, it is a client of its own in Cahaves' invoicing, and its invoices are addressed to it, with what its Billing details say. Billing covers each part.

Everything the console shows belongs to an organization, so a new account makes one first. After your first sign-in, including GitHub or Google, the console opens on Name your organization. Type an Organization name, such as your company's, then press Create organization. The name starts empty and is required. The Dashboard opens in the new organization and says "Your workspace is still being prepared." until its workspace is ready. Your workspace is still being prepared covers a wait that does not end.

An account made before organizations already has one. It carries the name on your account, or the part of your email address before the @ when the account has no name, and it holds everything the account had: its projects, its card or invoices, its limit and its statements.

Choose Contact us in the organization switcher, or write through Support, to ask for additional organizations. Cahaves enables them on your account. Staff can also create an organization for you and link its invoicing client.

Once enabled, open the switcher at the top of the sidebar, where Organization sits above the name of the one you are in, and choose New organization. The dialog says it "starts with no projects and is billed on its own". Type an Organization name and press Create organization. The console moves to the new organization, on its Dashboard, while Cloud prepares its workspace as it did the first one's.

An enabled account can own up to 10 organizations. Accounts already holding several keep them. If Cahaves turns additional creation off, your existing organizations stay available; you can still switch between them and rename them. A name is 1 to 80 characters: each run of spaces in it counts as one space, and spaces at either end are dropped. No two of your organizations share a name, whatever the capitals, though another person's organization may have the same name as one of yours.

The switcher's menu lists Your organizations, with the one the console is in marked. Choose another to move the console to it: its Dashboard opens, and the line under the title names it. On a phone or a narrow window, the switcher sits at the top of the drawer opened with the button at the top left. Organization settings, at the foot of the menu, opens the settings of the one you are in.

The console keeps your choice in this browser. Every open tab follows a switch from the next page it opens, so a tab left on a project of the organization you switched away from then reads "Nothing in this organization matches this address". Signing out forgets the choice, and the next sign-in opens your oldest organization.

A billing email names its organization, and its link opens that organization's billing. Every link Cloud sends, a deployment's or a domain's in a notification as much as a bill's, opens in the organization it belongs to, moving the console to it first.

Through the API, each request names its organization in a header. Authentication describes it.

Settings, then Organization, is about the organization the console is in. On its Name card, type the new Organization name and press Save name. A message such as "Renamed to Kopi Tiga." confirms it, and the switcher follows. A new name is held to the same rules as a first one, apart from the limit of 10. The organization's id, its projects and their addresses do not change.

The same page shows the Organization ID, with a button that copies it, to give support when you write about that organization, and What belongs to it: what is the organization's, and what stays yours.

Some things belong to you rather than to an organization, and work the same in every one of yours:

• your sign-in and your Cloud session, so one sign-in reaches all your organizations (Sign in and your Cahaves account);

• your SSH keys, which open a shell in a running service of any of your organizations (SSH access);

• your git providers: a GitHub connection deploys in any of your organizations (Deploy from GitHub);

• your notification channels, which hear from every organization, and the automatic account emails, which go to your one address (Notifications);

• your backup destinations: platform backup storage serves all your organizations, while each keeps its own schedules and backups (Backups).

Cahaves suspends or bans an account, never a single organization. A suspension stops the running services of every organization you own and refuses changes in all of them until Cahaves lifts it, and a ban stops you signing in at all. Suspended by Cahaves says what a suspension stops and what it keeps.

What an organization owes works the other way: an unpaid month, an overdue invoice, a missing card or a month at its limit refuses new paid work in that organization alone, and your others carry on as they are. What needs a card lists each case.

It can also stop that organization's paid services, and only that organization's. A failed charge, a month closed with no card, an overdue invoice or paid services run with no card on file does once its grace period ends, on the date Cloud emails you, and the month to date does once it reaches the monthly limit. The console then marks the organization's paid services Stopped for billing. Your other organizations keep running, and so do your free application and free database, in whichever organization they are, this one included. Nothing is deleted while the stop lasts. Once the month is paid or a card added, or for the limit once the next month begins or the limit is raised, Cloud starts again what it stopped. Stopped for billing covers the dates, the emails and what clears each cause. A stop for an unpaid month or for no card that lasts 30 days archives the organization's paid services, which Archived for billing describes.

The free allowance belongs to you, not to each organization, so a second organization does not bring a second one. Your first nano application in the shared pool and your first nano database, counted across all your organizations, are the free ones, each in whichever organization it runs. First means the oldest that exists now, so a nano service you create in a new organization is free only when you have no older one of its kind in another. The free allowance says what each covers.

• Members. An organization has one owner, the person who made it, and nobody else signs in to it. There are no invitations or roles.

• Moving a project. A project stays in the organization it was created in, with everything in it.

• Deleting an organization. One you no longer use stays in the switcher, and counts towards your 10.