Remove New Event Attendee button from related list Event Attendees and New Call button on related list Calls.

I only want users to be able to add Event Attendees on the Event itself and not via the related list Event Attendees on the Child Account. 

I only want users to be able to create calls via the 'Record a Call' button on top of the page and not via the related list Calls.  


  • Avatar
    Ian Wright Official comment

    Hi Leen,

    Thank you for posting in the Veeva CRM Product Suggestions Community.

    We have a feature that that can be used to disable creating new records for related lists associated with an Account. Using this feature, you could prevent the creation of Event Attendees from the Event Attendee related list on an Account page (https://crmhelp.veeva.com/doc/Content/CRM_topics/Accounts/Configuration/Disabling_the_+_Sign.htm ). The feature supports disabling the create button for all but the following related lists associated with the Account object: Call, Inventory, and Orders.

    This feature was designed primarily for preventing the creation of new records on the Account page. I understand you want to block the creation of records from the Child Account page though.

    Can you please provide me with some additional information and context behind your need for blocking the creation of Event Attendees and Calls from the Child Account page? Is there a particular reason you want to prevent this from happening on the Child Account page?

    Thanks in advance,


  • Avatar
    Leen Bruggeman

    Hi Ian, 

    thanks already for the provided information. It's unfortunate to hear that the feature doesn't work for Child Accounts. 

    Event management has been set up that users should only be able to add attendees via the event itself. This should not happen via the Child Account. 

    For Calls, the 'New Call' button doesn't work on the related list and they should only use the 'Record a Call' button to record a call. Having 2 buttons to log a call would only be confusing. 

    We just want to make it as user friendly as possible. Hope this explains why we want to prevent this. 

    Best regards, 

    Leen Bruggeman


Please sign in to leave a comment.