# Configure a Project

Project settings govern the development resource. Choose instructions and reusable resources that help the application work. Connectors and MCPs require authorized assignment to the Project; simply connecting an account to a Workspace does not let a Project invoke it.

## Keep scopes clear

Development secrets and services belong to the Project. A Site has its own production configuration and credentials. Creating a Project, importing content, or remixing a template does not create a Site or transfer live connection authority. Review [configuration](/docs/configuration/overview) and [Permissions](/docs/concepts/permissions) before adding sensitive access.

Configuration changes apply to future work under Workspace policy. Check the Project's budget and [usage](/docs/billing/usage), especially for managed services or scheduled work. Release-specific choices belong to the selected [Site](/docs/sites/releases).

## Example: prepare development access

For a portal that reads from an external service, choose the supported Connector, authorize the intended account, and assign it to this Project’s development scope. Add the project-specific Instructions and reference Files separately.

Verify a small read against the intended account before building the full workflow. Use [Connections](/docs/configuration/connections) for authorization and [Site Runtime](/docs/sites/runtime) for the separate production context.

## Supply context in the Composer

Attach a specification as a [Source](/docs/composer/controls#attachments) for a particular change. Keep reusable product background in [Files](/docs/configuration/files) and development conventions in [Instructions](/docs/configuration/instructions). Review the owner shown by a [configuration command](/docs/composer/slash-commands) before saving a change.