Grant Vault

Publish project results securely — with licensing and access control

Public dissemination of deliverables, datasets and code with TRL-based search, licence controls (integrated with Grant Legal), access requests, and maximum security by design.

Get early access See how it works

The challenge

Horizon Europe projects must disseminate results, but public websites and shared drives are brittle: no licence governance, no TRL context, weak provenance and uneven security. Mixing internal storage with public access also creates risks. Teams need a dedicated, secure “publication layer” with clear licences, access requests and audit trails.

Who it is for

Key capabilities

Public publication layer

Public publication layer (air-gapped from internal storage)

Publish results—documents, datasets, code, media—intentionally uploaded to Vault. No direct links to Grant Hub to minimise risk and enforce curation.

Licence controls

Licence governance with Grant Legal

Select a licence (open, restricted, custom) or attach a legal package from Grant Legal. Mandatory confirmation that content is rights-cleared before publishing.

Access requests

Access requests & approvals

Gate sensitive assets: collect requests, route to owners for approval, issue expiring links, and keep a full audit trail.

TRL search

Public search with TRL ranking

Search by keyword, topic, asset type and TRL; see KER associations and adoption signals to prioritise what matters.

Metadata & provenance

Rich metadata & provenance

Attach KER links, WP/Task, authors, grant ID, version, methods and source files. All downloads are logged for reporting.

Security

Security by design

EU-hosted, role-based access, strict isolation, malware/PII scanning at upload, signed URLs and immutable checksums.

Lifecycle controls

Embargoes, takedowns & updates

Schedule releases, set embargoes, replace versions with change notes, and manage takedown requests with traceability.

Grant 360 integrations

Integrations across Grant 360

Link Vault items to KERs in Grant Impact, adoption scoring in Grant Insight, and legal licences in Grant Legal.

How it works

For publishers (project team)

  1. 01

    Prepare the asset

    Choose type (document, dataset, code, media) and add metadata (WP/Task, KER, TRL, grant ID, authors).

  2. 02

    Select licence & access

    Pick an approved licence (or a Grant Legal package). Confirm rights clearance; set public or request-only access.

  3. 03

    Upload & validate

    Upload to Vault (virus/PII checks). Optionally set embargo and version notes; assign an owner for approvals.

  4. 04

    Publish & track

    Publish with a stable URL. Track views/downloads and respond to access requests with audit trails.

For visitors (public)

  1. 01

    Discover

    Search by keyword, topic, TRL and type; filter by licence and project.

  2. 02

    Evaluate

    Review abstracts, metadata and provenance; see KER links and related assets.

  3. 03

    Reuse or request

    Reuse under licence terms, or submit an access request for restricted items.

Get a freebie

The Horizon Europe Open Science & Dissemination Checklist: everything you must comply with—open access, data management, dissemination obligations, visibility rules, and reporting expectations.

FAQ

Does Vault expose internal files from Grant Hub?
No. Vault requires intentional uploads and keeps a strict separation from internal storage to reduce risk and enforce curation.
How are licences enforced?
You choose an approved licence or attach a legal pack from Grant Legal. Publishers must confirm rights clearance; access policies are applied at the asset level.
Can we gate assets and approve requests?
Yes. Restricted items collect access requests, route them to owners, and issue expiring links upon approval. All actions are logged.
Do you support TRL and KER linkage?
Yes. Assets can be tagged with TRL and linked to KERs. Search and ranking can prioritise by TRL.
What about DOIs and citations?
DOIs can be supported later as an optional add-on. Meanwhile, stable URLs and citation blocks are provided.
How do you handle takedowns/embargoes?
Embargo dates and takedown workflows are built in, with traceable reasons and version history.

Comparison: Grant Vault vs alternatives

CriteriaGrant VaultProject websiteGeneric repositories (Zenodo etc.)Shared drives
Licence governance with legal integration ✓ Manual and inconsistent Generic; no project playbooks Not supported
Access requests & approvals ✓ Email forms; no audit Basic; not tailored to project roles Ad-hoc, insecure
TRL-based public search ✓ No TRL context Limited project context No search/metadata
Air-gapped from internal storage ✓ Often mixed with CMS Separate but external Shared link sprawl
Provenance & download logs ✓ Minimal Varies by platform None or hard to trace
Embargoes, takedowns & versioning ✓ Manual updates Partial; not workflowed File overwrite only
EU-hosted & security hardening ✓ Hosting varies Varies No guarantees