{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/92ba7c1a80f04085bf5ae29ffb1b904a\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/92ba7c1a80f04085bf5ae29ffb1b904a-816a6a6321ebcced.gif","duration":723.606,"title":"Athenian Custom Pages and Restricted Access","description":"This Loom explains how Athenian uses custom page restrictions to show entity data and registration details only to the teams that need them. The author demonstrates creating a Bank Accounts custom page with predefined system and custom fields, plus registration tables, then restricting visibility so roles like accounting or finance do not see the bank page unless assigned. In display settings, admins can control which system and custom registration types appear for specific teams, using examples such as limiting what the tax team can view. It also covers restricting custom registration fields, like a tax GII IN number, so only the tax team user Sally can see and optionally edit the field, even if it belongs to tax registrations."}