Modify BRIX Enterprise parameters

Name

Description

GLOBAL: Platform parameters.

brix365.global.host

The domain (FQDN) or IP address through which the system will be accessible.

When installing the system with a specified domain name, it is necessary to add the corresponding AAA record to the DNS server: "mybrix365.com" <-> "IP address of the machine with BRIX365".

Default value: example.com.

brix365.global.edition

The version of the BRIX application to be installed.

Default value: enterprise.

Available options: standard, enterprise.

brix365.global.ingress.hostEnabled

Enabling host in ingress (value is taken from brix365.global.host). If TLS support is enabled, the value is automatically set to true.

Important: If TLS support is not enabled, it's recommended to enable it. It is also planned to use the domain (FQDN) to access the S3 minio storage, installed in the Kubernetes cluster using charts brix365-dbs.

Default value: false.

Available options: true, false.

brix365.global.ingress.annotations

Annotations for ingress.

{"kubernetes.io/ingress.class": "nginx"}.

brix365.global.ingress.timeoutSeconds

The maximum wait time for sending and receiving a response from the server in seconds for the Ingress controller.

brix365.global.gatewayAPI.enabled

Enables the use of the Gateway API (HTTPRoute) to publish BRIX services through an external Gateway.

If enabled, traffic is routed through the Gateway API instead of Ingress.

Default value: false.

Available options: true, false.

brix365.global.gatewayAPI.parentRefs

Link to the Gateway through which BRIX will publish.

This parameter must match a previously created Gateway resource in the Kubernetes cluster.

Format:

- name: <gateway-name>
  namespace: <gateway-namespace>

Where:

• <gateway-name> is the name of the Gateway resource.
• <gateway-namespace> is the namespace in which the Gateway was created.

Example:

- name: main-gateway
  namespace: istio-system

brix365.global.gatewayAPI.envoyFilter.enabled

Enables the use of the EnvoyFilter for proper routing through the Gateway API.

Default value: true.

Available options: true, false.

brix365.global.gatewayAPI.envoyFilter.namespace

The namespace in which the Gateway is installed, for example, Istio Gateway.

Default value: istio-system.

brix365.global.gatewayAPI.envoyFilter.workloadSelector

A selector that determines which Gateway components the EnvoyFilter is applied to.

Used to bind settings to the Gateway controller.

Example: gateway.istio.io/managed: istio.io-gateway-controller.

brix365.global.kubeVersion

Override the Kubernetes version.

brix365.global.openshift

Enable support for HAProxy Ingress to work on the OpenShift platform.

Default value: false.

Available options: true, false.

brix365.global.checkdbs

Enable check of database connection when installing or updating the BRIX application.

Default value: true.

Available options: true, false.

GLOBAL: proxy server parameters

brix365.global.proxy.enabled

Enables the use of a proxy server for outgoing application connections.

Default value: false.

Available options: true, false.

brix365.global.proxy.httpsProxyCaps

HTTPS proxy address in uppercase of the environment variable (HTTPS_PROXY). Use this for some case-sensitive applications and libraries.

Value format: https://<user>:<password>@<host>:<port>/.

Example: https://proxy_user:proxy_pass@host:port/.

The default value is not set.

brix365.global.proxy.httpProxyCaps

HTTP proxy address in uppercase of the environment variable (HTTP_PROXY).

Value format: http://<user>:<password>@<host>:<port>/.

Example: http://proxy_user:proxy_pass@host:port/.

The default value is not set.

brix365.global.proxy.httpsProxy

HTTPS proxy address in lowercase of the environment variable (https_proxy). Use this for most Linux applications.

The value format is: https://<user>:<password>@<host>:<port>/.

Example: https://proxy_user:proxy_pass@host:port/.

The default value is not set.

brix365.global.proxy.httpProxy

The HTTP proxy address in lowercase of the environment variable (http_proxy).

The value format is: http://<user>:<password>@<host>:<port>/.

Example: http://proxy_user:proxy_pass@host:port/.

The default value is not set.

brix365.global.proxy.noProxyCaps

A list of uppercase addresses and subnets (NO_PROXY) for which the proxy is not used. Separate them with commas:

• Domains: for example, example.com.
• Subnet IP addresses in CIDR format: for example, 192.168.0.0/16.
• Service names: for example, localhost.

Example: localhost,example.com,127.0.0.0/8,cluster.local,linkerd.svc.

