How can I exclude who receives a Knowledge Alert?

You could make a group just for them that would have Read Only perms on that collection. I think they can still comment on the cards tho. If they want to have Author perms but not receive KA's I'm not sure what to do there.

You have to choose the Group when sending a KA so that should work to make the CEO in their own group. They could still retain Author perms then 

I know that having more custom roles was something talked about on the roadmap call tho! @chrisanderson fyi for that perhaps?

Great question @laquize, and thanks for your helpful tips @siobhan! A couple of clarifications just in case anything is fuzzy:
• To send a knowledge alert (KA) you have to be the author of the Card, but any user (regardless of role) can receive a KA as long as
a.) they're in the Group you send the KA to, and
b.) the Group has access to the Collection where the Card lives (you won't even see Groups that do not have Collection access in the option list though)

• When you send a KA to a Group, all members of that Group will receive it. I agree with the above tip to create some sort of "non-KA" Group that you can move your CEO into (and out of the Group that will receive KAs).

Hope this helps! Also, for anyone curious, here's a Help Center article all about KAs which links to a previous Deep Dive we hosted on KAs 

I found it super helpful to go through and make leveled out groups based on company level in Guru, we also have leveled out collections based on company level as well so if we need to send KA's to managers only we can.

Just to chime in, I’d like to use Knowledge Alerts to alert specific users, rather than groups - feels like we need an Exclude/Include This User option maybe! :D

e.g usually I’d spam the whole of a team, but maybe in this case I want 2 SMEs to review it first and alert them, before alerting the entire team about it.

@Charshy Nash Thanks for your feedback! Luckily, this idea is reflected in our Product Feedback category here! 

You can navigate into this Community post, upvote the idea, discuss workaround solutions, and subscribe to future updates. Our product management team is actively engaged in our Community and they'll share any changes as we make progress on this request.