Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
  • Home
  • User Guides
  • Approvals & Disclosures
  • General FAQ

Why is the recipient on my request blocked?

Written by Michelle Henley

Updated at October 21st, 2022

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Home
  • User Guides
    Approvals & Disclosures Third-Party Management Compliance Monitoring
  • Integrity Gateway Configuration Guide
    Approvals & Disclosures Request Types Configurable Components FAQ
  • Service Desk FAQ
  • Release Notes
    Release Notes - Approvals & Disclosures/ Third Party Management Release Notes - Compliance Monitoring
  • Roadmap
+ More
  • User Guides

    • Integrity Gateway Configuration Guide

      • Service Desk FAQ

        • Release Notes

          • Roadmap

            In some cases, an organization may choose to block an Employee, Third-Party or HCP/GO User from being used in the system. Once a Employee, Third-Party, or HCP/GO is blocked the selected individual can no longer be used in requests. 

            HCP's coming from Veeva or Reltio are blocked or inactivated from Veeva or Reltio. 

            If the recipient on your request needs to be unblocked, please contact your organization's Master Data Administrator. 

            Was this article helpful?

            Yes
            No
            Give feedback about this article
            Print to PDF

            Related Articles

            • How to Submit a New Request for Consultant Engagements (HCP, GO, Patient)
            • Request Status, Activity Status, & Recipient Status

            Knowledge Base Software powered by Helpjuice

            Expand