The default value is not set.

brix365.global.proxy.noProxy

This is the lowercase equivalent of the brix365.global.proxy.noProxyCaps parameter for the environment variable (no_proxy). Use this for most applications running in a Linux or Unix environment.

The format and example are the same as for the noProxyCaps parameter.

The default value is not set.

GLOBAL: TLS encryption parameters

brix365.global.ingress.onpremiseTls.enabled

Enable TLS support (Enable HTTPS).

Default value: false.

Available options: true, false.

brix365.global.ingress.onpremiseTls.secret

Name of the secret with certificates for HTTPS operation.

Default value: brix365-onpremise-tls.

brix365.global.ingress.onpremiseTls.enabledCA

Enabling the root CA certificate for HTTPS operation with a self-signed certificate.

Important: before enabling, it's necessary to install the add-on components.

Read more in Enable network encryption (TLS) in BRIX Enterprise.

Default value: false.

Available options: true, false.

brix365.global.ingress.onpremiseTls.configCA

Name of the ConfigMap with the root CA certificate for HTTPS operation with a self-signed certificate.

Default value: brix365-onpremise-ca.

GLOBAL: Monitoring parameters

brix365.global.monitoring.enabled

Enables monitoring support on the BRIX application side.

Important: Before enabling service monitoring, it's necessary to install add-on components. For more details, refer to the article Enable monitoring in BRIX Enterprise.

Default value: false.

Available options: true, false.

brix365.global.monitoring.metrics.enabled

Enables the installation of ServiceMonitor in the Kubernetes cluster for BRIX application services.

Default value: false.

Available options: true, false.

brix365.global.monitoring.metrics.all

Enables the provision of a significantly larger number of metrics in Prometheus format by the BRIX application services. It's disabled by default to prevent disruption of the entire monitoring system due to an excessive number of metrics.

Default value: false.

Available options: true, false.

brix365.global.monitoring.provisioner

Configures the supplied monitoring tools for the target platform.

Default value: k8s.

Available options: k8s, deckhouse.

brix365.global.monitoring.dashboard.enabled

Enables the installation of Dashboards (ConfigMap) in the Kubernetes cluster for BRIX application services.

Default value: false.

Available options: true, false.

brix365.global.monitoring.alerts.enabled

Enables the installation of PrometheusRule (CRD) in the Kubernetes cluster for BRIX application services.

Default value: false.

Available options: true, false.

brix365.global.monitoring.jaegerAgentAddress

Enables sending traces to the Jaeger agent at the specified address.

Default value: jaeger-agent.monitoring.svc.cluster.local:5775.

brix365.global.monitoring.jaegerCollectorEndpoint

Enables sending traces directly to the collector to the specified address. Has a priority over global.monitoring.jaegerAgentAddress.

Default value: http://tempo.monitoring.svc.cluster.local:14268/api/traces.

global.monitoring.lowcode.metricExportEnabled

Enables the export of brix365_telemetry_* metrics, which are recorded in the performance report, to the Prometheus storage for their visualization using Grafana.

Default value: false.

Available options: true, false.

brix365.global.monitoring.externalRmqMetrics

Enable RabbitMQ metrics for the HPA (Horizontal Pod Autoscaler).

Available values: true, false.

brix365.global.monitoring.rmqExporterVhost

Specify the virtual host (vhost) from which queued message data is collected for the HPA metrics collection component.

Default value: brix365.

GLOBAL: Parameters for adding labels and annotations to BRIX services

brix365.global.podLabels

Labels are Kubernetes internal navigation and grouping tool. For example, you can add monitoring labels to pods to find specific logs.

A label is a key-value pair. Specify them in this parameter in the format: key: value.

Use them to define general settings without duplicating them for each service.

brix365.global.podAnnotations

Annotations are a Kubernetes tool for storing auxiliary data that helps configure the behavior of external systems or leave notes.

An annotation is a key-value pair. Specify them in this parameter in the format: key: value.

Use them to define general settings without duplicating them for each service.

Parameters for specifying labels and annotations at the pod level for a specific BRIX service. These parameters are combined with global parameters. In case of conflict, these parameters have a higher priority than the global parameters.

brix365.<service>.podLabels,

where <service> is the name of the service.

A label is a key-value pair. Specify them in this parameter in the format: key: value.

brix365.<service>.podAnnotations,

