Hello, you can hide it using the "Hide bell after subscribing" option in Perfecty Push > Settings > Public widget. You cannot send push messages if the user has not subscribed (this is part of how Push Notifications work and doesn't depend on our plugin) so it's mandatory to show them the bell so that they can subscribe. Once they subscribe, the bell will disappear.

Thank you. I'm sorry, but I'm not sure what I wrote.
Right now I have to click on the bell to get the dialog to allow notifications, but I'd like that to show up directly.
I know I can hide the bell icon, but that doesn't bring up the dialog.
I'd love to be able to change the hierarchy of where the dialog appears in the settings.
I think I can add that to window.PerfectyPushOptions.

Thanks!

Right now we don't support asking notifications directly, you can follow this previous conversation:

The reasons to not do it are very well explained here: https://developers.google.com/web/fundamentals/push-notifications/permission-ux

It’s considered a bad practice to ask for browser permissions directly. For the moment, the plugin doesn’t support other patterns but we have plans to do it, and if there are good reasons to support direct permissions, we could consider them. Could you please elaborate your use case?

I don't have a specific use case, but in Japan, where I am from, there are many sites that display it directly, and I recognize that it is probably a national trait.
Therefore, my client instructed me to create something similar to that.
I'm sorry I can't provide a specific use case.
I just don't think I can do away with the direct display on all pages.
I also recognize that direct display is a bad thing, so I've decided to make a special exception and use the forked version for this case.
Thank you for your patience on this matter. But the plugin itself is very nice!
I'd be happy to help with the translation next time I have time!
I'm closing this case now, thank you for your support!

Hi @shossk thanks for letting us know. As I said, we've received this request in the past so we might support it. I'll keep it as open so that we can address this in the upcoming versions.

This has been released in v1.2.0