Signing in, team and roles¶
How sign-in works¶
The console at app.sheersight.io sits behind Zero-Trust access. Before any
page loads, you prove who you are with:
- your organization's Google or Microsoft account, or
- a one-time PIN sent to your work email.
The console then checks your verified email against your organization's member list. An email that isn't on the list is turned away, even if it signed in successfully. This check runs on our servers on every request, not just in your browser.
Roles¶
Every member of your organization has one of three roles.
| Role | What they can do |
|---|---|
| Admin | Manages the team, connects integrations, approves actions. Sees everything for your organization. |
| Analyst | Investigates and answers questions on incidents. Sees everything for your organization, but can't change the team. |
| Viewer | Read-only access to incidents, alerts and reports. |
An organization always has at least one admin. The console won't let you remove or demote the last one.
Who can see your organization's data¶
| Who | What they can see and do |
|---|---|
| Members of your organization | Your organization's console, within their role (see above). |
| SheerSight analysts (Sheer Safe staff) | Your organization's console, to run the service: setting up your instance, starting and stopping sources, upgrades, and alert triage. Every action they take is written to your activity log under their own email. |
| Anyone else, including other SheerSight customers | Nothing. Asking for another organization's data returns "not found", so the existence of other customers isn't revealed. |
The console never sees the credentials you connect in readable form. They're encrypted in your browser and only your dedicated instance can decrypt them. Sheer Safe administers that instance for you, so our administrators can access it when maintaining or supporting it. See Security & trust.
The Team page¶
Open Settings, then Team. Everyone in your organization can see the list of members and their roles.
Admins also see when each person was added and by whom, and whether they have signed in yet ("Invited, hasn't signed in yet" or "Last active 3 days ago"). Analysts and viewers see email and role only.
Confirming team changes with your authenticator¶
Adding someone, changing a role and removing someone all need a code from your authenticator app. One code covers further changes for the next 10 minutes. A recovery code works in place of an app code.
If you haven't set up an authenticator yet, the console asks you to do it first. Go to Settings, then Profile, and follow the setup steps there. Keep your recovery codes somewhere safe.
Inviting colleagues¶
Admins can invite people:
- On the Team page, select Invite.
- Enter one or more work emails (up to 20 at a time, separated by commas or new lines) and pick a role.
- Enter a code from your authenticator when asked.
Each email gets its own result: added, already a member, or not a valid email. Inviting someone who is already a member doesn't change their role.
SheerSight doesn't send an invite email yet. Tell your colleague they can sign in
at app.sheersight.io with that email, or use Copy sign-in link on their
row and send it to them yourself.
An email can belong to only one organization. If it already belongs to another SheerSight customer, the console says so; email support@sheersafe.com and we'll sort it out.
Changing a role¶
Admins pick the new role from the person's row. Switching between analyst and viewer applies straight away, with a short window to undo. Making someone an admin, or taking admin away, asks you to confirm first.
Removing someone¶
Admins can remove any member from the row menu. They lose access on their next request. Their past answers and comments stay in the activity log.
Leaving an organization¶
Any member can leave: on the Team page, choose Leave on your own row and confirm with your authenticator. You lose access straight away. If you're the only admin, make someone else an admin first.
Signing out¶
Account menu (top right), then Log out. This ends your Zero-Trust session.
When someone leaves your company¶
Remove them on the Team page, and disable them in your Google or Microsoft account as usual. Once their identity account is disabled they can't complete sign-in anyway, but removing them from the member list closes access in both places.