In OutSystems Platform, site properties are global variables that have a constant value, or a value that does not change often. All modules are created with predefined site properties, but you can create your own.

One of the benefits of using site properties, is that you can change its value at runtime using the environment management console.

Pre-defined Site Properties

Some site properties are automatically created and handled by OutSystems Platform, namely:

User-defined Site Properties

To create a site property:

  1. Right-click on the Site Properties folder (in the eSpace tree under the Data layer);

  2. Select the Add Site Property option.

When the tenant is deployed, the site properties that you create have the default value specified.

Multi-Tenant Applications

Internally, Site Properties are stored in the cache of each Front-end Server. If the Site Property is set as Multi-tenant, it will be stored in the tenant's cache. Although this is an implementation detail, you must be aware of it due to the fact that whenever the cache is invalidated, all the site properties are also re-evaluated.

In a multi-tenant scenario, all the tenants share a common definition and just implement eSpace logic once. However, it is possible to have properties whose values are tenant-dependent. These properties are called Site properties.

You can use the pre-defined site properties or define your own properties.

Even though all the tenants share a common definition, there can be some slight differences, for example in the currency parameter. These customizations should be implemented by defining the suitable site properties.

Site properties can be used like global variables in your applications, and as a best practice you should not change their value often (either through the environment management console, or programmatically), or store large amounts of data in it. Since site properties are cached, to effectively change their value, you need to invalidate the tenant or module cache. Learn more about Invalidating the Cache.

Beware that invalidating the tenant or module cache frequently might lead to performance degradation.

Multi-Tenant Scenarios

Site properties are useful in multi-tenant scenarios, since their value can be customized per tenant. As an example, by using site properties, you can configure the currency symbol used for each tenant of your application.

Learn more About Multi-Tenancy.

Site Property Properties




Default value



Name of the Site Property.



See rules for naming elements.


Free text that describes the Site Property. You can edit the text by directly typing it in the property or in the description editor which opens by clicking



Useful for documentation purposes.

The maximum size of this property is 2000 characters.

Data Type

List of all the types supported by Service Studio. A site property cannot be of the types Binary Data, Object, Record, or Record List.



See list of possible types

Default Value


Default value for the site property.




The default value of a site property must be a literal. If Text Data Type is used, the literal can have at most 2000 characters.

The Site Property's default and effective values in the server are set to the default value defined in the eSpace, when the eSpace is published in one of the following situations:

  • It's the first time the eSpace is published;

  • The effective and default values are the same in the server but the default value has changed in the eSpace.

In any other situation, the default value is ignored.

Is Multi-tenant

Indicates whether the entity is Multi-tenant or Single-tenant.


No, if the eSpace is Single-tenant.


Yes, if the eSpace is Multi-tenant.


<not defined>, if the Site Property inherits the value set in the 'Is Multi-tenant' property of the eSpace

Learn more About Multi-Tenancy

See Also

About Session Variables