Default Behavior

Last updated 25/02/2026

Default User Interface Behavior

In Five, the default user interface for all new applications is New York.

Application-Level Default

Each application has a Default User Interface setting. This determines which user interface will be applied to newly created instance records.

• If no changes are made, all new instance records will use New York
• If the Default User Interface field on the application record is changed (for example, to Boston or Seattle), then:
• All future records created after this change will default to the newly selected user interface
• Existing instance records will not be updated automatically

info

When making changes to your application or instance records, you will need to remove deployment and deploy your application again for these changes to take effect.

Existing Instance Records

Changing the application-level default does not retroactively update previously created instance records.

If you need to change the user interface for an existing instance:

• Open the instance record
• Update the User Interface field manually

Precedence Rules

If the following is set:

• A value in the Default User Interface field (application-level)
• A different value in the User Interface field (instance-level)

Then, the User Interface field on the instance record takes precedence. This means the instance-specific setting will override the application default.

Summary

Level	Field	Applies To	Priority
Application	Default User Interface	Future instance records	Lower
Instance	User Interface	That specific instance record	Higher

In short:

• New York is the default starting point
• Application default affects future instances only
• Instance-level setting always wins
• Existing instances must be updated manually if changes are required