View as
View as lets the owner of Hydra see the app exactly as one staff member sees it: their chats, design cards, Images, Devices and Inbox. It exists for support: to reproduce a problem someone reported. Nothing can be done in their name while it is on.
What staff can rely on
- Only the owner can use it. Admins and other staff cannot, and the owner cannot view as another owner.
- It is read-only. Every action that would change something (sending a message, saving, deleting, starting a turn) is refused with Read-only while viewing as and the person's name. Their designs open for looking, never for editing.
- It is time-limited. At most 60 minutes, 30 by default. Then it ends by itself.
- The person is told. When it ends, they get an Inbox note from Hydra: who viewed, from what time to what time, that it was read-only, and the reason that was given.
- It is on the record. The audit log keeps
viewas.start,viewas.stopand every refused write (viewas.refused), with the owner as the real actor.
Starting it
- Open System → People.
- Press View as on the person.
- Write the reason. It is required, at most 200 characters, and the person reads it, so write it for them. For example: "Mai reported that the dispatch sheet card never fills in; checking her chat from this morning."
- Choose the minutes.
The app then opens as that person.
What the owner sees
While it is on, a bar across the top of every page says Viewing Hydra as with the person's name and email, that it is read-only, and when it ends. The bar cannot be hidden. Stop ends the view at once and returns to the owner's own view of the same page.
When to use it, and when not
| Use it to | Do not use it to |
|---|---|
| See an error message exactly as the person sees it | Read someone's chats out of curiosity: the person is told, and it is in the audit log |
| Check that a role or a team gives the right pages | Do work for someone: it cannot write |
| Check a device or integration shows the right account | Test as a role in general: use a test account with that role instead |
Related
- Roles and approvals: who is the owner, and what each role can do.
- Devices and privacy: what Hydra keeps about each device.