where <service> is the name of the service.

An annotation is a key-value pair. Specify them in this parameter in the format: key: value.

GLOBAL: Portable services parameters

brix365.global.managedServices.enabled

Enables support for portable services.
Default value: true.
Available options: true, false.

brix365.global.managedServices.namespace

Names of the namespace where portable services will be placed.
Default value: brix365-applets.

brix365.global.managedServices.defaultStorageClass

Specify a data storage system.

Default value: longhorn.

brix365.global.watchableConfigMap.enabled

Enables the use of ConfigMap to configure portable services. This allows you to set resource distribution limits, customize the placement of microservice pods on cluster nodes, etc.

Default value: false.

Available options: true, false.

GLOBAL: Service scaling parameters

brix365.global.autoscaling.enabled

Enables support for auto-scaling on the BRIX application side. Important: Before enabling service scaling, it is necessary to install add-on components. Read more in the article Enable service autoscaling in BRIX Enterprise.

Default value: false.

Available options: true, false.

brix365.global.autoscaling.type

Choosing the auto-scaling method.

Default value: hpa.

Available options: hpa, keda.

Where:

• keda is Kubernetes Event-driven Autoscaling.
• hpa is Horizontal Pod Autoscaler.

brix365.global.autoscaling.minReplicas

Configures the minimum number of replicas.

Default value: 1.

brix365.global.autoscaling.maxReplicas

Configures the maximum number of replicas.

Default value: 9.

brix365.global.autoscaling.rabbitmqQueueLength

If you have enabled RabbitMQ metrics for the HPA mechanism, set the maximum number of messages in the RabbitMQ queue. Exceeding this number triggers automatic pod scaling.

Default value: 500.

GLOBAL: Connection parameters to the private container image repository

brix365.global.image.repository

Connection string for private registry.

Format: hostname:port/path.

Where:

• hostname is the IP or domain name of the private registry.
• port is the connection port.
• path is the path to the directory.

Default value: hub.brix365.tech.

Read more about the required image storage configuration in Prepare infrastructure.

brix365.global.image.pullSecret

Name of the secret with access rights to the private registry (must be created manually, encrypted in Base64).

Default value: yandexsecret.

GLOBAL: A list of additional environment variables

brix365.global.extraEnv and brix365.<service>.extraEnv,

where <service> is the name of the service for which you set the parameter.

Lists of additional environment variables are added:

• global: to containers of all services.
• <service>: to containers of the specified service only.

If both parameters are specified, variables for a specific service have a higher priority. Global variables are not used.

Example:

1. Global parameter:

global:
  extraEnv:
    BRIX365_JAEGER_ENDPOINT: “jaeger.monitoring.svc”

2. Worker service parameter:

worker:
  extraEnv:
    BRIX365_JAEGER_ENDPOINT: “jaeger.loadtest.svc”

 
If you have not set a specific value for the BRIX365_JAEGER_ENDPOINT variable for a service, the global value is used, and tracing is sent to the monitoring namespace. The worker service has the value jaeger.loadtest.svc set, so its tracing is sent to the loadtest namespace.

GLOBAL: Additional parameters

brix365.global.postgres.maxIdleConns

Maximum number of connections to the main PostgreSQL node in the pool of unused connections.

Default value: 10.

brix365.global.postgres.maxOpenConns

Maximum number of open connections to the main PostgreSQL node from the pool.

Default value: 50.

brix365.global.postgres.maxConnLife

Maximum lifespan of a connection to the main PostgreSQL node from the pool.

Default value: 1m.

brix365.global.postgres.poolMaxIdleConns

Maximum number of connections to PostgreSQL copies in the pool of unused connections.

Default value: 10.

brix365.global.postgres.poolMaxOpenConns

Maximum number of open connections to PostgreSQL copies from the pool.

Default value: 50.

brix365.global.postgres.poolConnMaxLifetime

Maximum lifespan of a connection to PostgreSQL copies from the pool.

Default value: 5m.

brix365.global.maxGrpcMessageSize

Maximum response size.

Default value: 8388608.

brix365.global.maxGrpcBackoffDelay

Maximum delay between attempts to establish a GRPC connection.

Default value: 2s.

brix365.global.activeDeadlineSeconds

Number of seconds allocated for the entire Job to execute.

Default value: 3000.

brix365.global.backoffLimit

