A Site is an independently accessible production destination. It serves an explicitly released revision from a Project or eligible static Chat or Agent output. The source and destination remain separate: editing a Project or file does not change what visitors see.
What a Site owns
A Site owns its active release, visitor audience, production configuration, usage, operational evidence, and recovery. Runtime Sites may operate application data and jobs; static Sites serve eligible output without giving a Chat or Agent a dynamic application backend. One source can supply multiple Sites with different permissions and production settings.
Creating a Site establishes the destination. Connect an authorized source and make an explicit release to put it into use. Start with the Site quickstart, then review access and operations.
Example: one source, two destinations
A Project can supply an internal demonstration Site and a customer-facing Site. Each destination has its own audience, active release, and production configuration. Updating one should not be treated as updating the other.
Choose the destination explicitly in Releases, configure Access, and inspect the Runtime options appropriate to that Site.