Sign-in
People sign in through your organisation’s own identity provider. Media Verdict keeps no passwords of its own.
| How it works | |
|---|---|
| Single sign-on | By OpenID Connect, through your identity provider. The console’s screens and their data views need a signed-in session. |
| Two factors | The installation’s sign-in requirement for the approver and admin roles, met through your organisation’s single sign-on. |
| Roles from your groups | Each group in your identity provider maps to one of the five roles. A group that is not mapped grants nothing, and a person with no mapped group gets no session. |
| The session | A signed cookie that holds the person’s id, name, roles and expiry, and never a token from the identity provider. It lasts 12 hours by default. |
| People on record | Each user is mirrored from your identity provider and holds no credentials. Every write carries the user’s id; approvals, rule changes and settings changes also need a reason. |
| Development sign-in | A local sign-in exists only in a development build with no identity provider set, and is never part of any other build. |
Who may do what
A person can hold more than one role. Each action is checked against the roles the person holds when they act.
| Action | Analyst | Approver | Policy owner | Admin | Viewer |
|---|---|---|---|---|---|
| Read the console’s screens | Applies | Applies | Applies | Applies | Applies |
| Label items, and open and work on cases | Applies | Labels escalated items only | Does not apply | Applies | Does not apply |
| Close a case, which seals its evidence pack | Does not apply | Applies | Does not apply | Applies | Does not apply |
| Change the watch list and start or stop collection | Applies | Does not apply | Applies | Applies | Does not apply |
| Write rules and try them on past data | Does not apply | Does not apply | Applies | Applies | Does not apply |
| Draft and edit a response | Applies | Does not apply | Does not apply | Applies | Does not apply |
| Approve and send a response, when not its drafter | Does not apply | Applies | Does not apply | Does not apply | Does not apply |
| Release an external report | Does not apply | Applies | Does not apply | Applies | Does not apply |
| Change a protected setting in production, with a second person’s acknowledgement | Does not apply | Applies | Does not apply | Does not apply | Does not apply |
| Change other settings in production | Does not apply | Does not apply | Applies | Does not apply | Does not apply |
How access flows

1
A person
Opens the console and is sent to your identity provider.
2
Your identity provider
Signs the person in by single sign-on and passes on the groups they belong to.
3
Groups to roles
The person’s groups map to the five roles. The two marked in red, approver and admin, are required to sign in with two factors.
4
The console
Screens and data views open under a signed session that expires after 12 hours by default.
5
The audit log
Every write the person makes is recorded with their id.
Each person’s own trail
The Users screen lists every person mirrored from your identity provider, with their two-factor status, their last sign-in and their own audit trail.
A reviewer can open one person and read every change they made, every approval they gave and every action they sent, in order.
In production, a change to a protected setting needs an approver and a second person’s acknowledgement, signed from that person’s own signed-in request; a user id typed in by someone else does not count.

What is not claimed
This page claims no security certification and no outside audit. Each statement on it describes how the product is built and configured, so it can be checked on an installation.
Two factors are the installation’s sign-in requirement for approvers and admins, met through your organisation’s single sign-on; this page does not claim that the product itself verifies the second factor. No such requirement is set for analysts, policy owners or viewers.
The product holds no passwords. It holds none of the tokens of your official accounts either: your social desk connects those to the outside sending service on its own machine.
Map your organisation’s groups to these five roles with your identity team before the first sign-in.
Request a demo/trust/security · Security and sign-in