It has only been a few months since our last platform update, but MICOO has already entered a new phase.
The latest developments are not simply a list of additional features. Together, they close many of the operational gaps that organizations encounter when they want to recognize skills in a reliable, scalable and usable way.
A credential is the visible outcome. Behind it, however, there is a complete process: people must be onboarded, learning and achievements must be connected, evidence may need to be assessed, responsibilities must be clear, issuance may require formal approval, and the final result must remain verifiable and useful over time.
This is the direction in which MICOO is evolving: from a digital credential platform into a complete infrastructure for skills recognition.
A More Complete Recognition Lifecycle
Organizations rarely work with only one type of achievement.
A company may need to issue a simple badge after mandatory training. A university may require evidence, assessment and formal sign-off. A public project may need to document learning outcomes, store a complete evidence dossier and export credentials in formats that can be used across European systems.
MICOO is designed to support these different levels within one environment—from lightweight recognition to structured, evidence-based credentials.
The most recent developments strengthen every part of that lifecycle.
Credentials That Fit Different Contexts
Organizations can now create fully customized PDF certificate templates using their own layouts, branding, images, dynamic data and verification QR codes.
At the same time, the same achievement can be exported in interoperable formats such as Open Badges 3.0 and Europass. When enabled, Europass credentials can also be digitally sealed, adding a stronger layer of institutional verification.
This means organizations no longer have to choose between a certificate that looks right and a credential that works across systems. MICOO supports both the human-facing document and the structured digital credential behind it.
Additional information—such as an endorsing body, a legal organization identifier and organization-specific user fields—can also become part of the credential record and its outputs.
Clear Governance Before Issuance
In many organizations, issuing a credential is not a single-click action.
It may require approval from an academic director, a legal representative, a project coordinator or another authorized person. MICOO now includes a dedicated Signatory role and a structured issuing workflow for these scenarios.
Credentials can enter an intermediate Issuing status while signatures are collected. Authorized signatories can sign certificate files, while mandates allow them to delegate the operational task to designated managers without sharing personal accounts or losing clarity over responsibility.
Bulk actions also make this process practical when many credentials must be completed at the same time.
This turns issuance into a controlled organizational process—not an informal step outside the platform.
Learning Systems Connected to Recognition
Learning often happens in an LMS, while credentials are managed somewhere else. This separation creates duplicate work and makes the learner experience less coherent.
The new MICOO integration for Moodle connects course activity with credential workflows. Organizations can synchronize MICOO credential templates, add MICOO activities to Moodle courses and connect learning completion with the appropriate recognition process.
For the learner, this creates a clearer journey from learning to achievement. For the organization, it reduces manual coordination and makes recognition part of the existing educational environment.
An Integration Layer for the Wider Ecosystem
Moodle is one important use case, but the integration strategy goes further.
MICOO now provides a public integration API and organization-level API keys. External platforms can use stable public identifiers, retrieve relevant credential and flow information, and connect MICOO with portals, HR systems, project platforms and automation workflows.
API keys can be created, managed and revoked directly by the organization, making integrations easier to operate over time.
A mature credential platform should not require organizations to replace the systems they already use. It should connect with them.
Onboarding and Data Management at Scale
Large cohorts create a different set of challenges.
The new CSV import flow allows managers to validate data before import, preview and edit records, invite users or create accounts, and update existing profiles instead of creating duplicates.
Organizations can also configure which standard personal fields they require and define up to five additional fields for their own operational needs—for example a student number, department, course, location or project code.
These values can remain specific to each organization, even when the same person belongs to multiple organizations in MICOO. They can also be used in imports, profiles and certificate templates.
This provides flexibility without forcing every organization into the same data model.
Beyond the Final Certificate
For many use cases, the final credential is not enough on its own.
Quality assurance teams, funded projects, auditors and awarding organizations may also need access to the process behind the credential: activities, assessment information, evidence and verification references.
MICOO can now export a completed flow as a structured ZIP package, creating a readable record that can be archived, reviewed or transferred outside the platform.
This is an important distinction. A certificate communicates the achievement. A complete evidence dossier documents how that achievement was recognized.
A Smoother Platform for Daily Work
Alongside the major releases, we have continued improving the daily experience across the Design, Wallet and Assess applications.
Navigation is more consistent and role-aware. Table preferences can be remembered for each user. Organization dashboards provide clearer information. High-volume organizations can access larger credential histories, and invitation, evidence and confirmation flows have been refined throughout the platform.
These improvements may be less visible than a new standard or integration, but they are essential to making MICOO reliable in real operational environments.
From Digital Credentials to Skills Recognition
The purpose of MICOO is not limited to issuing microcredentials.
It is to help organizations recognize learning, skills and achievements with the level of structure appropriate to each context—then make that recognition portable, verifiable and useful.
The new platform capabilities bring together:
- learning and external systems
- user and organization data
- evidence and assessment
- formal governance and signatures
- interoperable credential formats
- verification and long-term records
This is what makes skills recognition operational at scale.
And this is the next stage of MICOO.
