A2ZDispatching Extensions Support

Welcome to the A2ZDispatching Extensions Support Center. Here you will find detailed information about all available variants of our Chrome extensions that enforce tab restrictions on DAT.COM pages, instructions for installation, configuration guidance, FAQ, troubleshooting tips, and contact details. We also link to our Privacy Policy for any data-related clarifications.

Privacy Policy:
https://a2zdispatching.com/privacy-policy/#extension

1. Overview

A2ZDispatching offers a family of Chrome extensions designed to secure and manage sessions on DAT.COM (one.dat.com) by restricting how many simultaneous tabs can be opened for the DAT.COM load-search page. Each variant is a separate extension with a hard-coded tab-limit (so end users cannot override it). These extensions help prevent session hijacking or unauthorized duplication of sessions in multi-tab scenarios.

Below is the list of published extensions and their core purpose:

  1. A2ZDispatchingR (Single-Tab) — Version 1.4
    • Allowed tabs: Exactly 1 DAT.COM tab. Any attempt to open a second DAT.COM tab triggers a 10-second warning overlay and then closes the extra tab.
  2. A2ZDispatching-Max2 (Dual-Tab) — Version 2.0.0
    • Allowed tabs: Up to 2 simultaneous DAT.COM tabs. A third DAT.COM tab triggers the warning overlay and closes the extra tab after 10 seconds.
  3. A2ZDispatching-DatController4.1 (Single-Tab) — Version 4.1.0
    • Allowed tabs: Exactly 1 DAT.COM tab. (Essentially same behavior as A2ZDispatchingR, but under a new naming/version.)
  4. A2ZDispatching-DatController4.2 (Dual-Tab) — Version 4.2.0
    • Allowed tabs: Up to 2 simultaneous DAT.COM tabs. Third tab triggers warning & close after countdown.
  5. A2ZDispatching-DatController4.3 (Triple-Tab) — Version 4.3.0
    • Allowed tabs: Up to 3 simultaneous DAT.COM tabs. Fourth tab triggers warning & close after countdown.
  6. A2ZDispatching-DatController4.4 (Quadruple-Tab) — Version 4.4.0
    • Allowed tabs: Up to 4 simultaneous DAT.COM tabs. Fifth tab triggers warning & close after countdown.

Note on Naming:
The above names (especially for 3–6) reflect your current naming scheme. However, to improve clarity for end users and administrators, you may consider renaming them to something like:

  • A2ZDispatching-SingleTabController v4.1.0 (instead of “DatController4.1”)
  • A2ZDispatching-DualTabController v4.2.0
  • A2ZDispatching-TripleTabController v4.3.0
  • A2ZDispatching-QuadTabController v4.4.0

Or embed the allowed-tab count in the display name:

  • A2ZDispatchingR (Max 1 Tab)
  • A2ZDispatchingR (Max 2 Tabs)
  • A2ZDispatchingR (Max 3 Tabs)
  • A2ZDispatchingR (Max 4 Tabs)

This helps users immediately recognize which variant to install. If you choose to rename, reflect the name consistently in:

  • manifest.json → "name" field
  • The Store listing title
  • Icons/screenshots (e.g., overlay a small “1 Tab”/“2 Tabs” label)
  • Support page descriptions below.

2. Available Extensions: Descriptions & Versions

Below we detail each extension variant, its version, and its behavior:

2.1. A2ZDispatchingR (Single-Tab) — Version 1.4

  • Name (Chrome Store): A2ZDispatchingR
  • Version: 1.4
  • Behavior:
    • Enforces that only one DAT.COM tab (one.dat.com/search-loads-ow) can be open at a time.
    • If the user tries to open a second DAT.COM tab, the extension:
      1. Brings focus back to the existing tab.
      2. Injects a full-screen warning overlay with a 10-second countdown: “SECURITY ALERT: Only one tab is allowed for this website. This tab will close in X seconds. Please return to the original tab to continue working.”
      3. After the countdown, automatically closes the extra tab.
  • Use Case: Organizations or users who want to strictly enforce single-session only, disallowing any possibility of multiple DAT.COM tabs.

