Run apps for an organization

An organization can own apps and other deployments, apart from the ones on your account. App Deployment in the sidebar lists them beside your own, and the organization's App Deployment tab lists them too. Both open the same pages your own deployments have, for releases, domains, variables, billing and settings. Owners and admins make changes there. Every other member of the organization sees the same pages without the controls that change anything.

• You need to be a member of the organization. To create, deploy, change or delete its apps, you need the owner or admin role; to change how they are billed, the Billing role or above (Organization roles and permissions).
• Web services and sites need App Deployment open on the platform. While it is not, the organization has no App Deployment tab, and only its game servers and databases are listed.

From the sidebar:

1. In the dashboard, select App Deployment.
2. Each card names the organization under the deployment's name, and the table's Owner column does too. To see one organization's alone, choose it under Owner, which starts at All owners.
3. Select a deployment to open its page. The line under its name starts with the organization's name, which opens the organization.

From the organization:

1. Go to Organizations and open the organization.
2. Select the App Deployment tab, after Cloud Compute.
3. Select a deployment to open its page.

The list works as your own App Deployment list does, with the same tiles, filters, search and sorting, except the Owner menu, which only the sidebar list has (Your deployments). A deployment's page has the tabs your own have, and each one works as its guide describes:

• Releases: Deploy, promote and roll back releases.
• Domains and Networking: Add a domain and protection.
• Variables: Environments and variables.
• Usage and Billing: How App Deployment is billed.
• Settings: Change or delete a deployment.

A game server or a database the organization owns has its server's tabs too, such as Console, Files and Snapshots, for its owners and admins. They open the server as its owner does, including SFTP with their own email address and password.

In the dashboard, select For an organization on App Deployment, then the organization, or select New deployment on the organization's App Deployment tab. The menu lists each organization where you are an owner or admin. The configure page says Ordering for and the organization's name (Order a deployment).

With the Apps API, use POST /api/v1/orgs/{org_slug}/apps and the token of an owner or admin. The app belongs to the organization, not to the member who created it, and it appears under App Deployment and on the organization's App Deployment tab. When the organization has as many apps as it may, the request answers 409 with app_limit.

With a role below admin (Billing, any support tier or Read only), you can open every deployment and read its releases, build logs, domains, variable names and settings. A deployment opened from App Deployment says Your role in <organization> is <role>, so you can look at this deployment but not change it. An owner or admin of <organization> makes changes., and on the organization's tab the top of the tab says Changes here need an owner or admin; the tables below are read-only for you. The pages leave out every button and menu that changes something, such as Deploy a branch…, Rebuild… and Redeploy…. If you open the address of one of those pages, such as the one that deploys a branch, it says that only owners and admins can use it. A game server's or a database's own tabs, such as Console and Files, are left out: they are for owners and admins, as a Cloud Compute console is. To make changes, ask the owner or an admin to give you the admin role (Change a member's role).

The Billing tab and what a deployment costs are for the Billing role and above. Below it, the tab says Billing in <organization> is for the Billing role and above.

An organization's apps work as your own do, with these differences:

• Every member of the organization can see them, under App Deployment and on the organization's tab. Only owners and admins can change them.
• They are billed to the organization's owner. Members with the Billing role or above see and change how each one is billed, but never the owner's credit balance or the spend limit across the owner's account (Who can change billing).
• They count towards the organization's app limit, which is separate from your account's (Apps API limits).
• Each change a member makes goes into the organization's audit log, on the Audit tab for owners and admins (Read the organization audit log). Its actions start with app. or deployment., such as app.deploy and deployment.billing_changed, and the Actor column names the member. Releases that a push starts are not in the log; the app's Releases tab shows them.
• An app stays with the owner it was created for. No request moves it between your account and an organization.
• The organization cannot be deleted while it has apps. The Delete organization card on its Settings tab lists them as, for example, 2 apps still running, with Delete them first; their replicas and domains go with them. Delete each one from its own page's Settings tab (Change or delete a deployment).
• While you work in another account from its team, App Deployment lists that account's deployments only. Switch back to your own account to see the organization's.

The organization's apps are under App Deployment, with the organization's name on each of its cards, and on its App Deployment tab. Every member of the organization can open them. Owners and admins deploy and change them, and the other members read them.

An organization's deployment is not under App Deployment

You are working in another account from its team, or you are not a member of the organization. Switch back to your own account, or ask the organization's owner to add you (Add a member). A suspended organization's deployments are not listed.

The organization has no App Deployment tab

App Deployment is not open on the platform, or the dashboard could not reach it when the page loaded. Reload the page to ask again.

A button such as Deploy a branch… is missing

Your role in the organization is below admin. The notice under the deployment's name, or the badge next to the organization's name, shows your role.

The limit is 20 apps. Delete one before creating another

The organization has reached its app limit. Delete an app it no longer needs, then create the new one.

No such organization

You are not a member of the organization, or it does not exist. Ask its owner to add you (Add a member).

• The Apps API
• Create an app with the Apps API
• App Deployment
• How App Deployment is billed
• Move an organization's deployment to usage billing
• Organization roles and permissions
• Manage members and roles
• Read the organization audit log
• Delete an organization

An organization's apps are under /api/v1/orgs/{org_slug}/apps. The requests take the same bodies and give the same answers as your own apps under /api/v1/client/apps (Apps for an organization), and each task page shows its request with the organization's path. GET /api/v1/orgs/{org_slug}/apps lists the organization's apps:

curl "https://api.coritan.com/api/v1/orgs/acme/apps" \
  -H "Authorization: Bearer $CORITAN_TOKEN"

Each app in the answer has owner set to {"type": "organization"}. In the answer to GET /api/v1/orgs/{org_slug}/apps/regions, limits.apps_used counts the organization's apps, not yours (Regions, sizes and limits). The organization's deployments of every kind are under /api/v1/orgs/{org_slug}/deployments, and their billing under /api/v1/orgs/{org_slug}/billing (How App Deployment is billed).

To list every organization's deployments beside your own, as App Deployment does, add include_organizations=true to GET /api/v1/client/deployments:

curl "https://api.coritan.com/api/v1/client/deployments?include_organizations=true" \
  -H "Authorization: Bearer $CORITAN_TOKEN"

Each of an organization's deployments in the answer has owner set to {"type": "organization", "slug": "acme", "name": "Acme Hosting", "role": "admin"}, with your role in it, and your own have {"type": "user"}. Read and change an organization's deployment under /api/v1/orgs/{owner.slug}/deployments/{uuid}. Only your own sign-in may ask for organizations: an API key, or a request that acts for another account with X-Coritan-Account, answers 403 with own_sign_in_only.

Any member's access token can read, and a request that changes something needs the owner or admin role. These answers are particular to the organization's paths: