Short answer: some secured sites will work and some won’t. The limit is usually in how the page gets rendered for review, not in the Workfront approval workflow.
The 26-Q4 web link approval depends on the Frame.io integration. The release note says it isn’t available in the Preview sandbox for that reason. Frame.io’s web review loads the live page in a frame, and its HTML Review article lists the conditions:
- The site has to allow iFrame embedding. Many login-protected apps and intranets send X-Frame-Options or a Content-Security-Policy frame-ancestors header that blocks it. That usually shows up as the blank or half-rendered frame you’re seeing.
- Private URLs are supported, but “certain authentication flows may not work depending on server configuration.” SSO flows that bounce through an identity provider are the usual culprit.
- Some private and restricted URLs need the Frame.io browser extension, and it’s Chrome only.
- Admins can allowlist redirect domains in Frame.io’s Content Security Settings. That helps sites that need a redirect to finish signing in.
What I’d check, in order:
- In dev tools on the target site, look at the response headers for X-Frame-Options or frame-ancestors. If those block framing, no extension will fix it. The site owner would have to allow Frame.io, which is often doable on a staging host.
- Make sure every reviewer has the extension installed and is already signed in to the site in the same Chrome profile.
- If sign-in redirects through Okta, Entra or similar, have your Frame.io admin add those domains to the redirect allowlist.
- Test in Production, not Preview, because the feature isn’t available in the Preview sandbox.
If the site can’t be framed, the fallback is a staging copy that allows framing, or a zipped HTML build. Zip HTML is supported for interactive review today.