Skip to main content

Viewing the app as a member

Added in v0.72.0. When a member reports "the Billing page shows the wrong balance" or "I can't find the document you sent," the fastest way to understand it is to look at their screen. View as member lets you do that without asking them to share a screen or hand over a password.

Starting a session​

There are two ways in. Both open the same dialog and start the same session.

From anywhere, using the profile menu​

Added in v0.72.2. Use this when you already know who reported the problem.

  1. Click your name in the top-right corner → View as member.
  2. Start typing the member's name or email, then pick them from the list.
  3. Type a reason.
  4. Click Start read-only session.

The list only offers members you are actually allowed to view as, so anyone covered by Who cannot be viewed below simply will not appear — including yourself.

From the member's record​

Use this when you are already looking at someone's profile.

  1. Open Members → the member → the Security card.
  2. Click View as member.
  3. Type a reason.
  4. Click Start read-only session.

The reason is required either way, and it is not a formality — it goes into your organization's audit log and into the email the member receives.

The app reloads as that member: their navigation, their chapter, their data. A persistent amber banner across the top names who you are viewing, counts down the remaining time, and holds the exit button. It stays there no matter how far you scroll, and it survives a page refresh — you should never be uncertain about whose account you are in.

What the session can and cannot do​

✅ Read any page the member can readTheir dashboard, invoices, courses, documents, forums, events
❌ Change anythingNo posting, paying, voting, RSVPing, or editing — every write is refused
❌ Their credentialsPassword, passkeys, linked email addresses and consents are unreachable
❌ Their direct messagesThe Messages area is closed for the whole session
❌ Live featuresChat and live election tracking do not connect during a session

The read-only rule is enforced by the server, not just hidden in the interface — a session cannot write even if a page tries.

:::note Why messages are excluded Nothing else in GreekManage lets an admin read a member's private conversations, and a support tool is not the place to start. If a member reports a messaging problem, ask them to describe it or share their screen. :::

Who cannot be viewed​

  • Platform admins, org admins and regional admins — including admins of other organizations who happen to also be members of yours. Ask a co-admin to share their screen instead.
  • Members with a pending password change, who would land you on a screen the session is not allowed to submit.
  • Disabled accounts.
  • Yourself.

Chapter officers can be viewed — you already have more reach than they do inside your own organization, and officers are often the ones reporting problems.

The 30-minute limit​

Sessions end automatically after 30 minutes and cannot be extended. When one ends — whether you exit or it times out — you are returned to your own account, not signed out. If you need longer, start a fresh session; that re-runs every check and writes a new audit entry, which is the point.

A session also ends immediately if your admin role is revoked, or if the member is removed from your organization, while it is running.

What gets recorded​

Every session writes two audit entries — one when it starts, carrying your reason and the deadline, and one when it ends. Both are attributed to you.

Anything you look at during the session is recorded against the member, because that is genuinely who the request authenticated as, with your name stamped alongside it. That distinction matters: it means the audit log can always tell the member's own activity apart from an admin looking through their account.

The member's notification​

By default the member is emailed as soon as a session starts. The email names you, quotes your reason, and explains what the session can and cannot do.

Org admins can turn this off in Settings → General. Turning it off only suppresses the email — the audit entry is written either way. We recommend leaving it on: it is what makes the feature straightforward to explain if a member ever asks why someone was in their account.

One session at a time​

Sessions live in your browser, so you can only hold one at a time, and you cannot start a second from inside one. Exit the current session first.

See also​