📋 GRC compliance for CMMC 2.0, CPCSC, CPA Canada, IIROC…SaaS discovery for data governanceFree enriched web chat widget🚀 Enriched remote support without your laptop

Custom scripting

Simple and powerful custom scripting

Annoyed with how RMMs make scripting either overly complicated or immensely inefficient? Lavawall® takes a straightforward approach that even automates the automation. Paste a script, pick a platform, and deploy it across the right organisations with placeholder variables so you never maintain a dozen near-identical copies.

Start free, no credit card See placeholder variables

Batch · Bash · PowerShell · Zsh · per-organization access

Enter a script with the defaults

Creating a script takes four steps. Start typing a title, enter an optional short description, paste your script into the Contents field, and click Save. Choose the platform and Lavawall® selects the interpreter for you.

  • Mac automatically uses Zsh.
  • Linux automatically uses Bash.
  • Windows defaults to PowerShell, and you can select Batch instead.
adding a new script with the default fields in Lavawall
choosing the platform and interpreter for Linux, Mac, or Batch

Make scripts easier to find

Assign a category so your library stays organised. The predefined categories are AWS Management, Diagnostics, Free Disk Space, General Scripts (the default), Hardware Information, Management Facilitation, OS Maintenance, and Tools.

A default icon is chosen based on the category you select, but to make scripts even easier to spot you are welcome to pick from many additional icons.

searching and selecting a script category in Lavawall
an AWS Management category script in Lavawall

Limit access by organizations

By default, all of your organisations can access your script. If you would like to limit access to users and devices within specific organisations, you can select them from the Allow this script for the following Organizations field. Start typing to filter, and add as many organisations as you need.

searching for an organization to grant script access
granting script access to multiple organizations at once

One script to rule them all

Instead of having to upload separate scripts for each company because an argument is different, Lavawall® lets you use placeholder variables within scripts. Variables use a double curly-brace format, for example {{variable_name}}.

Since these can be easy to forget or miss, the system automatically adds a list of the variables found in your script to the Organization Variables field, so you always know exactly what each organisation needs to supply.

the full add-script form in Lavawall with contents and variables

Powerful customisations

Most scripts run well with system-level permissions. However, sometimes you need to run Windows scripts in the user context, so a Run as Logged-in User checkbox is available. These scripts may fail on certain headless servers and in other user circumstances, so the setting is left off by default.

the Run as Logged-in User option on a Windows script

Try Lavawall® scripting free →

Free plan · no credit card · month-to-month

Frequently asked

Which scripting languages does Lavawall® support?
Batch and PowerShell on Windows, Bash on Linux, and Zsh on macOS. When you pick a platform, Lavawall® selects the right interpreter automatically, and on Windows you can choose PowerShell (the default) or Batch.
How do I reuse one script across many organizations?
Use placeholder variables written as double curly braces, for example {{variable_name}}. Instead of uploading a separate script per client because one argument differs, you write the script once and Lavawall® fills the value per organisation. Any variables it finds are added to the Organization Variables field automatically.
Can I limit a script to certain organizations?
Yes. By default every organisation can access your script, but you can restrict it to specific organisations using the Allow this script for the following Organizations field.
Can a script run in the logged-in user's context?
Yes. Most scripts run well with system-level permissions, but you can tick Run as Logged-in User when a Windows script needs the user context. It is off by default because such scripts can fail on headless servers and in some user circumstances.