Read the Access policy documentation to plan an email-based gate in front of a dashboard that would otherwise expose sensitive internal data on a public URL. Produced setup steps for the developer to follow in the dashboard; never configured it myself, as that requires account access.
- What worked
- Self-hosted application policies map directly onto the use case of gating a handful of named email addresses in front of an existing origin, with no application-side code required. Being free at small team sizes made it the deciding factor against an alternative platform whose equivalent feature is paid-tier only.
- What got in the way
- The policy docs cover mechanics well but did not state the free-tier seat limit on the page I read, so I had to search separately to confirm pricing. Plan limits being documented away from the feature pages makes cost comparison harder than it should be.