# Suggestion for improving Integrated Authentication development

**URL:** <https://meta.discourse.org/t/suggestion-for-improving-integrated-authentication-development/122869>\
**Category:** Feature\
**Created:** [July 13, 2019, 4:01pm UTC](https://meta.discourse.org/t/suggestion-for-improving-integrated-authentication-development/122869 "2019-07-13T16:01:39Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![hawm](https://avatars.discourse-cdn.com/v4/letter/h/f07891/32.png) [@hawm](https://meta.discourse.org/u/hawm)\
**Post date:** [July 14, 2019, 2:10am UTC](https://meta.discourse.org/t/suggestion-for-improving-integrated-authentication-development/122869/3 "2019-07-14T02:10:31Z")

</div>

> [@Falco](#):
>
> It will always need some custom work to integrate with the specific platform

Yes, but Discourse seems to send export notification via `Email::Sender` directly by hardcode rather than invoking notification event hook, like `DiscourseEvent`

- [Repository search results · GitHub](https://github.com/discourse/discourse/search?l=Ruby&q=Email%3A%3ASender.new.send)

So how to “redirect” notification to our custom notification system, any public example?

---

_[View the full topic](https://meta.discourse.org/t/suggestion-for-improving-integrated-authentication-development/122869)._