# Site access

Choose who may reach a Site: **Restricted**, **Workspace**, or **Public**. This platform visitor policy controls reachability. It does not grant Site management, source editing, Workspace administration, or access to a connected Agent.

## Two layers of permission

The hosted application may also require its own login and business permissions. Passing the Site visitor gate does not make someone an application administrator; signing into the application does not make them a Project builder or Site manager.

Invite a collaborator to manage the Site only when they need that role. Source editing and release authority are separate, so review each person's access at the resource where they act. See [Workspace sharing](/docs/workspaces/sharing) and [Site releases](/docs/sites/releases).

## Example: a public portal with private records

A Public Site can expose its landing page to visitors while the application requires login before showing customer records. The application must enforce which records each signed-in user can read or edit.

The Site audience controls reachability; it does not implement the application’s business permissions. Review [Permissions](/docs/concepts/permissions), [Project development](/docs/projects/development), and [Security](/docs/services/security).

## Check both layers

Review the Site address as an intended visitor and as someone outside the intended audience. For an application with private records, also check which records an authenticated application user can read and change. Successful page access alone does not establish that those record permissions work.