FairConsent – How It Works & What You Should Know

Audience

Consent collectors, organization admins, project managers, and compliance teams.

Purpose

This document is the starting point for understanding FairConsent.

It explains:

• How to approach FairConsent as a system
• What documents to read depending on your role
• Where to find details about critical actions and limitations

This document does not explain every feature.

Instead, it guides you to the right articles so you can understand FairConsent correctly and safely.

How to Use This Guide

If you are new to FairConsent:

• Start from the top
• Read the sections in order
• Follow the referenced articles based on what you need

If you are looking for a specific answer:

• Jump to the relevant section
• Open the linked article for details

1. Start Here – Understanding the FairConsent Experience

Before using FairConsent in real projects, it is important to understand how the app and platform behave in practice, not just what features exist.

FairConsent – User Experience Overview 

2. The Main Consent Collection Flow (Most Important)

All consent collection in FairConsent follows a project-based flow:

• Creating a project
• Recording one or more consents
• Uploading data
• Completing the project

Understanding this flow is essential for:

• Field teams
• Project managers
• Anyone responsible for closing projects

Consent Collection – Main App Flow 

3. Working Offline – What to Expect

FairConsent supports offline usage, but offline work has specific rules and limitations.

This is especially important for:

• Field deployments
• Low-connectivity environments
• Long-running collection projects

Offline Mode – Limitations & Risks

4. Uploading Data & Platform Visibility

Recording a consent on the device and having it available in the platform are not the same thing.

To understand:

• When data becomes visible in the portal
• What uploading actually does
• What remains only on the device

Uploading Consents & Platform Visibility 

5. Completing a Project – Read This Carefully

Completing a project is a critical action.

Before doing so, users must understand:

• What happens to local data
• What remains available in the platform
• Why this action is treated as final

Completing a Project – Warnings & Consequences 

6. Roles, Access & Organization Boundaries

FairConsent enforces strict boundaries between:

• Users
• Roles
• Organizations

Not all users see the same data or have the same permissions.

• User Roles Explained
• Organization Separation & Data Boundaries

7. Special Scenarios (When Relevant)

Some documentation is only relevant depending on how you use FairConsent.

Consent Links (Beta) 

? DAM Integrations : Create a hub document for this

? Subscription & Billing : Create a document for this.

8. What FairConsent Does Not Do

To avoid incorrect assumptions, it is important to understand intentional limitations of the system.

What FairConsent Does NOT Do 

9. Need Help or Troubleshooting?

If you encounter an issue:

• Refer to the relevant document above
• Then consult the FAQ or contact support

Providing the name of the related document will help resolve issues faster.

Final Note

FairConsent is designed around explicit actions and clear responsibility:

• Recording consent
• Uploading data
• Completing projects

This guide exists to ensure all users start with the same understanding before using FairConsent in real-world scenarios.