Crates

Example: Microsoft onboarding crate -> Sub workflow "REWST - OPT GEN Get Unique Attributes from All AD Users -> never seems to check BYOD database like other onprem option generators Utilizing BYOD (particularly with datto RMM) GREATLY speeds up the process for filling out new hire forms. Would be great if any on prem data checks were stored in BYOD database !!

Customer would like an "uninstall crate" button. Desired functionality would allow them to quickly delete all elements unpacked as part of a crate. This is especially important when crates are replaced with new versions. They suggested a wizard that allows the user to view and select all elements of a crate, with a "used in x number of crates" indicator so they could deselect shared sub workflows, and then click "delete all selected."

Add a crate that documents Google Workspace environments, similar to how Document M365 Environment works for Microsoft 365. This would help automatically capture and inventory key details (users, groups, licenses, settings, etc.) across Google tenants.

Something similar to the crates below would be awesome to have to help manage contacts for the few clients we have on Google Workspace. Similar to these, but source from Google Workspace instead of On-Prem or Azure AD: Sync On-Prem Users to CWM Contacts Sync AzureAD Account Information with ConnectWise PSA Contacts (v3)

I'd love a workstation offboarding crate/form that allowed us to choose the PC being removed and have it pull the endpoint from AD/Automate/Control/huntress/literally everywhere. As important as removing users is removing a endpoint is close to important in my mind.

The Offboarding instructions for the M365 Offboarding Crate https://docs.rewst.help/documentation/crates/existing-crate-documentation/microsoft-user-offboarding-crate do not properly call out the requirements for the Disabled Users OU. The user must remain in a synced OU in order for the workflow to complete successfully for Hybrid Accounts. All subsequent Exchange Online actions will fail if the user is moved to an unsynced OU. The form field note should also be updated to read something like: "Warning - Moving to an OU that is not synced will delete the account in M365 and cause all Exchange-related workflow actions to fail."

Pulling logs from O365, identifying and rectifying malicious mail flow rules. Grabbing forensic data from cloud & end-user devices

We are hoping that a button can be added for 'If Ticket Exists', that would then provide a field for 'Existing Ticket Number' to be entered. Currently, the automation is creating a new ticket each time the automation completes. Our team would like for the automation to update the existing ticket, instead of creating a new one if a current ticket exists in HaloPSA. I have included a screenshot below that shows the current automation. I understand that we can clone the workflow and adjust it as needed. However, our team would like to continue to leverage the workflow maintained by Rewst if this can be added. Thanks!

I would love a crate that would allow us to move a prospect to client status in manage and have it then build out the onboarding checklist and do most of if not all the work. Create autoelevate,duo,huntress,immy,synnex, etc. Sophos would be big for making a monthly client then pulling in the install link to immy and setting up the deployment for onboarding.

"Hey, can you enable mailbox forwarding for xyz user starting on Friday, through end of next week?" Enabling and disabling mailbox forwarding is great and all, but we receive so many tickets asking for forwarding to be enabled at a later time or date. Our team would love to have the workflow account for this and provide the option to delay activation or de-activation of mailbox forwarding.