---
title: 'Manage projects'
description: 'Find project identifiers and manage names, appearance, and application connections.'
---

# Manage projects

A project belongs to a team and has its own schema, data, members, API configuration, and service settings. [Create a project](/docs/getting-started/create-project) before configuring Studio.

## Project ID

Open **Settings → General → Project ID**. Copy this value into the application's `projectId`. Use the ID when selecting the hosted API endpoint and deploying with the CLI. A display name is not a substitute for the ID.

## Project name

Use General settings to give the project a recognizable name. Studio's `title` is configured in application code and may remain different after a Dashboard rename. If users are confused, align both names deliberately.

## Project avatar

The avatar helps distinguish projects in selectors. Changing appearance does not change the schema, project ID, or hosted Studio URL. Use a non-sensitive image that remains recognizable at a small size.

## Connect people and applications

Grant [membership](/docs/dashboard/members), deploy the [schema](/docs/schema/deployment-and-migrations), and publish the [Studio application](/docs/deployment). Share the application URL with invited users. API tokens belong in trusted server environments rather than public configuration files.

For pauses, read-only restrictions, and deletion, see [project lifecycle](/docs/dashboard/project-lifecycle). Review the selected project and team before making an administrative change.


---

[View full sitemap](/docs/sitemap.md)