# ApplicationArea Property
> Version: _Available or changed with runtime version 1.0._
Sets the application areas that apply to the control. Standard values are All, Basic, Suite, and Advanced.
## Applies to
 Page Label
 Page Field
 Page Part
 Page System Part
 Page Chart Part
 Page Action
 Page Custom Action
 Page File Upload Action
 Page User Control
 Page
 Report
## Property Values
A text string that contains a comma-separated list of application area tags.
An application area tag must have the format name, where name is the application area. The name can be any combination of letters (Aa-Zz) and numbers (0-9) without spaces. For example, to specify the Basic and Fixed Assets application areas, set the property to Basic, FixedAssets.
If the control applies to all application areas, you can set the property to All. This means that the control will always appear in the user interface.
## Syntax
```al
ApplicationArea = Basic, Suite;
```
## Remarks
> APPLIES TO: Business Central 2022 release wave 2 and later
With Business Central 2022 release wave 2, the ApplicationArea property set on fields defaults to the page value. The property inheritance means that page controls without the ApplicationArea property explicitly set, inherit the ApplicationArea defined on the parent page or report if it's a request page. The ApplicationArea property can be used without setting the UsageCategory property on pages to provide a default fallback for controls, without forcing search visibility.
> TIP
> With Business Central 2023 release wave 1, a new code action is introduced to set the default value for ApplicationArea on a page or a report level and remove all duplicates on field level. This code action can be applied to an object, a document, a project, or a workspace. See AL Code Actions<../devenv-code-actions>.
> NOTE
> The ApplicationArea property inheritance has no impact on page or report extensions. On these extensions values must still be set explicitly.
Application areas represent a feature in the system that offers developers, administrators, and users the ability to define differentiated user experiences. They are mapped to controls to show or hide them on page objects to enable more or fewer business scenarios.
The ApplicationArea property is used together with the ../methods-auto/session/session-applicationarea-method to hide user interface elements.
If one or more application areas are enabled in a session, any controls that are not tagged with an application area will not appear in the user interface.
You can also add new application areas, see ../devenv-extending-application-areas for more information.
## Dependent Property
The UsageCategory property is a required setting used together with the ApplicationArea property. This enables a page or a report to be available in Search for the navigation support. For more information about navigation support, see Adding Pages and Reports to Search<../devenv-al-menusuite-functionality>.
## Related information
../methods-auto/session/session-applicationarea-method
../devenv-extending-application-areas
devenv-accessbypermission-property
devenv-properties

Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/properties/devenv-applicationarea-property, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact. https://jonas-paprotka.de/docs/dev-itpro/developer/properties/devenv-applicationarea-property/
