Environment Variables

A number of different environment variables exist to help control the behavior of the Toolkit Startup.



Overrides the location where Toolkit stores data, which includes bootstrap data as well as bundle cache, cached thumbnails and other temp files.


Allows you to store your configuration file somewhere else on your computer or on your network. See the documentation here.


Low level bypass to set the configuration desciptor URI that the bootstrap API should load up. Useful in complex workflow development scenarios.


Controls debug logging.



Specifies which authentication method should be selected if none are selected yet. Available values are credentials, qt_web_login, and app_session_launcher.

Note: this variable does not override the session cache. If a valid method has been recorded in the session cache, this method will be prioritized over the one provided by SGTK_DEFAULT_AUTH_METHOD.


Allows the user to bypass the HTTPS requirement for the authentication methods. This is not recommended and should only be used in combination with legacy ShotGrid local installations.


Always display the traditional authentication (login and password fields) in the login window dialog even when the Flow Production Tracking site has other authentication methods enabled.


Provide a custom application name when using the “App Session Launcher” authentication instead of relying on an autodetected name.


Indicates the default Autodesk Identity account to use to pre-fill the login window dialog. This is purely for the convenience of the user and has no other use or side-effects.


When the user’s Autodesk Identity account is on an email domain that uses SSO for authentication, setting this variable will allow the bypass of the initial Autodesk Identity window. This saves the user from entering their email twice. The expected format of this variable should be an email domain, like gmail.com, mystudio.com, autodesk.com, etc.. Other than that, this variable has no other use or side-effects.

Bundle cache


Path that lets a user specify bundle cache fallbacks to go look for a bundle in case it is now found in the bundle cache. This is part of the Bootstrap API. Also see Flow Production Tracking Integrations Admin guide.


Overrides the path to the main bundle cache, e.g. the location where the Descriptor URI will download bundles.


Setting this to 1 will disable any Flow Production Tracking Appstore access. No attempts to connect will be carried out. This option can be useful in cases where complex proxy setups is preventing Toolkit to correctly operate.

File resolving


Specifies your local storage root on different operating systems. See Resolving local file links.


Resolves a file:// URL on different operating systems. See Resolving file URLS.

Thumbnail display for Flow Production Tracking


When specified the old thumbnail cropping behavior will be used. See Configuring the thumbnail display in Flow Production Tracking