The block page and requests
When the StackJack browser extension stops a person from opening an AI site, it shows the block page. The page says why, and lets the person ask your organization to approve the site. This page…
Written By Christopher Scaminaci
Last updated 17 days ago
When the StackJack browser extension stops a person from opening an AI site, it shows the block page. The page says why, and lets the person ask your organization to approve the site. This page describes what the person sees and where their request goes.
At a glance
- What it does: shows what a person sees when the extension blocks a site, and where their request goes.
- Plan: Pro and above.
- Who: staff see the block page. An Administrator decides requests.
- Where: requests arrive on AI Governance → AI inventory → Tool requests.
What the person sees
The block page names the AI site and gives one of three reasons:
- "Your organization has not approved this AI site." The site is not approved, or you denied it, and your policy blocks unapproved sites.
- The site is allowed only with a company account.
- "StackJack cannot be reached, and your organization blocks AI sites until it can." This appears only when you turned on Block AI sites when StackJack cannot be reached, and only after the extension could not read the policy for longer than the allowed time.
When your policy only warns, the same page has a Continue button. Continue opens the site for the rest of the browser session and records that the person continued.
A blocked send, as opposed to a blocked site, shows a short message on the AI site itself and keeps the text in the prompt box. The message names the rule that stopped the send, never the text that matched. If the rule asks the person to give a reason, the message holds a link. The person opens the link, gives a reason, and sends again.
Asking for approval
The block page has a Request this tool form. The person gives a work email (the extension fills in the email of the browser profile where it can, and the person can change it) and a reason of 10 to 500 characters. When they send the form:
- StackJack makes a tool request for the site. It is in the same list as the other tool requests, labeled "via the browser extension (email not verified)".
- The person sees "Your request was sent."
- You or a reviewer approve or deny the request as you do any other. If you approve, the site is on your approved list, and the extension lets it through after its next policy update.
A person can send up to five requests an hour from one email address. The page tells them if a limit stopped a request.
The email on a request is what the person typed. StackJack does not check it, and the request never sends mail to that address.
The first-run page
The first time the extension runs, and again when the text changes, it shows a first-run page that points to your organization's AI policy. The page has an I understand button.
The button does not record an acknowledgement. It asks StackJack to email the person a link to the policy, if the person has a policy to acknowledge. The acknowledgement is recorded only when the person opens that link from their own mailbox. This is the same rule as for every other acknowledgement: only someone who can read the mailbox can acknowledge. Whatever email the person gives, the page shows the same answer, so nobody can use it to learn which addresses StackJack knows.
What you can change
- Whether the page blocks or warns. Use the policy choices in Browser policy.
- Who can approve. Requests follow the same roles as the other tool requests.
- The wording. The block page text is fixed. Your own message belongs on the policy that people acknowledge.
If a person says the page is wrong
Was this helpful?
More in Connect your AI
Data sourcesSend telemetry from coding toolsSettings for staff machinesDelivering the settings through your RMMStill need help? Ask the team