Roadmap

Instead of directly sending an email, we are planning on adding the ability to save the branded email as a Gmail draft. This enables the user to make final touches within Gmail, schedule the email, and more.

Manage recipients by picking from a list of recent or frequently used emails, add Confluence users or groups, etc.

Currently emails can only be sent from a connected Google account. We plan on adding more integrations as required by our users.

Currently emails can only be sent from a connected Google account. We plan on adding more integrations as required by our users.

Currently emails can only be sent from a connected Google account. We plan on adding more integrations as required by our users.

See the documentation to learn more about unsupported rich links. The goal of this feature is to allow PageMailer to connect to these other Atlassian apps in order to fetch link data.

Send emails on behalf of a Google group or using a different name and email as approved by your Confluence administrator.

Set and manage outgoing emails with scheduling.

Automate emails when a blog post is created, or automate sending onboarding (or other) pages as emails when a new user is added to Confluence, or when they get added to a specific group.

If Atlassian provides the necessary functionality, we plan to integrate support so your team’s custom emojis display correctly in email content. Learn more.

Manage who can send emails with PageMailer in your Atlassian site, and limit sending options.

Allow users to save templates as favorites for organizations with many templates and varied branding.

Reference your users’ or contact names, job titles, and more to automate sending emails with a template managed within PageMailer. Contact information for sales could be loaded from an external spreadsheet.

Analytics on your outgoing emails, top senders and destinations, etc.