2.2. A2ZDispatching-Max2 (Dual-Tab) — Version 2.0.0

  • Name (Chrome Store): A2ZDispatching-Max2
  • Version: 2.0.0
  • Behavior:
    • Allows up to 2 simultaneous DAT.COM tabs.
    • If the user attempts to open a third DAT.COM tab, behavior is analogous: focus returns to one of the existing tabs, warning overlay appears on the third tab with 10-second countdown, then the extra tab closes.
  • Use Case: Teams or individuals who need two concurrent DAT.COM sessions (e.g., monitoring two separate loads), but no more.

2.3. A2ZDispatching-DatController4.1 (Single-Tab) — Version 4.1.0

  • Name (Chrome Store): A2ZDispatching-DatController4.1 (or renamed to A2ZDispatching-SingleTabController)
  • Version: 4.1.0
  • Behavior: Same as A2ZDispatchingR (Single-Tab). Enforces exactly 1 DAT.COM tab, with 10-second warning + auto-close on attempts to exceed.
  • Use Case: Alternative packaging or updated codebase; for clarity, you may phase out A2ZDispatchingR v1.4 and replace with this if you wish.

2.4. A2ZDispatching-DatController4.2 (Dual-Tab) — Version 4.2.0

  • Name (Chrome Store): A2ZDispatching-DatController4.2 (or renamed to A2ZDispatching-DualTabController)
  • Version: 4.2.0
  • Behavior: Allows up to 2 DAT.COM tabs; third triggers warning + close after 10 seconds.
  • Use Case: For employees authorized to have two concurrent sessions.

2.5. A2ZDispatching-DatController4.3 (Triple-Tab) — Version 4.3.0

  • Name (Chrome Store): A2ZDispatching-DatController4.3 (or renamed to A2ZDispatching-TripleTabController)
  • Version: 4.3.0
  • Behavior: Allows up to 3 DAT.COM tabs; fourth triggers warning + close after 10 seconds.
  • Use Case: Employees or roles requiring up to three concurrent DAT.COM sessions.

2.6. A2ZDispatching-DatController4.4 (Quadruple-Tab) — Version 4.4.0

  • Name (Chrome Store): A2ZDispatching-DatController4.4 (or renamed to A2ZDispatching-QuadTabController)
  • Version: 4.4.0
  • Behavior: Allows up to 4 DAT.COM tabs; fifth triggers warning + close after 10 seconds.
  • Use Case: High-demand roles requiring up to four concurrent sessions, but no more.

Tip on Naming Consistency:

  • If you keep the “DatController4.x” naming, ensure your support page and Store listing explicitly state “Version 4.2.0 allows up to 2 tabs,” etc.
  • If you prefer more intuitive names (e.g., “SingleTabController”, “DualTabController”), update manifest.json "name" fields and Store listing titles accordingly, and adjust icons/screenshots to display “Max 1 Tab,” “Max 2 Tabs,” etc.

3. Installation & Setup

