Roles and permissions

Signicat Mint uses roles in the Signicat Dashboard to control who can build workflows, manage settings, view analytics and inspect journey data.

To use Mint, a user needs the Account Viewer role and at least one Mint role, as shown in the Mint roles overview below.

When your Mint workflows use features from other Signicat products, you need to verify that those products are enabled on your account and review the access provided by the Mint role, as explained in the Access to Signicat products section.

Managing roles and permissions

To learn how to invite users and assign roles in the Signicat Dashboard, see Managing roles and permissions.

Mint roles overview

The table below lists Mint roles and the access each role grants:

Role descriptions

Mint Administrator: Grants full Mint access. Users can create, update, publish and delete workflows, manage form profiles and secrets, view analytics, and manage journey data containing personally identifiable information (PII).
Mint Editor: Grants access to create, update, publish, review and delete workflows. Users can also manage settings and access journeys, PII and analytics.
Mint Viewer: Grants read-only access to workflows, journeys, PII and analytics. Users cannot edit workflows or journeys.
Mint Workflow Builder Editor: Grants access to create, update and publish workflows in the Mint Builder. Users cannot view journey data, PII in Mint Journeys or analytics directly.
Mint Journey Editor: Grants access to view and update journey data (including PII) and view analytics. Users cannot edit workflows in the Mint Builder.
Mint Analytics Viewer: Grants read-only access to Mint Analytics without access to journey data or PII.

Access to Signicat products

Certain Mint steps rely on features from other Signicat products (such as eID and Wallet Hub, Data Verification, Electronic Signing and Digital Evidence Management) inside your workflows.

Because Mint runs these steps on behalf of your Signicat account, you should treat Mint roles as an access layer on top of product access.

Verify access to Signicat products before assigning Mint roles

Before assigning a Mint role, verify that the user in the Signicat Dashboard has access to the Signicat products used in your workflows and that the Signicat products used in your workflows are enabled on the account. Also review the resulting journey data and PII, depending on the role you assign to the user.

You can learn more about the relation between Mint roles and access to Signicat products in the next sections below.

Workflow editing grants product usage through Mint

Mint users with a workflow-editing role can add and use all supported Signicat products enabled on the account through steps in their workflows, regardless of their individual native permissions for those products.

This applies to the following roles:

Mint Administrator
Mint Editor
Mint Workflow Builder Editor

Scope of product access

Access through Mint applies only within Mint workflows. A Mint role does not grant direct access to each product's own interface in the Signicat Dashboard or its APIs.

Journey data access includes data collected by products

Mint users with a journey-access role can review data collected by the Signicat products used in a workflow when that data is available in the journey. This also includes PII data.

This applies to the following roles:

Mint Administrator
Mint Editor
Mint Viewer
Mint Journey Editor

Scope of product access

Mint users with these roles can view step outputs, files and end-user PII in Mint Journeys, even without a native viewer role for the product that collected the data.

Examples

The examples below show how Mint roles interact with product access on your account:

Example 1: Product usage without a native product role

Suppose Digital Evidence Management (DEM) and Data Verification are enabled on your account.

You assign Mint Workflow Builder Editor to a user who has no native DEM or Data Verification roles.

That user cannot open the DEM settings or call the DEM API directly, but they can build and publish a Mint workflow that retrieves DEM records or runs Data Verification lookups.

Example 2: Visibility into product data through a journey

Suppose a workflow verifies an end-user with eID and Wallet Hub and Biometric Verification and saves the result in the journey.

A user with Mint Viewer or Mint Journey Editor can open the journey in Mint Journeys and view the identity data and PII from those steps, even without a native role for those products.