diff --git a/dev-itpro/developer/devenv-lists-as-tiles.md b/dev-itpro/developer/devenv-lists-as-tiles.md
index 85a5fde979..ee045c0cff 100644
--- a/dev-itpro/developer/devenv-lists-as-tiles.md
+++ b/dev-itpro/developer/devenv-lists-as-tiles.md
@@ -53,7 +53,7 @@ The order of the fields determines how they appear in the layout of the tile, no
 - A verbose field appears at the bottom of the tile, separated by a line.
 
 > [!NOTE]
-> The Tile view respects user permissions and visibility settings on fields, like the `Visible` property, personalization, and so on. For example, suppose you have a field defined in `fieldgroup(Brick; <...>)` but the field is only defined in the table object, not in the page object: This field doesn't display in the Tile view by default. Users can display the field by using personalization.
+> The Tile view respects user permissions and visibility settings on fields, like the `Visible` property, `AccessByPermission` property, and personalization, and so on. For example, suppose you have a field defined in `fieldgroup(Brick; <...>)` but the field is only defined in the table object, not in the page object. This field doesn't display in the Tile view by default. Users can display the field by using personalization.
 
 
 ### Including images in tiles