Each variant is published as a separate Chrome Web Store item. Follow these steps:

  1. Determine which variant to install
    • Review your organization’s policy or your own requirement: how many DAT.COM tabs are allowed concurrently?
    • Choose the corresponding extension URL (e.g., “A2ZDispatchingR” for single-tab, “A2ZDispatching-Max2” for dual-tab, or the “DatController4.x” variant).
  2. Install from Chrome Web Store
    • Visit the Chrome Web Store URL for that variant (e.g., https://chrome.google.com/webstore/detail/<ItemID>).
    • Click “Add to Chrome”.
    • Grant permissions when prompted (the extension needs tabs, scripting, storage, and host permission on https://one.dat.com/search-loads-ow*).
    • After installation, the extension icon appears in the toolbar.
  3. Verify Installation
    • Open Chrome → go to chrome://extensions → find the installed extension. Ensure it shows the correct version number.
    • Click “Details” to check that it has the expected permissions and that the host permission matches one.dat.com/search-loads-ow*.
  4. Initial Test
    • Navigate to https://one.dat.com/search-loads-ow in one tab.
    • Attempt to open the allowed number of tabs: if it’s the single-tab build, open a second tab to see the 10-second warning then closure; if dual-tab build, open two allowed tabs and then a third to test; etc.
    • Confirm the overlay appears and the extra tab closes after countdown.
  5. No Options Page for Runtime Changes
    • Because each build has a hard-coded limit, the extension may not present a user-editable dropdown for “maxTabs.” Attempting to open an “Options” page may either not be available or show read-only info. This is by design to enforce the fixed limit.
  6. Managed Policies (Enterprise)
    • If you use Chrome enterprise policies (via Group Policy or managed storage), you can further lock down the extension or push it automatically to users. For details on managed deployment, refer to Google’s documentation on [Chrome extension force-install via enterprise policy].

4. Configuration & Customization

Because each extension variant has the tab-limit baked in, there is no runtime configuration for changing that limit. However, some settings remain configurable (where relevant):

  • Security Overlay: If your code allows toggling securityOverlay on/off, you may choose to lock it via managed storage so end users cannot disable the warning overlay. For strict environments, administrators can push policies so that securityOverlay: true is enforced.
  • Logging Endpoint: If your extension forwards tab-open/close events to a backend API for auditing, ensure the endpoint URLs and authentication (if any) are configured in the code or via environment as per your infrastructure. Each variant should have identical logging logic except for the tab-limit check.
  • Versioning: When releasing updates (e.g., v1.4 → v1.5 for single-tab), bump the version in manifest.json and re-upload as a new package under the same Store item ID. For the new variants (DatController4.2 etc.), each has its own item ID; future updates must be uploaded to that specific item.

5. Frequently Asked Questions (FAQ)

Q1: Why are there multiple extensions instead of one with a dropdown?

A: To enforce a fixed tab-limit that end users cannot override, we publish separate builds where the allowed number of DAT.COM tabs is hard-coded. This prevents any user from changing the restriction at runtime, which maintains the security policy for each role or user group.

Q2: Which variant should I install?

A: Choose based on how many concurrent DAT.COM sessions your role or your organization allows:

  • Single-tab users → install A2ZDispatchingR (v1.4) or A2ZDispatching-DatController4.1 (v4.1.0).
  • Dual-tab users → install A2ZDispatching-Max2 (v2.0.0) or A2ZDispatching-DatController4.2 (v4.2.0).
  • Triple-tab users → install A2ZDispatching-DatController4.3 (v4.3.0).
  • Quadruple-tab users → install A2ZDispatching-DatController4.4 (v4.4.0).

Q3: How do I know which Chrome Store URL is for each variant?

A: In your internal documentation or distribution email, list each item’s Chrome Web Store link alongside its name. For example:

Q4: Can I switch from one variant to another after installation?

A: No. Each extension build is independent. To move from, say, single-tab to dual-tab capability, you must uninstall the single-tab extension and install the dual-tab extension variant. They are separate Chrome items.

Q5: What if my employees accidentally install the wrong variant?

A: Simply instruct them to remove the incorrect extension via chrome://extensions and install the correct one via its Store link. You can also use enterprise policies (Google Workspace/Active Directory) to push-install or block specific extension IDs for different user groups.

Q6: How does the warning overlay work?

A: When the user exceeds the allowed number of DAT.COM tabs, the extension:

  1. Brings focus to one of the existing allowed tabs.
  2. Injects a full-page overlay on the disallowed tab, displaying a message: SECURITY ALERT: You have exceeded the allowed number of DAT.COM tabs. This tab will close in 10 seconds. Please return to one of your existing DAT.COM tabs to continue working.
  3. A countdown updates every second. When it reaches zero, the extra tab is closed automatically.

Q7: My organization uses managed Chrome policies. Can I auto-deploy the correct variant to each user group?

A: Yes. In Google Workspace or via your MDM, you can specify the extension’s Chrome Web Store ID in the policy for “Force-install” for specific OU or user groups. Create separate OU or groups in your admin console corresponding to the required tab-limit, and map each variant’s extension ID accordingly.

Q8: Do these extensions collect any user data?

A: Each variant only monitors tabs for https://one.dat.com/search-loads-ow*, logs open/close timestamps, and optionally forwards them to your backend (if your organization uses logging). They do not collect personal identifiers (names, emails, IPs) unless specifically configured in your logging backend. See our Privacy Policy for full details.

Q9: How do I update or get the latest version?

A: When a new version is released (e.g., v1.5 for single-tab), you will see an update available in Chrome Web Store. Users simply click “Update” or wait for auto-update. For each variant, keep the version number in manifest.json incremented and upload to the same item ID in your Developer Dashboard.

6. Troubleshooting

6.1. Extension Not Enforcing the Correct Tab Limit

  • Verify Installation: Go to chrome://extensions, find the extension variant and confirm the version and name match the intended variant.
  • Check Host Permission: Under extension details, ensure one.dat.com/search-loads-ow* is listed under site access. If not, remove and reinstall the extension.
  • Test in Incognito (if enabled): If you enabled extension in Incognito, ensure you allow it under extension details. Then test DAT.COM tabs in Incognito to see behavior.
  • Conflicting Extensions: Disable other session-management or tab-management extensions that might interfere.
  • Console Errors: Open DevTools on the DAT.COM page. Look for errors related to chrome.scripting.executeScript or background script errors. Report these to support with screenshots or logs.

6.2. Warning Overlay Doesn’t Appear

  • Check securityOverlay Setting (if available): Some builds may allow toggling overlay via managed storage; ensure it’s enabled. In fixed-limit builds, overlay should be always enabled unless explicitly disabled in code. Confirm code version if you have a custom build.
  • Content Script Injection Issues: Ensure your manifest’s content_scripts or host permissions include the correct URL pattern (https://one.dat.com/search-loads-ow*).
  • Chrome Version Compatibility: Use a recent Chrome version. Very old Chrome versions might not support chrome.scripting.executeScript in Manifest V3.

6.3. Extra Tab Not Closing After Countdown

  • Check console warnings: There might be errors in background script preventing chrome.tabs.remove(tabId). Note the error message in DevTools or background page logs.
  • Tab Already Closed: If the tab closes prematurely or fails to close, verify if another extension or policy is interfering.
  • Service Worker Lifecycle: In Manifest V3, background scripts run as service workers; ensure your code logic accounts for service-worker shutdown (e.g., avoid unawaited async calls). If necessary, add error handling/logging to background.js to capture failures.

6.4. Logging to Backend Not Working

  • Network Calls: If your extension sends fetch/XHR to your ASP.NET Web API, open DevTools Network tab to see request status.
  • CORS / Permissions: Ensure your Web API allows CORS from the extension origin or that you’re using appropriate methods (e.g., background script with fetch to your API).
  • Authentication: If your API requires authentication, ensure the extension includes necessary tokens or credentials.
  • Storage & Session ID: Confirm that the extension generates/reads the correct session identifier (RDP user or similar) and includes it in the payload.

6.5. Installation Issues

  • “You do not have permission to install this item”:
    • Check that the user is in the correct Google Group or OU if it’s a private/testers-only listing.
    • Confirm the extension ID matches the one in the policy or Store listing you shared.
  • Corrupted Extension:
    • Remove and reinstall from the Store.
    • Do not load unpacked in developer mode for production use; use the published Store version to ensure correct behavior.

7. Contact & Support

If you encounter issues not covered above, or require enterprise deployment assistance, please contact us:

When contacting support, please include:

  • Extension name and version (e.g., A2ZDispatching-DatController4.3 v4.3.0).
  • Chrome version and OS.
  • Steps to reproduce the issue.
  • Screenshots or console logs if relevant.
  • If it’s a managed environment, describe any enterprise policies applied.

8. Additional Resources

  • Privacy & Security:
  • Release Notes / Updates:
    • Maintain a changelog on your site or GitHub listing for each variant, e.g.:
      • v4.1.0 (Single-Tab): initial release under DatController4.1, code improvements over v1.4.
      • v4.2.0 (Dual-Tab): new variant for two-tab allowance, etc.
  • Enterprise Deployment:
    • Link to Google’s docs on [Force-install Chrome extensions via policy].
    • Provide guidance on packaging and version pinning.

9. SEO & Content Tips (Optional)

If you want to optimize this support page for SEO (so internal users or admins easily find answers):

  • Use clear headings with keywords like “A2ZDispatching Chrome Extension Support,” “Single-Tab DAT.COM Extension,” “Dual-Tab DAT.COM Tab Restriction,” etc.
  • Include a table summarizing variants: columns: Extension Name, Version, Allowed Tabs, Store URL.
  • Use FAQ schema markup if your WordPress theme supports it.
  • Ensure all links (Privacy Policy, Store URLs, support form) are valid and use HTTPS.
  • Regularly update the page when new versions or variants are published.
  • Consider adding a brief “How to choose the right variant” section near the top, so admins can quickly see which build applies to their team.

Example table (in HTML or Markdown) for quick reference:

Extension VariantVersionAllowed TabsChrome Store URL
A2ZDispatchingR (Single-Tab)1.41https://chrome.google.com/webstore/detail/…
A2ZDispatching-Max2 (Dual-Tab)2.0.02https://chrome.google.com/webstore/detail/…
A2ZDispatching-SingleTabController4.1.01https://chrome.google.com/webstore/detail/…
A2ZDispatching-DualTabController4.2.02https://chrome.google.com/webstore/detail/…
A2ZDispatching-TripleTabController4.3.03https://chrome.google.com/webstore/detail/…
A2ZDispatching-QuadTabController4.4.04https://chrome.google.com/webstore/detail/…

(Replace the “…” with the actual item IDs/URLs.)

10. Putting It on WordPress

  • Page Title: “A2ZDispatching Extensions Support”
  • Permalink: /support/a2zdispatching-extensions/
  • Content Sections: Use your theme’s heading styles (e.g., <h2>Overview</h2>, <h3>Installation & Setup</h3>, etc.).
  • Insert Links:
    • Privacy Policy link near the top and in FAQ sections.
    • Store URLs in a table or bullet list under “Available Extensions.”
    • Contact email as a mailto: link.
  • Schema Markup: If feasible, wrap FAQs in FAQ schema.
  • Search Functionality: If your site search can index this page’s content, use terms like “single tab extension,” “dual tab DAT.COM extension,” etc.

11. Summary

  • You now have six published variants: single-tab (v1.4, v4.1.0) and multi-tab builds (v2.0.0 for 2 tabs, v4.2.0 for 2 tabs, v4.3.0 for 3 tabs, v4.4.0 for 4 tabs).
  • Each variant is a separate Chrome Web Store item. Clearly list each on your support page with its Chrome Store URL, version, and allowed tabs.
  • Consider renaming them to more intuitive names (e.g., “A2ZDispatching-SingleTabController,” “A2ZDispatching-DualTabController,” etc.) to help users pick the correct one. Ensure you update manifest.json "name", icons/screenshots, and Store listing titles accordingly.
  • Provide clear installation, testing, and troubleshooting guidance for each.
  • Use the FAQ to address how to choose between variants and how to handle mis-installs.
  • Link to Privacy Policy and support contact.
  • Optionally, include a summary table for quick reference and optimize for SEO with clear headings and keywords.

With this revised support-page content, your users and administrators will have a one-stop resource to understand and install the correct extension variant for their required tab-limit. Feel free to adapt the suggested naming, headings, or FAQs to match your branding and organizational policies. If you need further assistance refining the text or integrating into your WordPress theme, let me know!