Allow for parent-child relationships between Roar Environments | Voters

Allow for parent-child relationships between Roar Environments

under review

Matt Miller

Allow for a single top-level environment in Roar that has child Environments. This would allow "child" Environments in Roar to sync to different Organizations/Accounts in our platform integrations like IT Glue, allowing for more flexible organization of MSP end-customers.

May 29, 2019

Paul Martin

We need this too. We have many clients who have many sites all of which have accounts or environments in our PSA tool (Autotask) and ITGlue, with have parent-child associations. We've recently introduced Roar and we're a little misaligned across our systems. When we sync Office 365 (via CSP), Webroot, Auvik, AD we're left with two options which both have a rub. Choosing just one Roar environment (which one of our clients many sites?) to attach this information too; Or, we create custom/duplicate inspectors to attach the same information to each Roar environment, which then causes duplicate information and potentially duplicate alerting and duplicate Alert tickets with PSA integration - we could then create some custom/complex Alert templates to ensure we don't get duplicate Alerts/tickets but by this stage instincts are ringing that this is untenable. Surprised this only has 5 votes so far! We need this as I'm sure many others will do too. Many thanks.