Experiment Leases

When experiment leases are enabled in a schema, an experiment’s inputs and/or outputs are locked by default and cannot be edited. To make changes, users must request a lease, which grants temporary editing access for a defined period. This feature is optional and can be enabled in the Company-Wide Settings.

Leases are particularly helpful when you want to:

  • Require users to have a reason for editing finalized data.
  • Maintain a clear record of who changed what and when.
  • Allow edits only during experimentation, while ensuring data is locked immediately afterward.

How to Enable Experiment Leases

To enable leases within your schema:

  1. Navigate to Company Wide SettingsChange Control tab.
  2. Toggle on either (or both):
    • Require leases for editing experiment inputs
    • Require leases for editing experiment outputs
  3. Set the lease duration in the Lease duration in minutes field.
    • This determines how long a lease will remain active.
    • The default is 60 minutes, but this can be adjusted as needed.

Once enabled, experiment data will become locked by default. Users must explicitly lease experiments to make edits.

How Experiment Leases Work

When leases are enabled:

  • A pink key icon 🔑 appears in the experiment header if inputs or outputs are locked.
  • Users cannot edit inputs or outputs unless they have an active lease.

To lease an experiment:

  1. Click the key icon in the experiment header.
  2. In the modal, select a Request Reason from the dropdown:
    • Results Entry
    • Modification during Experiment Run
    • Modification during Results Entry
  3. Click Lease.

This will grant editing access to all experiments currently in view for the specified lease duration. Once the lease expires, the data becomes locked again and a new lease must be requested to make further changes.

Details about experiment leases are stored in the experiment’s audit log. To review lease activity:

  1. Open the experiment.
  2. Use the Search Action button to access the Audit Log.
  3. The Audit Log stores information on lease requests, such as:
    • Who requested the lease
    • When the lease was granted and for how long
    • What fields were edited during the lease
    • A full history of changes made under the lease
Updated on April 25, 2025

Was this article helpful?

Related Articles