Crates

The current M365 Onboarding crate does not set the ticket owner as the form submitter, it uses an org variable to use the default user at the org in the ticket.

Most of the Rewst-provided Microsoft crates have built-in ticket implementation so you can put an existing PSA ticket number or create if left blank, but the Add or Remove Group Membership one does not have that. It is absent in the form and corresponding workflow. It would be great if this feature could be added so that we don't need to alter/unsync the workflow. Thank you!

The original Offboarding crate would document the groups the user was being removed from in the default PSA notes. The new version does not. Customers will request we model a new user after an already terminated user, so it is important we document what groups the user belonged to. Things like licenses, mailbox access, etc. would also be useful to have automatically documented for the same reason specified above.

Would be great to have an option to keep certain groups memberships with the offboarding form in the crate. One example in our use case is we have a group that keeps mailboxes backed up by Veeam, and some clients require the offboarded users' shared mailbox stay backed up.

Would allow for adding a new hire to SharePoint groups (for those using SharePoint online)

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!

A form to grant accesses outside of usual working country. Give options for country or countries of travel & return date to the US. Option for a cruise generator as that might have multiple countries / different limitations. Most important piece would be the aspect of the return date and removing the employees exceptions.

When you install a crate, if the crate is built to support multiple PSA or RMM integrations that you don't have, the list of workflows is generally very long. In a perfect world, installing a crate would only install the components of the crate that are useful to the partner. Absent that ability, what if there was a way to hide/filter all workflows that meet exclusion criteria defined by the partner.

To alert when end clients Sharepoint storage is reaching capacity similar to the mailbox quotas to proactively prevent shut down of Sharepoint sites past capacity.