View as and support access
View as lets an admin or ops person see every page as another person sees it, read-only. Support access lets a workspace admin allow Siftware support staff to do the same, for a limited time. Both live on one screen: Ops & admin > Access > View as.
What you can do
- Admin or ops: view as another person, to check what they meet. A banner reads "Viewing as <name> - read-only - Stop".
- Workspace admin: grant support access, and withdraw it.
- Siftware operator: start a support view of a person in a workspace that has granted access.
How to
View as (admin or ops):
- Open Ops & admin > Access > View as, or press the eye on a row of Team.
- Pick a person and start. Press Stop in the banner to end it.
Grant support access (workspace admin):
- Open Ops & admin > Access > View as and find the Support access panel.
- Choose how long: 1, 24 or 72 hours.
- Choose the scope: the whole workspace, or one person.
- Write a reason: what you want help with.
- Press Grant support access. Withdraw ends it early.
Start a support view (operator):
- Open the Support view panel on View as.
- Pick a workspace, then a person. A person the grant does not cover is listed but cannot be picked.
- Write a reason and press Start support view.
Limits
- Read-only. Nothing done while viewing is saved, sent or marked as seen for the person: writes are refused and mail, notifications and jobs are dropped.
- A view ends after 30 minutes, on Stop, or on sign-out. A support view also ends when the grant does. Only one view runs at a time.
- You cannot view as another admin or anyone who may use View as, a bot, an archived person, or yourself. A custom role does not get View as: it is for admin and ops.
- A support view needs a live grant. Without one it is refused.
- The workspace's admins are emailed before a support view starts.
- Every request, grant, withdrawal and start is audited, with the reason, in both the workspace's log and the operator's.
- The old Settings > Workspace > Support access screen is gone; its address redirects to View as.
- API tokens and agent connections are not affected by View as.