Know what each connection grants.
Organization connections and project settings do different jobs. A source-control grant permits work against repositories; describing a cloud environment grants no access to that account.
GitHub App
An administrator connects the provider, then an authorized person links a repository to a project. Planning, implementation, maintenance and code-derived documents use that repository.
Read setup instructions- Permission and scope
- The installed App and granted repository scopes bound access.
- What it does not do
- The project link is separate from organization setup. A deployment record is mirrored from GitHub; the connected pipeline executes it.
Internal package registries
Connect the registry that serves your organization’s packages, including a published design system. Agents can install the package and its versioned types.
Read setup instructions- Permission and scope
- Organization-level registry configuration is administrator work.
- What it does not do
- A brand document or repository reference is not the same thing as an installed, versioned package.
Microsoft Entra ID
Connect a directory against a domain your organization has verified. Configure the sign-in requirement with the documented owner recovery exception.
Read setup instructions- Permission and scope
- Directory configuration is distinct from membership, organization roles and team access.
- What it does not do
- Google sign-in is a separate convenience, not a connected customer directory. SAML and SCIM provisioning are not current offers here.
Environments and App URLs
Describe development, staging or production, its target cloud and region, and its public App URL. URL availability checks use that field.
Read setup instructions- Permission and scope
- The environment describes where the software runs; it does not connect a cloud account or grant infrastructure permissions.
- What it does not do
- Your pipeline deploys the software. An App URL check does not provide infrastructure monitoring or on-call coverage.
Browser beacon
Install the beacon with the environment’s generated DSN to collect browser experience signals. Installation can be a separate initiative through planning, build and review.
Read setup instructions- Permission and scope
- The DSN identifies the environment’s telemetry destination. Review collection and privacy requirements for your application.
- What it does not do
- Without the beacon, experience data is not set up. New environments learn a baseline; absent or stale samples are not a healthy result.