FairConsent – How It Works & What You Should Know
FairConsent Knowledge Base
This article is created for:
Consent collectors, Organization admins, Project managers, Compliance teams, Operational users responsible for consent workflows
Purpose
This article is the recommended starting point for understanding FairConsent. It explains:
- How to approach FairConsent as a complete system
- Which articles to read based on your role
- Where to find guidance for important actions, limitations, and responsibilities
This article does not explain every feature in detail. Instead, it helps direct you to the right articles so you can use FairConsent correctly, efficiently, and safely.
How to Use This Article
If you are new to FairConsent we recommend that you:
- Start from the top
- Read the sections in order
- Open the referenced articles based on your responsibilities
This gives you the clearest understanding of how the system works in practice.
If you need a specific answer
- Jump directly to the relevant section
- Open the linked article for detailed instructions
1. Start Here – Understanding the FairConsent Experience
Before using FairConsent in real projects, it is important to understand how the app and the 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 consents
- Completing the project
Understanding this flow is essential for:
- Field teams (collectors)
- 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.
It's important 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 collected consents
- What remains available in the platform
- Why this action is treated as final
> Completing a Project – Read this carefully
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.
> Organization Separation & Data Boundaries
7. Special Scenarios (When Relevant)
Some articles are only relevant depending on how you use FairConsent.
If these features apply to your organization, refer to the dedicated articles.
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 article above
- Then consult the FAQ or contact support: customersupport@fairpicture.org
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.