Experimental

Experimental is the shelf where new ideas live before they earn a place in the main navigation. Everything here is real and works against your real data, but none of it carries the compatibility promise the rest of the platform does: a card can change shape, move elsewhere, or disappear between releases.

Where to find it

Extra → Experimental in the sidebar. It requires the permission to change global settings, so it is an administrator surface.

What you will find there

The page is a grid of cards, each opening one prototype:

Tool	What it does
Requirements explorer	Visualises every requirement across every audit in one place, instead of one audit at a time
Findings	A combined review of findings across binders
Batch Creation	Creates many assets, entities or feared events at once from a plain text list — one name per line
Library Builder	Authors, adopts or clones custom libraries and publishes them through the standard loader
Bulk evidence upload	Uploads many files, or a whole directory, as evidences — with conflict strategies (skip, add revision, replace, rename) and checksum-based duplicate detection
Questionnaire Autopilot	Uploads a customer security questionnaire as a spreadsheet, scopes it to a domain, and maps its columns
Asset Whiteboard	Places and links assets on a freeform canvas per domain; edges you draw update the real parent-asset relationships, while positions stay in your browser
Analytics Export	Exports the analytics dashboard data as a multi-sheet workbook — summary, risk levels, compliance, controls, incidents — ready for a reporting tool

A related prototype sits outside this page: open a requirement mapping set and the View on graph explorer link draws the mapping between two frameworks as an interactive graph, which is considerably easier to read than the table when you are checking coverage.

Setting expectations

Caution

Prototypes are not a supported part of the product. Before you use one on real data, assume that: its screen may change without notice; it may not enforce the same validation as the mainstream forms; and it will not necessarily be there in the next version. Nothing here should sit in the critical path of an audit deadline.

That said, the tools fall into two honest categories, and it is worth knowing which is which:

• Bulk operations — Batch Creation, Bulk evidence upload, the Library Builder. These write real objects through the normal APIs. What they create is ordinary data, so if a tool disappears, everything it produced stays exactly where it is. These are the ones safe to lean on.
• Alternative views — the explorers, the whiteboard, the graph. These mostly read. Losing one costs you a viewpoint, not data. The Asset Whiteboard is the exception worth noting: edges you draw do change real parent-asset links, while the layout itself only lives in your browser, so a colleague opening the same board sees a different arrangement.

Tip

Use the bulk tools for the tedious first pass — dumping an asset list, loading a folder of evidences — then finish and maintain the records through the normal module pages, where the full validation and history apply.

Related

• Data wizard — the supported route for bulk import from Excel.
• Libraries — where built libraries are loaded.
• Evidences — the destination of a bulk upload.