> ## Documentation Index > Fetch the complete documentation index at: https://docs.scaling.cloud/llms.txt > Use this file to discover all available pages before exploring further. # Setting up your organisation > The first thing an admin sees in a new organisation: install the GitHub App, add your Anthropic key, pick a repository and check its scaling.yml. A new organisation has nothing to send an agent to yet. Setup walks an admin through what it needs, one step at a time, on a page of its own. Each step shows where it stands, and you can leave and come back to it. ## What you need * The **admin** role in your organisation. Creating an organisation makes you its admin. * A GitHub account that can install an app on the repositories you want to use, or an owner who can approve the request. * An API key from the Anthropic Console. * A `scaling.yml` file at the root of the repository's default branch, or a few minutes to commit one. ## Where setup starts When you create an organisation you land on setup at the first step. On the left is the step you are on. On the right, on a wide screen, are all four steps with what each has settled so far. On a narrow screen, such as a phone, the list is hidden and the foot of the page says which step you are on, for example **Step 3 of 4**. Setup is finished once the config file of one repository checks out. Until then, anyone in the organisation who opens the app is brought to setup: an admin to the first unfinished step, a member to a page saying an admin has to finish. ## Step 1: install the GitHub App Choose **Install on GitHub**. GitHub asks which repositories the app may see. Choose only the ones you want Scaling to work on, and approve. GitHub sends you back to setup, which confirms the installation and shows the account it is installed on and how many repositories it can see. Choose **Continue**. To do this step with the API instead, see [Connecting a repository](/guides/connecting-a-repository). If the installation cannot be confirmed, the step says **The installation could not be confirmed**. That happens when you cancel on GitHub, or when an owner of the GitHub organisation has to approve the request first. Choose **Try again on GitHub**, or come back once the owner has approved. Only the person who installed the app, or an admin of its GitHub organisation, can connect it to your Scaling organisation. ## Step 2: add your Anthropic key Paste your key into **API key** and choose **Check and save**. The key is checked with Anthropic before it is stored. When it is valid the step shows `sk-ant-…` followed by its last four characters. The value is not shown again. If Anthropic refuses the key, the step says so and nothing is saved. Paste a working key and try again. [Adding your Anthropic key](/guides/adding-your-anthropic-key) covers what is kept, how to replace the key later and what happens when it stops working. ## Step 3: pick a repository The step lists the repositories the installation can see, each with whether it is private or public and its default branch. With more than eight repositories, a filter appears above the list. Choose one, and choose **Continue**. A repository that is already a project is marked **Already a project**. The API does the same job: see [Connecting a repository](/guides/connecting-a-repository). If the installation can see no repositories, the step says **The installation can see no repositories**. Choose **Change access on GitHub**, give it access to at least one, return, and choose **Look again**. The same link, **Change what the installation can see**, sits under the list when the repository you want is missing. ## Step 4: check the config file The file `scaling.yml` at the root of the repository says how its stack boots in a sandbox. Setup reads it from the default branch and shows what it found: the install commands, the services, the processes and the network access the file asks for. ### A valid file When the file can be used, the step says **scaling.yml is valid** and that setup is finished. Choose **Go to runs** to open the app. From then on everyone in your organisation can open the app, and opening setup again takes you straight to it. ### No file If the branch has no `scaling.yml`, the step says **No scaling.yml on** that branch and shows a starter. Choose **Copy**, commit the file to the root of the repository, and choose **Check again**. The starter boots a single app, so change its commands to yours. ### An invalid file If the file cannot be used, the step says how many problems it has. Each one shows the key it is about, the line it is on, and what is wrong with it. Fix them on the default branch and choose **Check again**. ### The repository cannot be reached If the installation can no longer see the repository, the step says to give it access on GitHub. Do that, then choose **Check again**. If the installation was removed or suspended before your organisation was set up, setup returns you to the first step and offers to install the GitHub App again. For a suspended installation, unsuspend it under your GitHub account's installed apps instead, then reload the page. If your organisation was already set up, the app stays open. A project whose config was valid keeps your organisation set up, so people can still open the app and read past runs while you fix access on GitHub. Opening setup on its own takes you back to the app, so open `/onboarding?step=github` on the address you use for Scaling. The app does not link to it yet. It shows the first step, which offers to install the GitHub App again. For a suspended installation, unsuspend it on GitHub instead, as above. ## Coming back to a step A refresh returns you to the step you were on, or to the first one that is not finished. Nothing is lost, because setup reads what already exists in your organisation rather than keeping a separate record. A finished step on the right is a link: choose it to see that step again. A step beyond the first unfinished one cannot be opened early. ## If you are a member A member of an organisation that is not set up sees a page saying so, with the admins who can finish it and a button to email each. There is nothing for a member to do. Once an admin has a repository whose config file checks out, reloading the page gives way to the app. ## Adding another repository The steps that pick a repository and check its config work the same way for every repository after the first. Open `/onboarding?step=repository` on the address you use for Scaling. The app does not link to it yet. Choose a different repository, and it is checked in the same way. When its file checks out, the step says the repository is ready to use, because your organisation could already open Scaling. The GitHub App needs to see it first, which you change with **Change what the installation can see**. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.