Number of migration attempts during BRIX update.

Default value: 5.

values.global.maxScriptTimeoutSeconds

Maximum waiting time for the worker service to finish processing the script.

values.global.defaultScriptTimeoutSeconds

The default waiting time for script processing to complete. The parameter will be applied if the wait time specified in values.global.maxScriptTimeoutSeconds is exceeded.

values.global.runtimeSchemaCacheMemoryLimit

Allows you to set a limit on the caching of server script execution schemes in the worker service.

values.global.maxFileSizeMB

Sets the maximum size of the files downloaded into the system.

Platform debugging parameters

brix365.debug

Enables platform debugging mode.

Default value: false.

Available options: true, false.

Company parameters

brix365.bootstrapCompany.email

The email address is specified. The email address will serve as the login for the main administrator.

Important: Used when creating a company at the time of BRIX installation, changing brix365.bootstrapCompany.email makes it impossible to apply new parameters or update BRIX.

Default value: admin@mail.com.

brix365.bootstrapCompany.password

Password for the main administrator login.

Important: Used when creating a company at the time of BRIX installation.

Default value: test.

brix365.bootstrapCompany.locale

Company interface language.

Default value: en-US.

Available options: "en-US", "es-ES", "de-DE".

Platform language parameters

brix365.language.default

Installed platform language.

Default value: en-US.

Available options: "en-US", "es-ES", "de-DE".

Database connection parameters

brix365.db.psqlUrl

Connection string to PostgreSQL for write and read operations.

Format: postgresql://user:password@hostname:port/databaseName?sslmode=disable.

Where:

• user is the name of the PostgreSQL user with rights to the databaseName database
• password is the password for the PostgreSQL user.
• hostname is the IP or domain name of the PostgreSQL server.
• port is the port for connecting to PostgreSQL, standard port: 5432.
• databaseName is the name of the database.
• sslmode is the use of a secure connection.

For more details on the necessary PostgreSQL configuration, read the article Prepare infrastructure.

brix365.db.secrets

Enable the use of the external secrets to connect to the database (psqlSecret, roPsqlSecret, mongoSecret, redisSecret, amqpSecret, s3Secret).

Default value: false.

Available options: true, false.

brix365.db.psqlSecret

Secret name with connection to PostgreSQL for read operations (must be manually created, encrypted in Base64).

It should contain the key PSQL_URL.

Important: enabling brix365.db.psqlSecret disables the brix365.db.roPsqlUrl parameter.

brix365.db.roPsqlUrl

Connection string to PostgreSQL for read operations.

Format: postgresql://user:password@hostname:port/databaseName?sslmode=disable.

Where:

• user is the name of the PostgreSQL user with rights to the databaseName database
• password is the password for the PostgreSQL user.
• hostname is the IP or domain name of the PostgreSQL server.
• port is the port for connecting to PostgreSQL, standard port: 5432.
• databaseName is the name of the database.
• sslmode is the use of a secure connection.

For more details on the necessary PostgreSQL configuration, read the article Prepare infrastructure.

brix365.db.roPsqlSecret

Secret name with connection to PostgreSQL for read operations (must be manually created, encrypted in Base64).

It should contain the key RO_POSTGRES_URL.

Important: enabling brix365.db.roPsqlSecret disables the brix365.db.roPsqlUrl parameter.

brix365.db.mongoUrl

Connection string to MongoDB.

Format: mongodb://user:password@hostname:port/databaseName?ssl=false&replicaSet=rs0&readPreference=nearest.

Where:

• user is the name of the MongoDB user with rights to the databaseName database.
• password is the password for the MongoDB user.
• hostname is the IP or domain name of the MongoDB server.
• port is the port for connecting to MongoDB, standard port: 27017.
• databaseName is the name of the database.
• ssl is the use of a secure connection.
• replicaSet is the replica set number.
• readPreference is the preferred read mode.

For more details on the necessary MongoDB configuration, read the article Prepare infrastructure.

brix365.db.mongoSecret

Secret name with connection to MongoDB (must be manually created, encrypted in Base64).

It should contain the key MONGO_URL.

Important: enabling brix365.db.mongoSecret disables the brix365.db.mongoUrl parameter.

brix365.db.vahterMongoUrl

Connection string to MongoDB for the authorization server.

Format: mongodb://user:password@hostname:port/databaseName?ssl=false&replicaSet=rs0&readPreference=primaryPreferred.

