BlazeXL Docs

Blaze Sheets

Share Excel workbooks with embedded Blaze Block dependencies that work for anyone, with automatic detection and security-first consent.

Blaze Sheets

Blaze Sheets are governed portable workbooks for Excel.

They allow you to create shareable .xlsx files with embedded Blaze Block dependencies so the workbook can execute the same approved logic everywhere it is opened.

When a teammate, client, or another business unit opens the sheet, BlazeXL detects, resolves, and imports the required Blocks under a consent-first model. The workbook stays familiar. The logic becomes governed.

Zero-Friction Sharing for Teams

Create complex Excel models powered by custom Blaze Blocks, then share the .xlsx file. Recipients don't need to manually find, import, or configure the Blocks you used — the workbook carries its own dependency manifest.

The Vision: A Workbook That Carries Governed Logic

In traditional Excel, sharing complex models often leads to "Broken Link" errors or requires recipients to have specific add-ins and local scripts installed. Blaze Sheets solves this by:

  1. Auto-Detection: The add-in detects required Blaze Blocks the moment the file is opened.
  2. Block Dependency Injection: Required code is securely injected into the compute session.
  3. Consent-Based Security: Users remain in control of what code runs on their behalf.

This turns the workbook into a governed distribution layer for business logic, not just a file with hidden formulas and macros.

How It Works

For Sheet Creators (The Authors)

  1. Open the Dependency Manager: In the BlazeXL add-in taskpane, navigate to the DEPS tab.
  2. Add Published Blocks: Search the Block Registry and add any published Blaze Blocks your formulas rely on.
  3. Set Custom Aliases: (Optional) Rename advanced_valuation_v2 to something short like val to keep your formulas clean.
  4. Save and Share: Dependencies are saved directly into the workbook's hidden metadata (Custom XML). Just email the .xlsx file like any other.

For Sheet Users (The Recipients)

  1. Open the Workbook: Open the shared .xlsx file in Excel with the BlazeXL add-in active.
  2. Block Autodiscovery: BlazeXL detects the manifest and prepares the required Blaze Blocks.
  3. One-Click Consent: On the first formula execution, a security dialog appears. Once approved, the Blocks load instantly.
  4. Seamless Execution: All formulas execute exactly as the creator intended.

Consent Security

Security is at the heart of Blaze Sheets. BlazeXL never executes third-party code without explicit authorization.

Secure by Design

The "Consent Security" mechanism ensures that even if a sheet is shared publicly, no Python code runs until the user has reviewed and approved the Block dependencies.

The Consent Dialog

When a user opens a Blaze Sheet, they are presented with:

  • Block Identity: Name, version, and publisher of each dependency.
  • Source Verification: A "View Code" link that opens the Block in the BlazeXL Web Dashboard for full source review.
  • Persistence Control: Option to approve for the "Current Session" or "Remember" (save consent to local storage) for that specific Block/publisher combination.

Why Teams Love Blaze Sheets

1. Unified Logic for Organizations

Orgs can publish "Standard Library" Blaze Blocks (e.g., risk_models, pricing_engine). Analysts can then build sheets using these Blocks, and anyone in the org can open those sheets with the assurance that they are using the exact same logic as everyone else.

2. Immutable Versioning

Only published Blocks can be added to a manifest. Because published Blaze Blocks are immutable, your shared sheets are "immune to change" — they will work the same way today as they will in five years, regardless of how the creator's local workspace evolves.

3. Intellectual Property Control

Creators can share sheets that use Private or Org-Visible Blaze Blocks. Only users with the appropriate permissions (e.g., being in the same org) will be able to resolve those dependencies, protecting your proprietary logic while enabling collaboration.

4. Safer AI-Assisted Spreadsheet Workflows

Teams can use AI to help draft spreadsheet logic, then formalize the important parts as published Blaze Blocks. Blaze Sheets let those reviewed Blocks travel with the workbook without falling back to unmanaged local logic.

Example Use Cases

  • A finance team distributes a pricing workbook that always uses the approved pricing policy Block
  • A procurement team shares an approval sheet that resolves the current governed approval rules
  • A risk team sends a workbook to regional users while keeping the underlying risk logic version-pinned and centrally controlled

FAQ

Does this work on Excel Online?

Yes! Our Block dependency management system ensures compatibility across Windows, Mac, and Excel on the Web.

Can I use my own unpublished scripts?

No. To ensure reliability for the recipient, only published Blaze Blocks (Private, Team, or Org) can be added as dependencies. This guarantees the code will always be available when the recipient opens the file.

What happens if I rename a Block?

You can set a Custom Alias in the Dependency Manager. This allows you to use my_mod.func() in Excel while the manifest correctly points to actual_long_module_name_v5.func().

Next Steps

© 2026 BLAZE LABS PTY LTD. ABN 66 694 592 553. All rights reserved.
GitHub