2.4 Important Terminology & Concepts

Overview

This section provides clear definitions of key terms used throughout Maestro. Each concept is intentionally concise and tied to its function within the platform to support quick onboarding and consistent understanding across teams.


2.4.1 Script

A Python-based automation executed within Revit using Maestro. Scripts modify elements, create content, run QA checks, or streamline repetitive workflows. Stored and managed through the Script Library.


2.4.2 Deployment

A controlled, enterprise-level distribution package that bundles scripts for firm-wide rollout. Ensures every user receives the same version of an automation. Managed by Super Users and Administrators.


2.4.3 Ribbon / Panel / Button

Customized user interface components created in the Ribbon Manager.

  • Ribbon: A top-level tab in Revit.
  • Panel: A grouping of buttons within a ribbon.
  • Button: A UI trigger that runs a script or opens a file, folder, or URL.

2.4.4 MVAR (Maestro Variable)

A parameter annotation within a Python script that prompts users for input at runtime.

Example:

my_var = <default_value>  # @mvar(type='<type>', display='<Optional Display Name>')

Used to create flexible, reusable automations without custom UI development.


2.4.5 Telemetry Event

A tracked action that records automation usage data. Includes script runs, success/failure counts, AI thread usage, and active user sessions. Accessible via the Maestro Online Portal.


2.4.6 Super User

An enterprise-level role with full permissions, including:

  • Script creation and editing
  • Deployment creation and publishing
  • Ribbon building
  • Access to all Maestro features

Acts as a local automation administrator.


2.4.7 Standard User

A user under an enterprise license with limited access. Can:

  • Run scripts
  • Use and create custom ribbons
  • Access deployments assigned to them

Cannot create deployments or modify high-level automation structures.


2.4.8 Script Library

The storage system for all scripts a user or firm manages. Includes:

  • Personal collections (free tier)
  • Centralized, version-controlled libraries (enterprise)
  • Script templates and reusable patterns

2.4.9 IDE (Integrated Development Environment)

Maestro’s built-in code editor used to create, edit, and debug scripts. Features:

  • Syntax highlighting
  • Console output
  • Execution feedback
  • Versioning

2.4.10 Execution Context

The Revit document and application state during script execution. Determines:

  • What elements can be accessed
  • Which models are open
  • What selections exist
  • How transactions behave

Understanding execution context is critical for predictable automations.