> ## 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.

# Your organisation's name, logo and idle sessions

> Rename your organisation, set its logo, copy its ID, and choose how long an idle session lives.

Open **Settings**, then **General** under **Organisation**.
Only admins see this page.
A member who opens it sees a notice that it is for admins, and the API refuses a member's changes too.

## Rename your organisation

Type the new name in **Name** and select **Save name**.
Every member sees the new name in the organisation switcher and the top bar the next time a page loads.
Your own page updates as soon as the name is saved.

A name that is empty, or only spaces, is refused and the page says why.
The organisation keeps its current name.
Spaces at either end of a name are removed.
A name can be up to 256 characters.

## Set the logo

Select **Upload logo** and choose a PNG, JPEG, GIF or WebP image of up to 4 MB.
A square image works best.
The logo appears beside the organisation's name in the organisation switcher for every member.
SVG files are not accepted.
Until you upload one, the switcher shows the organisation's initials.

## Copy the organisation ID

**Organisation ID** shows the ID of your organisation, with a **Copy** button beside it.
Quote it when you contact support or call the API.

## How long an idle session lives

**End idle sessions after** sets how long a session can sit idle before it ends.
Choose from 1 hour, 1 day, 3 days, 7 days, 14 days or 30 days.
A new organisation uses 7 days until an admin chooses another.
Nothing shorter than an hour can be chosen.

* **Waiting on a person counts as idle.**
  A question or a plan left unanswered for this long ends the session too.
* **An ended session cannot be started again.**
  Start a new session to carry on.
* **A change applies from each session's next idle period.**
  A session that is idle when you change the setting keeps the end time it already has, so lowering the setting never ends one early.
  A session that wakes for a message and then goes idle again is on its next idle period, so it uses the new setting.
* **No running session ends because of a change.**
  The setting only counts time a session spends idle.
* **A run from Linear that is waiting on your decision about review findings always keeps at least 24 hours**, even when you choose 1 hour.

After you lower the setting, the page reminds you that sessions idle now keep their end time.
The choice saves as soon as you pick it.
If it cannot be saved, the page says so and shows the value your organisation still has.

There is no setting for how long a running session can go on, or for when an idle sandbox goes to sleep.
See [Starting and following a session](/guides/starting-and-following-a-session) for what a session shows when it ends.

## From the API

These calls need the **admin** role.
A member's call is refused with `forbidden`.

```bash theme={null}
curl -s https://api.scaling.cloud/organisation/session-settings \
  -H "Authorization: Bearer $ACCESS_TOKEN"
```

```json Response theme={null}
{ "idleSessionLifetimeSeconds": 604800 }
```

`PUT` the same path with one of `3600`, `86400`, `259200`, `604800`, `1209600` or `2592000`.
The answer is the value now in force.
Any other value, and any other field in the body, is refused with `invalid_request` and nothing changes.

```bash theme={null}
curl -s -X PUT https://api.scaling.cloud/organisation/session-settings \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"idleSessionLifetimeSeconds": 86400}'
```

```json Response theme={null}
{ "idleSessionLifetimeSeconds": 86400 }
```

To rename the organisation, `PUT /organisation/name` with a `name`.
The answer is the name your organisation now holds, with the spaces at either end removed.

```bash theme={null}
curl -s -X PUT https://api.scaling.cloud/organisation/name \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"name": "Acme Labs"}'
```

```json Response theme={null}
{ "name": "Acme Labs" }
```

To set the logo, `PUT /organisation/logo` as `multipart/form-data` with the image in a field named `file`.
It answers `204` with no body.

```bash theme={null}
curl -s -X PUT https://api.scaling.cloud/organisation/logo \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -F "file=@logo.png;type=image/png"
```

## When it fails

| Code | Status | What it means here |
| - | - | - |
| `forbidden` | 403 | You are a member and this needs an admin |
| `invalid_request` | 400 | The lifetime is not one of the choices, or the body has a field that is not known |
| `identity_change_refused` | 422 | The name is empty, or the logo is not a PNG, JPEG, GIF or WebP image of up to 4 MB |
| `identity_change_not_done` | 503 | The change did not go through on our side, so try again in a moment |

Branch on `code`, never on `message`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.