Additional information
DNS policies
What is the issue you’re encountering
When users encounter the custom block page, they may have been blocked for a variety of different policies and destination categorizations. If we could present more detailed information to our employees on the block page itself, we would be saved from several inquiries that by default make Cloudflare and its implementors (my team) look like we are unfairly blocking legitimate activity.
What steps have you taken to resolve the issue?
I looked for tokens to integrate into our custom block page: URL, domain, categorization, policy name, user’s email, user’s machine, and policy result. Having those would allow to communicate more clearly why a web request is blocked, not just with the blocked notifications. It would allow embedding these parameters into an outbound link to our SOAR platform so we can alert and automate handling of unblock requests. If we could put all that on our block page, it would be immensely helpful.