Supported directory variables

Applies to managed Chrome Browsers and Chrome devices.

As an admin, you can use variables to configure file paths, such as the directory that Chrome uses for storing user data. That way,  you don't need to set a hard-coded path.

For example, to store profile data under the user local application data on Windows, set the UserDataDir policy to ${local_app_data}\Chrome\Profile. For most Microsoft Windows 7 and Vista installations, this resolves to C:\Users\CurrentUser\AppData\Chrome\Profile.

Chrome Browser user profiles are not backwards-compatible. If you try to use mismatched profiles and Chrome Browser versions, you might experience crashes or data loss. For details, see Common Chrome Browser issues.

Tips for setting paths in policies

  • Policies that include paths where Chrome stores data are platform-dependent. Some policies are only available on certain platforms while others can be used across all platforms.
  • Paths should be absolute. This helps to avoid errors caused by applications starting in different locations on different occasions.
  • Each variable can occur only once in a path.
  • Where possible, most policies will create a path if it doesn't already exist.
  • Using network locations for some policies can lead to unexpected results. For example, the user profile is not backwards-compatible. So, running a different version or channel of Chrome Browser with the same profile might corrupt your profile.

List of supported path variables

Path variable Description Example
All platforms

${machine_name} 

The machine name. The domain name can be included.

john.ab1.solarmora.org

johnnyabc

${user_name}

The user who is running Chrome (respects suids). 

johndoe

Apple® macOS® only

${documents}

The current user’s Documents folder. /Users/johndoe/Documents

${users}

The folder where user’s profiles are stored. /Users

Microsoft® Windows® only

${client_name}

The name of the client PC connected to a Remote Desktop Protocol (RDP) or Citrix session.

Take into account that this variable is empty if used from a local session. So, if used in paths, you might want to prefix it with some text so that part is guaranteed not to be empty.

C:\chrome_profiles\session_${client_name} produces:

  • For local sessions—
    C:\chrome_profiles\session_
  • For remote sessions—
    C:\chrome_profiles\session_somepcname

${documents}

The current user’s Documents folder.

C:\Users\Administrator\Documents

${global_app_data}

The system-wide application data (AppData) folder.

C:\AppData

${local_app_data}

The current user’s AppData folder.

C:\Users\Administrator\AppData\Local
 

${profile}

The current user’s home folder.

C:\Users\Administrator

${program_files}

The current process’s Program Files folder. Depends on whether it is 32-bit or 64-bit process.

C:\Program Files (x86)

${roaming_app_data}

The current user’s Roaming AppData folder.

C:\Users\Administrator\AppData\Roaming

${session_name}

The name of the active session. Useful for distinguishing multiple remote sessions that are simultaneously connected to a single user profile. 

Local desktop sessions—WinSta0

${windows}

The Windows folder.

C:\WINNT

C:\Windows

 

Was this helpful?
How can we improve it?