Skip to content
DataSquaresDocs
datasquares.aiSign inStart free

AI

Ask AI beside any web app

The DataSquares browser extension puts the DataSquares AI assistant in the side panel of Google Chrome or Microsoft Edge, next to the web app you work in: a CRM, an ERP, a helpdesk, an internal portal. On a site your administrators set up, the chat starts on the data they chose for it, such as the sales dashboard beside your CRM, so you can ask “how is this account doing?” without leaving the page.

Every answer runs as you, with your role, row-level security and masking, exactly as in the web app’s AI chat: the extension shows you nothing you could not see in DataSquares.

Install it

Section titled “Install it”

The extension’s listings in the Chrome Web Store and Microsoft Edge Add-ons are on their way. Once they’re live, install DataSquares from the Chrome Web Store (Chrome) or Microsoft Edge Add-ons (Edge); your IT team may install it for you. To keep it at hand, pin it: in Chrome, open the puzzle-piece menu beside the address bar and pin DataSquares; in Edge, open Extensions and choose Show in toolbar.

Sign in

Section titled “Sign in”
  1. Click the DataSquares icon in the toolbar. The side panel opens.
  2. Choose Sign in. Your browser opens a DataSquares sign-in window: sign in as you always do, single sign-on and two-factor authentication included. If you are already signed in to DataSquares in this browser, you go straight to the next step.
  3. The window shows who the extension will ask as and in which workspace. Choose Connect.

The extension never sees your password, and it holds no API key: it gets a sign-in of its own, as you, in the workspace you connected it in. That sign-in lasts until you close your browser; then sign in again. It is listed under Settings → Security as Browser extension (Active sessions), where you can end it like any other.

If your company runs its own DataSquares server, choose Use another address before signing in and enter your company’s DataSquares address (and its API address, only if your IT team gave you a separate one). The extension keeps it until you close your browser; your IT team can set it for everyone.

Allow your company’s sites

Section titled “Allow your company’s sites”

After you sign in, the extension lists the sites your administrators set up and asks your browser for permission to read their addresses. Choose Allow, then confirm in the browser’s own prompt. You are asked once for each new site. On every other site the browser doesn’t even tell the extension which page you are on, and it never reads them.

Ask about the page you’re on

Section titled “Ask about the page you’re on”
  • On a site your administrators set up, the panel names the site and the data it starts on, for example Salesforce · Sales pipeline. A small DataSquares button on the page opens the panel too.
  • Ask in your own words, or choose one of the suggested questions, which come from that data. The answer streams in as it is written; Stop ends it.
  • Page context. Where your administrators set it up, a value from the page’s address, such as the account on screen, is passed with your question as a filter, and the panel shows it (for example Account Id: 0018a00000Xyz).
  • Add this page. Where your administrators allow it, tick Add this page to add the page’s text to one question: the part you selected on the page, or the whole page when nothing is selected. Only that question carries it, and the box unticks afterwards. A page longer than one question can carry is not cut short: select the part you need and ask again.
  • Effort. If your company lets you choose, the effort picker beside Send works as in the chat, and your choice is saved to your profile (Effort).
  • Open in DataSquares opens the conversation in the web app, where it continues. A change the assistant proposes, such as a new dashboard, is approved there.

On a site nobody set up, the panel either says that DataSquares isn’t set up for the site or offers your usual chat, as your administrators chose.

What it can and cannot see

Section titled “What it can and cannot see”
The extension
Reads the address of a page Only on the sites your administrators set up, after you allowed them
Reads the text of a page Only when you tick Add this page, for that one question, where your administrators allow it
Keeps anything No: its sign-in is forgotten when you close your browser; conversations stay in DataSquares, as on the web
Sees your password Never

Each question is recorded in your workspace’s audit log as one asked from the extension, without its words, the page’s text or the page’s address.

Set it up (administrators)

Section titled “Set it up (administrators)”

Company administrators set the extension up for a workspace under Administration → AI → Browser extension. Until someone turns it on, it is off: it can’t sign in or ask in that workspace.

  1. Turn on the browser extension.
  2. Who may use it: everyone whose role has the AI chat, or only the roles you choose. Company administrators may always use it. The AI controls still apply to every question (AI controls).
  3. On sites with no data set: nothing (the extension says the site isn’t set up), or the person’s usual chat.
  4. Add a site for each web app:
    • a name people recognise, such as Salesforce;
    • its web address: one address (erp.example.com, an intranet name, an IP address) or every address under a domain (*.salesforce.com). Not every site, and not a whole top-level domain such as *.com; no https://, path or port. Paste a full link and the page offers its address instead;
    • the dashboard or model of this workspace its chat starts on;
    • whether people may add the page’s text to a question (off unless you turn it on);
    • page context (optional): where a value sits in the page’s address, as a path with {value} for the part that changes and * for any one part (/lightning/r/Account/{value}/view), or as a query parameter (?accountId), and the field it filters (Account Id). A value too long or unusual to pass on whole is not used.

A site narrows where the chat starts; it never widens what anyone may see. A person who can’t open a site’s dashboard in DataSquares is told the site’s data isn’t available to them. When a site’s dashboard or model is deleted, the site says so here until you choose new data.

Install it for everyone

Section titled “Install it for everyone”

IT can install the extension for everyone and preset your DataSquares address through the browser’s policies (Google Admin, Microsoft Intune or Group Policy): force-install it (ExtensionInstallForcelist) and set its managed settings, appUrl (the address people sign in at) and apiUrl (only when the API has an address of its own). People still sign in as themselves.

On a DataSquares server your company runs itself, the extension can sign in only once the server names the extensions it accepts: its operator sets BROWSER_EXTENSION_IDS in the API’s settings (.env.api) to the extension’s ids in the Chrome Web Store and Microsoft Edge Add-ons (each the 32 letters at the end of its store listing’s address), separated by a comma, and restarts the API. Until then, signing in says The browser extension isn’t set up on this DataSquares server yet.

The API

Section titled “The API”

The routes behind the settings need a signed-in company administrator, in the workspace the session is in; an API key can’t use them. On Team, a change answers 403 PLAN_TIER_REQUIRED with details.feature browser_extension.

Route What it does
GET /api/extension/admin The settings (enabled, otherSites, allRoles, roleIds), the sites, and whether the plan includes the extension
PUT /api/extension/admin/settings Set the four settings
POST /api/extension/admin/sites Add a site: name, hostPattern, target ({ "type": "dashboard" or "model", "id" }), pageText, addressRule, addressField
PUT /api/extension/admin/sites/{id} Change a site; another site with the same address is 409
DELETE /api/extension/admin/sites/{id} Remove a site
Section titled “Related”