# Use Device Facts as Custom MDM Profile Variables [Use Device Facts as Custom MDM Profile Variables – Addigy](https://support.addigy.com/hc/en-us/articles/4403542462099-Use-Device-Facts-as-Custom-MDM-Profile-Variables) # Custom MDM Profile Variables Addigy Custom MDM Variables allow you to save variables within your Addigy Organizations that can later be used in Custom MDM Configurations. Addigy Custom MDM Variables are configured at the API Level.^[[Addigy Custom MDM Variables – Addigy](https://support.addigy.com/hc/en-us/articles/4403549706259)] # Huntress Huntress is an example of passing the name of the top-level [[Addigy Policies|policy]] into the script to match the organization key during installation. This script was before variables were publicly available. ```bash # If the organization key is passed as a parameter, it will be used instead of this defaultOrgKey variable. # If you have a preferred "placeholder" organization name for Mac agents, you can set that below. # defaultOrgKey="__ORGANIZATION_KEY__" ############################################################################## ## In many multitenant environments, the Top-Level Addigy Policy name ## matches the name of each Organization. If you wish to dynamically use the ## Top-Level policy name as your Organization Name, you can pull the ## $POLICY_PATH environment variable from Addigy's Policy pipeline. ## ## For this method, comment line 56 above and uncomment lines 67-68. ############################################################################## topLevelPolicy=$(echo ${POLICY_PATH} | awk -F ' \\| ' '{print $1}') defaultOrgKey="$topLevelPolicy" ```