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-onBy OpenID Connect, through your identity provider. The console’s screens and their data views need a signed-in session.
Two factorsThe installation’s sign-in requirement for the approver and admin roles, met through your organisation’s single sign-on.
Roles from your groupsEach 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 sessionA 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 recordEach 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-inA 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.

ActionAnalystApproverPolicy ownerAdminViewer
Read the console’s screensAppliesAppliesAppliesAppliesApplies
Label items, and open and work on casesAppliesLabels escalated items onlyDoes not applyAppliesDoes not apply
Close a case, which seals its evidence packDoes not applyAppliesDoes not applyAppliesDoes not apply
Change the watch list and start or stop collectionAppliesDoes not applyAppliesAppliesDoes not apply
Write rules and try them on past dataDoes not applyDoes not applyAppliesAppliesDoes not apply
Draft and edit a responseAppliesDoes not applyDoes not applyAppliesDoes not apply
Approve and send a response, when not its drafterDoes not applyAppliesDoes not applyDoes not applyDoes not apply
Release an external reportDoes not applyAppliesDoes not applyAppliesDoes not apply
Change a protected setting in production, with a second person’s acknowledgementDoes not applyAppliesDoes not applyDoes not applyDoes not apply
Change other settings in productionDoes not applyDoes not applyAppliesDoes not applyDoes not apply

How access flows

Media Verdict console
1 2 3 4 5
IllustrationNumbers match the five steps beneath. Red marks the two roles that need a second factor.
  1. 1

    A person

    Opens the console and is sent to your identity provider.

  2. 2

    Your identity provider

    Signs the person in by single sign-on and passes on the groups they belong to.

  3. 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. 4

    The console

    Screens and data views open under a signed session that expires after 12 hours by default.

  5. 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.

Media Verdict console
IllustrationEach row is one write the person made, in order: when, what and on what. The two-factor status is left blank; the red square marks an approval the person gave.

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