Configuration files

The settings in the custom /custom/stwebclient.config.json configuration file override the settings in the default C/config/default.config.json configuration file.

Note You must not modify the C/config/default.config.json configuration file. You must make your changes in the /custom/stwebclient.config.json configuration file.

The default configuration file has the following top-level keys:

{
  "features": {
    ... // enabling/disabling features
  },
  "i18n": {
    ... // adding/modifying languages (internationalization)
  },
  "branding": {
    ... // branding
  }
  "transferQueue": {
    ... // transfer queue settings
  },
  "views": {
    ... // views configuration
  }
  "liteMode": {
    ... // enabling/disabling liteMode
  },
  "passwordManagement": {
    ... // forgot password and change password settings
  },
  "accessControl": {
    ... // enabling/disabling access to some UI functions
  },
  "sessionManagement": {
    ... // client session management settings
  },

"disclaimer":{

    ... // disclaimer settings
 }
}

The custom stwebclient.config.json configuration file must have the same structure as the default.config.json configuration file, but including a key in the custom configuration file is optional. If a key is not present in the custom configuration file, the key in the default configuration file is used.

For example, the following custom stwebclient.config.json configuration file only has a branding key.

{
  "branding": {
    ...
  }
}

In this example, the features and internationalization configurations are provided by the keys in the default.config.json file, and the branding configuration is provided by the key in the stwebclient.config.json file. Keys not included in the stwebclient.config.json file are inherited from the default.config.json file.

Related Links