-
Notifications
You must be signed in to change notification settings - Fork 10k
[CF1] CWI step 3 expansion #22664
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CF1] CWI step 3 expansion #22664
Conversation
|
Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment. We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally. PR Change SummaryExpanded the Clientless Web Isolation documentation with detailed setup instructions and enhanced clarity on browser isolation policies.
Modified Files
How can I customize these reviews?Check out the Hyperlint AI Reviewer docs for more information on how to customize the review. If you just want to ignore it on this PR, you can add the Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add |
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
human3
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
|
||
| 5. Name your policy and define who will have access to your isolated application. Refer to the [Access policy documentation](/cloudflare-one/policies/access/#actions) to construct your policy. | ||
|
|
||
| 6. Under **Additional settings**, toggle the **Isolate application** on to enable your application to be served in an isolated browser for users matching your policy. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This part is only necessary if you are doing it for apps through the normal Access part of the dash. For the clientless BISO application its not needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To clarify.
Setting > Browser Isolation> select Manage next to Permissions. This does not require the isolate setting in Access policies. It is managing the login page for .cloudflareaccess.com/browser.
If you enable the isolate toggle in a policy and include that policy on a normal self-hosted application then we will isolate that for all users that match that policy.
...ontent/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx
Show resolved
Hide resolved
...ontent/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx
Outdated
Show resolved
Hide resolved
…up/clientless-browser-isolation.mdx
* [CF1] CWI step 3 expansion * final edit * Update src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx
Summary
PCX-17493
Screenshots (optional)
Documentation checklist