# HDP - cryptographic human authorization for CrewAI agents **URL:** \ **Category:** General\ **Tags:** agent, crewai\ **Created:** [March 27, 2026, 12:25pm UTC](https://community.crewai.com/t/hdp-cryptographic-human-authorization-for-crewai-agents/7434 "2026-03-27T12:25:11Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Siri](https://avatars.discourse-cdn.com/v4/letter/s/a183cd/32.png) [@Siri](https://community.crewai.com/u/Siri)\ **Post date:** [March 27, 2026, 12:25pm UTC](https://community.crewai.com/t/hdp-cryptographic-human-authorization-for-crewai-agents/7434/1 "2026-03-27T12:25:11Z")
current HITL implementations solve the pause/resume problem but not the trust problem. but there’s no way for the agent to verify the approval actually came from an authorized human vs an injected signal. HDP (human delegation provenance) fixes this at the protocol layer. native CrewAI support is implemented and awaiting review: 👉 [feat(examples): HDP delegation provenance integration by asiridalugoda · Pull Request #5135 · crewAIInc/crewAI · GitHub](http://github.com/crewAIInc/crewAI/pull/5135) happy to answer questions. ---
**Author:** ![credian](https://avatars.discourse-cdn.com/v4/letter/c/d2c977/32.png) [@credian](https://community.crewai.com/u/credian)\ **Post date:** [July 31, 2026, 7:21am UTC](https://community.crewai.com/t/hdp-cryptographic-human-authorization-for-crewai-agents/7434/2 "2026-07-31T07:21:53Z")
This is a useful distinction. How are you thinking about the boundary between proving who approved an action and proving what they approved? For a payment, the amount, merchant, time window, and agent identity all seem like they need to be bound into the authorization, otherwise a valid approval could be reused in a different context. We are exploring this problem at Credian, so I am especially curious whether HDP records enough context for an auditor to reconstruct the decision later. More context on what we are researching is at [https://credian.io](https://credian.io)