User Roles Explained

Audience

Organization administrators, consent managers, consent collectors, and compliance teams.

Applies to

FairConsent Mobile App and Web Platform.

1. Purpose of This Document

This document explains the three user roles available in FairConsent and what each role can and cannot do.

It exists to clarify:

• Platform access vs mobile app access
• Operational responsibilities
• Seat usage and subscription implications

Roles in FairConsent are explicit by design and do not overlap.

2. Core Principles

User access in FairConsent follows these rules:

• Roles define capabilities, not exceptions
• Platform access does not automatically grant app access
• Using the mobile app requires an assigned seat
• Roles do not override data lifecycle rules (uploading, completion, deletion)

3. The Three Roles in FairConsent

1. Consent Collector

Primary context: Mobile App

Platform access: ❌ None (reference only)

Consent Collectors:

• Record consents using the mobile app
• Upload recorded consents
• Complete projects

On the platform:

• They cannot manage or view consent data
• They appear only in the Users dashboard for reference and reporting
• They cannot manage users, consent terms, or subscriptions

Seat requirement

• A Consent Collector must have a seat assigned to use the mobile app

2. Consent Manager

Primary context: Web Platform

Platform access: ✅ Operational access

Consent Managers can:

• Manage consent terms
• Manage users
• View and manage collected consents
• Review projects and uploaded data

They cannot:

• Manage subscriptions
• Manage billing or plan details

Using the mobile app

• A Consent Manager may assign themselves a seat
• Without a seat, they can fully use the platform but cannot use the app

3. Organization Admin

Primary context: Web Platform

Platform access: ✅ Full access

Organization Admins can:

• Do everything a Consent Manager can
• Manage subscriptions
• Manage billing and plan settings
• Assign, freeze, and reassign seats

Using the mobile app

• Admins may assign themselves a seat if they want to use the app
• Platform access alone does not consume a seat

4. Seats & Mobile App Access

• Seats are required only for mobile app usage
• Platform access never consumes a seat
• Seats can be assigned to:
  • Consent Collectors
  • Consent Managers
  • Organization Admins

5. Freezing and Reassigning Seats (Admin Only)

Organization Admins can:

• Freeze a user’s seat from User Management
• Reassign that seat to another user or collector

When a seat is frozen:

• The user loses access to the mobile app
• The user account remains active
• Historical data and attribution are preserved

This allows flexible management of field teams without deleting users.

6. What Roles Do Not Change

Regardless of role:

• No user can see unuploaded consents
• No role can recover deleted local data
• No role bypasses project completion rules
• Roles do not override organization boundaries

7. Related Documents

• Consent Collection – Main App Flow
• Uploading Consents & Platform Visibility
• Offline Mode – Limitations & Risks
• Completing a Project – Read This Carefully
• Organization Separation & Data Boundaries

Final Note

Roles in FairConsent are designed to:

• Separate responsibilities clearly
• Control app usage intentionally
• Support compliance and accountability

Understanding roles is essential before assigning users or seats.