---
title: "Settings"
description: "Renaming organizations and projects, and deleting projects."
---

`arkor.ai/<org>/settings` manages the organization and its projects.

![The organization settings page](/images/cloud/settings-light.png "www.arkor.ai/oddphin-org/settings")
![The organization settings page](/images/cloud/settings-dark.png "www.arkor.ai/oddphin-org/settings")

## Organization

You can change the organization's **display name** and **URL slug**. Slugs are lowercase letters, digits, and hyphens, at least 3 characters.

Changing the slug moves every dashboard URL under the organization (`arkor.ai/<new-slug>/...`) immediately. Old links stop working, and CLI configurations that reference the old slug need updating. Endpoint URLs are not affected; `*.arkor.app` subdomains belong to endpoints, not organizations. Once the organization's [public profile](/docs/cloud/public-projects) is enabled, the slug is frozen — it is the public URL, and renaming would free it for someone else to claim.

## Projects

Each project row supports:

- **Rename** — display name and slug (slug rules as above, minimum 2 characters). Renaming a project moves its dashboard URLs; endpoint URLs are unaffected.
- **Delete** — permanently removes the project with everything in it: training jobs and their artifacts, endpoints, and stored run history.

Deletion is refused while the project has queued, running, or preempted jobs; cancel them first from the [Jobs tab](/docs/cloud/training). The confirmation dialog states the scope before anything happens, and the deletion cannot be undone.

## Members and roles

Every account gets its own organization when it signs up, and that organization holds exactly one person — you, as its owner. There is nobody else to list, so it has no **Members** tab. The tab appears for organizations shared by several people, which are not available yet.

Roles apply to every organization all the same, yours included. Two of them exist:

- **Owner** — everything a member can do, plus changing the organization's name, slug and profile fields, publishing the organization's public profile, and deleting projects.
- **Member** — creating and renaming projects, submitting and cancelling training jobs, creating endpoints and API keys, and running inference. Members can also set an individual project's visibility, so once an owner has published the organization profile, a member can make a project publicly visible, and private again. The organization-level switch is the one that cannot be reversed.

Roles are enforced by the API, not just the dashboard: a request that a role does not permit is refused with `403` and the error code `insufficient_org_role`, whichever client sends it.

## Public profile and public pages

Settings is also where you publish the organization profile and manage each project's visibility, model card, and showcase adapter. See [Public projects & model cards](/docs/cloud/public-projects) — note that publishing the organization profile is permanent.

The **Profile** tab holds the profile fields shown on the public page — avatar, bio, company, location, and links. See [Organization profile](/docs/cloud/profile).