When we’re adding Cards in Bases, each Card can of course have a trigger to target a keyword, and more importantly apply page restrictions so that the keyword only triggers the card on specified pages. This is great, but it would be super helpful if we could edit the page restrictions for card triggers in mass instead of one by one.
The use case here is that we’ve built a baseline enablement package for clients with cards for definitions, embedded processes, etc, but every time we deploy it we need to go in and make sure that it’s restricted to the specific HubSpot portal they’re in, and no other applications. This means when the card is installed in their portal we’ll have to go through a QA process of checking each individual card and ensuring the right links are put on the page restrictions section, which becomes time consuming when there’s 100+ cards.

Please authenticate to join the conversation.
In Review
💡 Feature Request
Over 1 year ago
Ravi Persaud
Get notified by email when there are changes.
In Review
💡 Feature Request
Over 1 year ago
Ravi Persaud
Get notified by email when there are changes.