Set up Romy
Who it is for
For the admins who bring Romy into your organisation, covering Microsoft 365, Intune and Teams. Often that is one person. Romy operations joins at three points.
Why
So you know what lies ahead before you start. Each page says who does the step, why, with which permission, how long it takes, how to check it and how to undo it.
The order
Work through the pages from top to bottom. Each one is short and ends with the way to the next.
- Roles and permissionsFive roles and the steps they take
- Prepare and consentChannel, pilot group, sign-in and reading
- 1Intune setup (RBAC)Groups, scope tag and role
- 2Romy App for WindowsDeploy it and approve the device
- 3Romy on TeamsInto the org catalog, pilot group first
- 4Enable your employeesName the pilot people and the first chat
- Install a new releaseCheck, upload, done
- Check and roll backFor each step, the check and the way back
- ChecklistsBefore launch and in the first week
Every step with its time
10 steps make up the default path, one is optional. Teams is the default, and the Romy App only acts when the person confirms.
| Step | Who | Time |
|---|---|---|
| 1Choose channel and pilot group | Microsoft 365 admin | 15 minutes |
| 2Sign in to the Romy Platform | Microsoft 365 admin | 2 minutes |
| 3Let Romy Diagnostics read | Microsoft 365 admin | 2 minutes |
| 4Create groups, scope tag and role | Intune admin | 10 minutes |
| 5Deploy the Romy App for Windows | Intune admin | 15 minutes, plus up to 1 hour until Intune reaches the device |
| 6Approve the device in Romy Studio | Romy operations | a few minutes |
| 7Deploy Romy on Teams | Teams admin | 10 minutes. Policies take up to 24 hours to apply |
| 8Name the pilot people | Romy operations | 5 minutes |
| 9The first chat | Employees | 1 minute |
| 10Act through Intune with a service accountoptional | Intune admin | 10 minutes |
| 11Install a new release | Intune admin, Teams admin | 10 minutes per release |
