# Institution and application setup

Configure environments, applications, service connections and comparison sources.

## Roles and operating scope

A system administrator creates the institution and its initial administrator. Institution administrators work within their own scope. Check the institution and environment after signing in. If scope changes in another tab, reselect it when prompted before continuing.

## Environments

Under Setup → Environments, create an environment such as Test with a meaningful name and short code. Create separate credentials for production. Check the active environment before saving definitions.

## Applications

Add the product or workflow to be observed under Applications. Use a name that business users can recognise. SDK technology is selected per actual service; one application can include several programming languages.

## Services and connections

Define the actual components under Services, then connect them to the appropriate applications. Reuse an existing service identity for a shared service. Specify the entry service and actual entry-point match. Cancelling a service definition and disconnecting it from one application have different effects.

## Integrations

On Integrations, confirm the environment, application and service before downloading the SDK package and service configuration. A download is not evidence of a working integration. After installation, send a new request and check actual receipt under Product health and Transaction records.

## Comparison setup

After receiving observations, select fields with a corresponding institutional record under Comparison definitions. Then configure a read-only connection and field mappings under Institution record sources. See [Comparison definitions](https://www.sigillum.cloud/developers/verification/definitions/).