Skip to main content
Environments are isolated namespaces within your organisation. Each environment has its own auth provider configuration and a separate set of SDK credentials. Changes to one environment have no effect on another.

​
Why Use Multiple Environments

Keeping auth configurations separate means you can:
  • Test new provider credentials against a staging environment without touching production users
  • Use permissive CORS settings locally without opening up your production origin
  • Swap auth providers in development before rolling the change forward

​
Typical Setup

development   → Dynamic dev credentials, localhost CORS
staging       → Dynamic staging credentials, staging origin
production    → Dynamic prod credentials, production origin(s)
Each environment maps to a separate entry in your auth provider’s console. Always use the matching credentials — a production JWT presented to an environment configured with development credentials will fail validation.

​
Environment Credentials

Each environment has a unique set of credentials used to initialise the SIS SDK or construct API calls scoped to that environment.
FieldDescription
Environment IDUsed in SDK initialisation and API calls
NameInternal identifier (e.g. production) — lowercase, no spaces
LabelUser-facing label (e.g. Production) — shown in the dashboard

​
Managing Environments

Creating — Go to the Environments page and click New environment. Enter a name and label. Renaming — Select an environment and update the name or label from the environment settings. Deleting — Environments with active API keys or auth configuration must have those removed first. Deleting an environment is permanent and cannot be undone.