Bindings

The live project values templates, triggers and code can reference.

Where: Project → Settings → Bindings · /projects/<project>/settings?tab=Bindings

A read-only table of every project binding — a value you can insert into triggers, code and templates with the @Model. prefix, for example @Model.Project.Name. Next to each binding the tab shows the value it resolves to right now, using the same lookup the email/SMS/push template builders use — so what you see here is exactly what a template renders. Bindings shown as Not set are still valid; they resolve once the underlying project value is configured.

Screenshot TODO — capture comes from testing-plan area 17-project-settings.

Available bindings

Binding	Resolves to
@Model.Project.Name	The project display name.
@Model.Project.UniqueName	The project unique (slug) name.
@Model.Project.DefaultLanguage	The default language code.
@Model.Project.Url	The project marketing URL.
@Model.Project.AdminUrl	The effective admin-portal URL (developer override, else the canonical admin URL).
@Model.Project.Logo.Url / .Path / .IntegrationId	The logo's public URL, its storage path, and the file integration that holds it.
@Model.Project.Icon.Url / .Path / .IntegrationId	The same three values for the project icon.
@Model.Project.MainColor / @Model.Project.AccentColor	The brand main and accent colors.

Example: an email subject Welcome to @Model.Project.Name renders as Welcome to Aurora Shop when the Brand name is Aurora Shop.

API reference

Endpoints: get-project-tokens.