Home > User Voice > App binding for global constants, form/business rules and automations

App binding for global constants, form/business rules and automations

1

05.03.2026

14:17

Hi,

unfortunatelly global "objects" (business rules, form rules, constants, automations) have no app binding functionality as data sources have. Some global constants, business or form rules and automations may contain critical data (e.g. api tokens) that should not be useable by all devs with studio access.

An option to set an object as protected and enabling an app binding to allow the usage would solve this matter. Default would be same behavior as it is now. If a dev wants to protect the object from global usage one could select the apps being allowed to use the object explicitly.

Sidenote: The other way round would be to have protected and enabled app binding as default and an option „public usage“. This is not my favorite.

Kind regards
Sébastien

18.03.2026

09:05

I don’t agree with the example, because tokens shouldn’t be stored in constants, but regarding the overall idea — I think it would be very useful if we could assign global constants/rules only to specific applications, similar to how data sources work.
For environments where a many developers work in lite mode, this could be very helpful.

Solution (0)

Helpful (0)

Wrong answer (0)

18.03.2026

12:39

In reply to: Katarzyna

Hi Katarzyna,

where do you store an api token so that in can be managed in a central way. The api token can have a lifetime and if you put it everywhere in data sources or actions it's a pain to replace it by a new one, isn't it?

Kind regards
Sébastien

Solution (0)

Helpful (0)

Wrong answer (0)