Where:

• user is the name of the MongoDB user with rights to the databaseName database.
• password is the password for the MongoDB user.
• hostname is the IP or domain name of the MongoDB server.
• port is the port for connecting to MongoDB, standard port: 27017.
• databaseName is the name of the database.
• ssl is the use of a secure connection.
• replicaSet is the replica set number.
• readPreference is the preferred read mode.

For more details on the necessary MongoDB configuration, read the article Prepare infrastructure.

brix365.db.vahterMongoSecret

Secret name with connection to MongoDB for the authorization server (must be manually created, encrypted in Base64).

It should contain the key VAHTER_MONGO_URL.

Important: enabling brix365.db.vahterMongoSecret disables the brix365.db.vahterMongoUrl parameter.

global.nosqlUsesPostgres

Allows you to disable MongoDB during initial system installation. The parameter is available starting with version 2026.2. If enabled, unstructured system settings, @Activity stream, and chat data will be stored in a PostgreSQL database.
 
Default value: false. To disable MongoDB usage, set the parameter to true.
 
Important: The option to work without MongoDB is only available to new companies and does not apply to existing ones.

brix365.db.redisUrl

Valkey connection string.

Format: redis://user:password@hostname:port/databaseName.

Where:

• user is the name of the Valkey user with rights to the databaseName database.
• password is the password for the Valkey user.
• hostname is the IP or domain name of the Valkey server.
• port is the port for connecting to Valkey, standard port: 6379.
• databaseName is the name of the database.

For Redis, use the same connection string with the same format.

For more details on the necessary Valkey or Redis configuration, read the article Prepare infrastructure.

brix365.db.redisSecret

Secret name with connection to Valkey (must be manually created, encrypted in Base64).

It should contain the key REDIS_URL.

For Redis, use the same key.

Important: enabling brix365.db.redisSecret disables the brix365.db.redisUrl parameter.

brix365.db.amqpUrl

RabbitMQ connection string.

Format: amqp://user:password@hostname:port/vhost.

Where:

• user is the name of the RabbitMQ user with rights to vhost.
• password is the password for the RabbitMQ user.
• hostname is the IP or domain name of the RabbitMQ server.
• port is the port for connecting to RabbitMQ, standard port: 5672.
• databaseName is the name of the database.

For more details on the necessary RabbitMQ configuration, read the article Prepare infrastructure.

brix365.db.amqpSecret

Secret name with connection to RabbitMQ (must be manually created, encrypted in Base64).

It should contain the key AMQP_URL.

Important: enabling brix365.db.amqpSecret disables the brix365.db.amqpUrl parameter.

Parameters for connecting to S3 file storage

brix365.db.s3.method

S3 file upload method.

Default value: PUT.

brix365.db.s3.accesskeyid

S3 server user login.

brix365.db.s3.secretaccesskey

S3 server user password.

brix365.db.s3.bucket

S3 bucket name.

Default value: s3brix365.

brix365.db.s3.backend.address

S3 connection string.

Format: hostname:port.

Where:

• hostname is the IP or domain name of the S3 server.
• port is the port for connecting to S3, standard S3 port: 9000.

If the port is not specified:

• s3.ssl.enabled: false: select port 80.
• s3.ssl.enabled: true: select port 443.

brix365.db.s3.backend.region

S3 server location region.

brix365.db.s3.ssl.enabled

Usage of TLS encryption by the S3 server.

Default value: false.

Available options: true, false.

brix365.db.s3.virtualHostedStyle.enabled

Enabling the Virtual-hosted style mode for S3. In this mode, the bucket name is part of the url, for example: https://bucketname.example.com/objectName.

If the parameter is disabled, the address model used is Path‑style.

Default value: false.

Available options: true, false.

brix365.db.s3.dumpurl

S3 server address for backup by the script brix365db.sh.

Format:

• For S3 in the Kubernetes cluster: http(s)://minio.<namespace>.svc.<cluster.local>..

• For external S3: http(s)://example.com:9000.

brix365.db.s3Secret

Secret name with connection to S3 storage (must be manually created, encrypted in Base64).

Should contain keys S3_BACKEND_ADDRESS, S3_REGION, S3_KEY, S3_SECRET, S3_BUCKET, S3_SSL_ENABLED, S3_UPLOAD_METHOD, S3_DUMP_URL, S3_VIRTUAL_HOSTED_STYLE_ENABLED.

