Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Uploading Consents & Platform Visibility

Audience

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

Applies to

FairConsent Mobile App and Web Platform.

1. Purpose of  This Article

This article explains:

  • How consent data becomes visible in the FairConsent platform
  • Why uploading consents is required
  • What admins and managers can and cannot see

Understanding this flow is essential for correct usage and expectation setting.

2. The Core Rule (Most Important)

Only uploaded consents are visible in the FairConsent platform.

Anything that has not been uploaded:

  • Exists only on the app
  • Is not visible to admins or managers
  • Is not included in reporting or oversight

This rule applies at all times.

3. What “Uploading Consents” Means

Uploading consents is a manual, explicit action performed by the consent collector.

When consents are uploaded:

  • They are securely transferred to the platform
  • They become visible to authorized users
  • They are included in project counts and reporting
  • They are no longer available on the app

Uploading confirms that consent data is finalized and available for review.

4. What the Platform Shows

The FairConsent platform shows:

  • Uploaded projects and their status
  • The number of uploaded consents
  • Associated consent metadata
  • Visibility based on user role and organization

The platform reflects finalized, uploaded data only.

5. What the Platform Does NOT Show

The platform does not show:

  • Consents that exist only on the app
  • Offline or non-uploaded consents
  • Partially recorded projects
  • Data from other organizations

Admins and managers cannot access data that has not been uploaded.

6. Uploading vs. Completing a Project

Uploading consents and completing a project are two separate actions:

  • Uploading makes data visible in the platform
  • Completing a project ends local collection

Completing a project does not upload consents automatically.

Collectors should always upload required consents before completing a project from the platform.

7. Why Visibility Works This Way

This design ensures:

  • Clear accountability
  • Predictable oversight
  • No hidden or partial data states
  • Compliance with data-protection principles

Admins see only what has been explicitly uploaded and finalized.

8. Best Practices

To avoid confusion or data loss:

  • Upload consents as soon as possible
  • Do not rely on offline storage
  • Review upload status before completing projects
  • Train collectors on upload responsibilities

Uploading should be treated as a required step, not an optional one.

9. Related Articles

For full context, also review:

  • Consent Collection – Main App Flow
  • Offline Mode – Limitations & Risks
  • Completing a Project – Read This Carefully
  • What FairConsent Does NOT Do
  • User Roles Explained
  • Organization Separation & Data Boundaries

Final Note

Platform visibility in FairConsent is intentional and explicit.

If a consent is not uploaded, it is not visible by design.


Need More Help?

For any questions or support, reach out us at customersupport@fairpicture.org