Community resources
Community resources
Community resources
Understanding eIDAS & How It Relates to QC Approvals for Confluence Cloud
In today’s digital workplace, document approvals and electronic signatures are essential, not just for efficiency, but also for compliance and legal certainty in regulated environments. If you work with quality systems, audits, or cross-jurisdiction content reviews, you might be familiar with eIDAS, the EU regulation that sets standards for electronic identification and trust services.
In this article, we want to help you better understand how electronic signature standards like eIDAS relate to approval workflows in Confluence Cloud and what this means when you’re using our QC Approvals app.
What Is eIDAS?
eIDAS (Electronic IDentification, Authentication and trust Services) is a European regulation (EU Regulation No 910/2014) that defines standards for electronic signatures across EU member states. It lays out three levels of signatures:
-
Simple Electronic Signatures: basic digital consent or acknowledgment.
-
Advanced Electronic Signatures (AES): uniquely linked to the signer and the signed data.
-
Qualified Electronic Signatures (QES): the highest assurance level, created using a qualified certificate and trusted across all EU states with the equivalent legal effect of a handwritten signature.
When documents or records are signed in accordance with eIDAS, they benefit from cross-border legal recognition in the EU, helping organizations confidently handle digital approvals within internal processes.
Electronic Signatures Requirements
Under eIDAS, electronic signatures must meet several requirements:
-
Uniquely linked to the signatory (so the person can be identified).
-
Created under the sole control of the signatory (preventing misuse).
-
Linked to the signed data, so any post-signature change is detectable.
Tools that manage electronic signatures, whether part of a Confluence app or used as standalone services, often build on these criteria to offer greater transparency and traceability than informal workflows like email chains or comment threads.
How QC Approvals handles eIDAS
QC Approvals for Confluence Cloud brings secure approval workflows and version control directly into your Confluence environment. The app lets you:
-
Assign roles and signing responsibilities within reusable templates.
-
Trigger formal approvals based on major page versions.
-
Track who signed what and when with secure authentication choices such as two-factor authentication (2FA) and other identity verification options.
These capabilities help organizations standardize approvals and capture structured consent on Confluence content, an essential step in many compliance frameworks.
However, it’s important to clarify that QC Approvals does not provide eIDAS Qualified Electronic Signatures (QES).
Practical Takeaways for Confluence Teams
When configuring approval workflows:
-
Use QC Approvals to structure and automate internal review processes within Confluence.
-
Secure user authentication with 2FA or single sign-on to help strengthen signer identity.
What’s Next?
Whether your goal is internal quality governance, audit-ready documentation, or regulated sign-offs, adopting structured approval workflows in Confluence is a vital step forward. QC Approvals gives you the tools to manage that process reliably with transparency and traceability, even as you evaluate options for meeting specific regulatory signature standards like eIDAS.
👉 Try QC Approvals for Confluence Cloud on the Atlassian Marketplace and discover how it can help streamline your approvals and strengthen your documentation workflows.