Important: enabling s3Secret disables the following parameters:

• db.s3.method.
• db.s3.accesskeyid.
• db.s3.secretaccesskey.
• db.s3.bucket.
• db.s3.backend.address.
• db.s3.backend.region.
• db.s3.ssl.enabled.
• db.s3.dumpurl.
• db.s3.virtualHostedStyle.enabled.

Default value: brix365-custom-db-connections.

SMTP server connection parameters

This connection is used to send invitations to new users, letters to recover passwords, and notifications about new tasks

brix365.mailer.smtp.host

IP or URL address for connecting to the SMTP server.

Default value: " ".

brix365.mailer.smtp.port

Port for connecting to the SMTP server.

Default value: " ".

brix365.mailer.smtp.from

Email address (mailbox name) from which messages will be sent.

Default value: " ".

brix365.mailer.smtp.user

SMTP server user login.

Default value: " ".

brix365.mailer.smtp.password

SMTP server user password. Use permitted symbols.

Default value: " ".
 
Disabled if the brix365.mailer.smtp.mailerSecret parameter is active.

brix365.mailer.smtp.needTLS

Use of TLS encryption by the SMTP server.

Default value: false.

Available options: true, false.
 
Starting with version 2025.10.12, use the brix365.mailer.smtp.tls parameter to configure the TLS encryption method for the SMTP server. Leave the brix365.mailer.smtp.needTLS parameter set to false.

brix365.mailer.smtp.tls

This parameter is available starting with version 2025.10.12. Determines the TLS encryption method used by the SMTP server.

Select one of the following options:

• notls for an unsecured connection.
• tls for a TLS‑encrypted connection.
• starttls for a STARTTLS‑encrypted connection.

brix365.mailer.smtp.mailerSecret

The name of the secret with the password for authorization on the SMTP server.

The secret is created manually and is Base64‑encoded. It must contain the user-password key.
 
Important: activating brix365.mailer.smtp.mailerSecret disables the brix365.mailer.smtp.password parameter.

Parameters for managing two-factor authentication settings when logging in to the system and external portal

brix365.vahter.appconfig.secondfactor.limitAttempts

The maximum number of attempts to enter the confirmation code. If the limit is exceeded, the user is asked to enter the code again.

Default value: 3.

brix365.vahter.appconfig.secondfactor.codeLength

The length of the digital confirmation code the user receives.

Default value: 4.

brix365.vahter.appconfig.secondfactor.codeLifetime

The code's expiration time in minutes.

Default value: 2m.

Parameters for configuring recurrent restarts of business process instances

brix365.processor.appconfig. IntervalBetweenStartingRestoreProcesses

This parameter determines the interval between restart cycles for active business process instances with problems, such as those with a long-running automated action — script, request to a third-party service, etc.

Default value: 1h.

brix365.processor.appconfig. LimitByTimeContextToRunInstance

The duration of one cycle in minutes during which active business process instances with problems accumulated in the queue are restarted.

Default value: 10m.
 
If all instances have not been restarted, the remaining ones are processed in the next cycle. To prevent instances from piling up in the restart queue, you can increase the cycle duration or decrease the interval between cycles in the previous parameter.

Server script execution parameters

forkAvailableMemorySize

Sets a limit in MB for memory used by one execution fork inside one replica of the worker service.

If the parameter value is not set or is equal to 0, the worker service's operation remains unchanged.

Parameter for maximum email attachment size

ELMA365_POSTMAN_MAX_FILE_SIZE_MB

Sets the maximum size of attachments in outgoing emails. This value must not exceed the limit set in the values.global.maxFileSizeMB parameter. Before making changes, ensure your server has sufficient free disk space to store the increased volume of data.

Parameters of parallel processing of variables/functions

ELMA365_MAX_NUMBER_OF_WORKERS_TO_FILL_VARIABLES

Is set after the enableConcurrencyTemplateMapper feature flag is enabled. It sets the number of parallel worker instances inside the variable processing service.

This is useful if a lot of custom variables are used for generating document templates.

Default value is 5.

Enabling feature flags

brix365.settings.appconfig.onPremiseEnabledFeatureFlags

To enable a feature flag, enter its name in a new line. In front of the name, add a dash and a space. All the enabled feature flags are provided as a list.