Organization variables
Overview
Organization Variables serve as the foundational elements for setting and managing configurations across different organizational levels within Rewst. They ensure consistency and control within workflows and facilitate efficient management across the organizational hierarchy.
Inheritance and Overrides
Inheritance: Values set at the parent organization cascade down, providing a default setup for all client organizations.
Overrides: Sub-organizations can establish their own variables, prioritizing local settings over inherited defaults.
Usage in Workflows
Access variables seamlessly in any workflow with the following syntax:
Naming Conventions
Employ descriptive and straightforward wording using
snake_casefor clarity.Prefix integration-specific variables appropriately, like
psa_for PSA-related variables.
Defining Boolean Values: always use lowercase true or false to align with Rewst's standardized practices. This uniform approach applies to all future workflow designs. Existing legacy workflows may display variations.
Use as Default Feature
The "Use as Default" feature allows managing organizations to set a universal default value for an ORG variable. This default is applied to sub-organizations unless they specify their own value.
How "Use as Default" Works
Setting a Default: When you set a variable as default at the MSP level, it becomes the fallback for sub-organizations without a specified value.
Workflow Execution Context:
The default value is only utilized if the workflow is initiated from the managing organization.
To apply the default value to Client A, the workflow must start from the MSP, even if it operates within Client A’s context.
Triggers and Context:
Implementing triggers in the workflow ensures that the execution context is recognized. This facilitates the use of MSP-level defaults in sub-organization workflows.
Onboarding Requirements
Certain ORG Variables are essential for onboarding processes and are utilized by the Get and Set ORG Variables Workflow to ensure smooth integration and setup for new users or systems.
Default PSA
default_psa
Identifies the PSA that you use
cw_manage kaseya_bms datto_psa halo_psa freshdesk servicenow mail_only etc
Default RMM
default_rmm
Identifies the RMM that you use
cw_automatecw_control datto_rmm immybot ninja_rmm n_able kaseya_vsa kaseya_vsa_x etc
Primary Identity Provider
primary_identity_provider
Specify where users are created for the organization, either on premise or in Azure
on_prem azure_ad jumpcloud
Default Ticket Location
psa_default_board_id
The default PSA board (or other organizing feature) that Rewst will use to create tickets on when running automations
(depends on psa)
Default Ticket Status
psa_default_ticket_status
The default ticket status that Rewst will use when updating tickets. This is the status that Rewst will use when actively working on a ticket. It usually set to "In Progress" or a similar status.
name or id of ticket status
Ticket Status while Waiting for Input
psa_ticket_status_waiting_input
The default ticket status that Rewst will use when tickets are waiting for user input. This applies in cases where the automation will pause and prompt a technician to do an additional step outside of the automation before then returning to the ticket to confirm that action has taken place. This will then kickoff the automation to continue from the position it left off.
name or id of ticket status
Ticket Status when Workflow Complete
psa_ticket_status_completed_task
The default ticket status that Rewst will use when we finish an automation. Consider this the "quality check" status to make sure everything ran properly.
name or id of ticket status
No Time in Tickets
psa_no_ticket_time
Set this when you don't want automation to put time_worked in tickets. The "Yes" option will add notes in the ticket we create when running an automation. The "No" option will let us impersonate a technician to apply time under there name for automations that run. We do this because we can't apply time via the API for most PSAs.
1 or 0 (boolean )
Default Tech ID
psa_default_tech_id
Tech Id to user when updating ticket time
id of tech to use for time entries
Default Work Role
psa_default_tech_workrole
Tech Work Type to user when updating ticket time
id of tech work type to use for time entries
Default Work Type
psa_default_tech_worktype
Tech Work Role to user when updating ticket time
id of tech work role to use for time entries
New User Ticket Type
psa_new_user_ticket_type
Ticket Type to use on the New User Board when creating a ticket
int for type_id in CWM
New User Ticket Subtype
psa_new_user_ticket_subtype
Ticket SubType to use on the New User Board when creating a ticket
int for subtype_id in CWM
New User Ticket Item
psa_new_user_ticket_item
Ticket Item to use on the New User Board when creating a ticket
int for item_id in CWM
Time Entry Ticket Status
time_entry_ticket_status
Set tickets to this status to enable time entry
strStatus Name or int ID to use
New User Approval Email
new_user_approval_email
When email approval is needed for new user adds, use this address
email address
Require Approval For New User
require_approval_for_new_users
Controls the new user approval requirement.
(1 or 0) or (true or false)
Require Authorization for License Purchases
m365_require_authorization_for_new_licenses
Pause workflows for Inquiry when new license purchases are needed
1 or 0 (boolean )
Require Approval For Offboarding Users
require_approval_for_offboarding_users
Controls the new user approval requirement.
bool
Offboard User Approval Email
offboarding_user_approval_email
When email approval is needed for offobarding users, use this address
email address
New User Password Save Location
new_user_password_save_locations
Where to store the password during new user creation. Default to PSA if not defined
List of psa``itglue``hudu``custom-pwpushother systems
New User Password Save Location Custom URL
new_user_password_save_location_custom_url
In the event that we are storing a password in a custom PWPush, put the URL here
User Start Date Action
user_start_date_action
How to handle start_date in user onboarding
default document_only : only show in ticket
Override Email Domains
override_email_domains
List of email domains to show rather than querying from M365
List of domains
New User Automation Task Time
automation_task_new_user_time
Default time for the "New User" workflow, to add to the ticket at completion
int in minutes
Offboard User Automation Task Time
automation_task_offboard_user_time
Default time for the "Offboard User" workflow, to add to the ticket at completion
int in minutes
VIP Contact Type
psa_vip_contact_type
Contact Type to set for VIP users
name or id of Contact Type
Adds a field on forms for specific approver email
new_user_manual_approver_field
Allows the field in New User to show up and add a specific e-mail approver
1 or 0 (boolean )
New Ticket for License Purchases
license_purchases_in_new_ticket
When prompting in tickets for license purchases, do so in a new ticket
1 or 0 (boolean )
Board ID for License Tickets
psa_license_purchase_board_id
The PSA Board ID to use when license purchases are in a separate ticket
int board_id for CWM
Active Customer Statuses
psa_active_customer_status
Statuses in PSA for active customer organizations
List of status types from PSA
Default Priority
psa_default_ticket_priority
The default ticket priority that Rewst will use when creating tickets
name or id of ticket status
Default Agreement Name
psa_default_agreement_name
If you set a default agreement in your PSA on ticket creation, enter the name of it here.
str name of agreement
Send From Address
psa_send_from_address
When sending mail, we can set the "replyTo" address to this, to allow for proper ticket responses
str email addr
Store Password in Ticket
psa_store_password_in_ticket
When documenting the password, this will never store it in the ticket if set to false
bool
Microsoft Licensing Distributor
ms_licensing_distributor
Microsoft License Distributor (where to purchase CSP licenses)
pax8 microsoft_csp ingram_microsherwebsynnexmanual_only
Mandatory Licensing Groups
m365_mandatory_license_groups
If you use license groups with Microsoft 365 you can specify those groups here. This allows you to create a group of licenses that the user will be added to if selected.
list of group_names
Username Format
username_format
The format of the users username
flast firstl firstmlast
Preferred Domain Controller
preferred_domain_controller
Choose this DC instead of letting automation decide
ComputerName in RMM
Preferred ADConnect Server
rmm_preferred_adconnect_server
If your ADConnect is on a specific server, specify it here
str hostname of server
On-Prem Exchange Server
onprem_exchange_server
Server name to use if you have on-prem Exchange
ComputerName in RMM
On-Prem Hybrid Exchange
onprem_hybrid_exchange