Global Shell Apps and Account Variables without using Inherited variables

Hi Zach Pierce 

I'm wondering if this would solve your use case:

• Create an Inherited Variable at the MSP level and give it a placeholder value (or leave empty).
• On the customer level for the customers that the logic should be executed for, override the Inherited Variable value with the customer-specific value.
• In your Shell App script, only execute the required logic if the variable value is not equal to the placeholder.

For customers that don't have a value assigned, the script will execute successfully but will have no impact. For customers with a custom value, the script runs the logic you want using the customer-specific value without exposing it to other accounts.

Please let me know if this indeed enables your use case. If not, I'd like to understand more to see what would be needed.

Hi Gido,

I'm currently using this as a workaround so it is functional, but not optimal. I'm saving certain items, license keys and such into a secure variable. I'd love to create my shell apps at the global level to reference that. The inherited variable is a functional method but if I need to exclude an account or add it when I onboard a new client, it becomes messy quickly.