Checklists

Who it is for

For the person who owns the launch.

Go through the first list before launch and the second one in the first week.

The channel is chosen (we recommend stable), pilot devices and pilot people are decided.
Consent for Romy Diagnostics is granted. It contains “Read” permissions only.
The role “Romy App Installer” has 5 permissions and applies to “Romy Pilot Devices” only.
The Romy App is “Installed” on at least one pilot device, and you have seen the notice page.
Custom apps are allowed in Teams for the whole organisation.
Romy on Teams is available to the pilot group. Neither “Everyone” nor “No one” is selected.
If you have custom setup policies, pin Romy there too. The global policy is not inherited.
The pilot people are entered at Romy, and one person from IT has tried the first chat themselves.
You know whom to reach at Romy operations for a rollback or a block.

Tell the pilot group that Romy is in Teams, asks before any change, and that the notice page explains the rest.
In the first week, go through the results in the Studio trail with Romy operations every day.
Confirm your channel. New releases appear on the Releases page first and never arrive unannounced.
Widen the circle by adding devices to “Romy Pilot Devices” and extending “Available to”.
Later, everyone gets Romy pinned to the sidebar with a setup policy.