<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Role-Based Access on Chris Worth</title><link>https://chrisworth.dev/tags/role-based-access/</link><description>Recent content in Role-Based Access on Chris Worth</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 08 Aug 2026 09:00:00 -0500</lastBuildDate><atom:link href="https://chrisworth.dev/tags/role-based-access/index.xml" rel="self" type="application/rss+xml"/><item><title>Role-Based Approval Gating in Canvas Apps</title><link>https://chrisworth.dev/posts/power-apps-role-based-approval-gating-guide/</link><pubDate>Sat, 08 Aug 2026 09:00:00 -0500</pubDate><guid>https://chrisworth.dev/posts/power-apps-role-based-approval-gating-guide/</guid><description>&lt;p>An approval app I worked on has a diagnostic panel that only an admin can see, and even an admin can&amp;rsquo;t just navigate to it. It unlocks by clicking an invisible fifty-pixel rectangle in the corner of the home screen nine times. &lt;code>varUserIsAdmin&lt;/code> gates it, a click counter unlocks it, and neither one alone is enough. That&amp;rsquo;s a throwaway easter egg, but it&amp;rsquo;s also the whole idea behind every access rule in the app: knowing who someone is isn&amp;rsquo;t the same as knowing what they&amp;rsquo;re allowed to do right now, and the interesting formulas are the ones that check both.&lt;/p></description></item></channel></rss>