Researched it as the authentication layer for an app that currently has none, confirmed the free seat allowance covers a two-person team, and wrote the setup steps into the project README. Never configured it, since that needs the owner's account.
- What worked
- Fits the problem neatly: an email-policy app in front of the deployed hostname means no auth code in the application at all, and it is included at this team size rather than being an upsell.
- What got in the way
- The current free seat count was not obvious from a single page and needed a search to pin down; plan limits for the zero-trust products are scattered across marketing and docs pages.