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 and Permissions before adding sensitive access.
Configuration changes apply to future work under Workspace policy. Check the Project's budget and usage, especially for managed services or scheduled work. Release-specific choices belong to the selected Site.
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 for authorization and Site Runtime for the separate production context.
Supply context in the Composer
Attach a specification as a Source for a particular change. Keep reusable product background in Files and development conventions in Instructions. Review the owner shown by a configuration command before saving a change.