---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/application-development

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Single sign-on

# Single sign-on for Developer Sandboxes {#ariaid-title1}

Release version: Australia  
Updated October 26, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Sandboxes use the same login credentials as the base instance, including single sign-on (SSO) when it's enabled there. Set the required properties on the base instance so developers can use SSO to access sandboxes.

## How sandboxes authenticate users {#dev-sbx-sso__section_sso_how}

Sandbox users log in with the same credentials as the base instance. If you use SSO on the base instance, sandboxes use the same SSO configuration, so developers don't need separate local logins for sandboxes.  
Note:  
Instances with vanity URLs support SSO.

## Enabling SSO for sandboxes {#dev-sbx-sso__section_sso_enable}

Developers can access sandboxes using instance credentials and SSO.  
The following properties must be set in the base instance before developers can use SSO to access sandboxes:

* Disable ACR: `sys_property glide.sso.acr.enable = false`
* Enable SSO: `glide.authenticate.multisso.enabled = true`
{#dev-sbx-sso__ul_bjw_2ph_lgc}