How Romy is built
Three pictures show the path of a question, the four access levels and the path of a release to you.
Who it is for
For anyone who wants to understand how Romy is built before they consent. Especially for IT security and data protection.
Why this page exists
Three pictures show the path a question takes, which levels of access exist and how a release reaches you. Gold marks the places where a person decides.
The path of a question
Employees message Romy in Teams. Romy recognises the organisation, the person and their device, and asks by card. Only after the click does a signed order go to the Romy App. Romy Studio sees every step.
- 1
Employee
messages Romy in Teams
- 2
Romy
recognises org, person and device
- 3
Card to confirm
the person clicks
- 4
Signed order
to this device only
- 5
Romy App
reads or acts on the device
- 6
Result card
in the same chat
- 7
Romy Studio
sees every step (Loki, Grafana)
The four access levels
Each level is a separate decision on your side, and you can revoke each one on its own. Level 3 is approved by the person themselves, every time.
- 1
Read on the device · Romy App for Windows
Intune admin deploys the app, reads only when someone asks
- 2
Read from Microsoft 365 · Romy Diagnostics
Microsoft 365 admin, one consent, “Read” permissions only
- 3
Act on the device · Romy App for Windows
the person themselves, in Teams, only after confirmation, signed order
- 4
Change Intune · Romy account in your role
Intune admin grants the role, 5 permissions, pilot group only, tag ROMY
How a release reaches you
Every release runs at Romy first, then with customers who test early, and then for everyone. Your admin installs it when you want.
- 1InternalWe test every new version ourselves first.Nothing changes on your side.
- 2BetaFor customers who want to test earlier.After one day at the earliest, weekdays at 10:00.
- 3StableYour default. This is what customers get.Two days after Beta at the earliest, Tuesdays and Thursdays at 10:00.
- 4Your devicesYour Intune admin installs it.Whenever you want. Nothing arrives by itself.
How do I find out?
Every new release appears on the Releases page, with every file and its SHA-256. No release arrives unannounced.
To the filesWhat do I do?
Your Intune admin uploads the new Romy App. If the Teams package is new, your Teams admin uploads that too. It takes about 10 minutes.
Setup, step 11How do I see it has arrived?
Ask Romy in Teams “Which version are you?”. The answer names the version on your device.
How do I roll back?
Upload the previous version from the Releases page again. Romy takes a faulty release out of the channel within one hour.
Freeze and rollbackHow we approve a release
A release only moves on if it meets every condition. If a measurement is missing, it does not move. A person at Romy approves every move.
From Internal to Beta, if
- The release ran at Romy for at least a day.
- Every device check ran without errors at least three times on both test devices, with exactly this Romy App.
- At least 95 percent of our chat tests passed.
- In those tests Romy did nothing it was not allowed to do.
- Every device check is monitored and raises an alert if something fails.
From Beta to Stable, if
- The release ran in Beta for at least two days.
- Since Beta, every device check ran without errors at least five times on each device.
- In Beta, Romy solves problems at least as often as internally at Romy.
Anything finished in the 2 hours before a date waits for the next one. A version that was taken back never returns to the same channel.
Keep reading
The guides belong together. Each one explains one part of the path.