New Feature Announcement: Stored Templates by Subaccount

Irina Doliov
Sep. 6, 2017 by Irina Doliov

Our Latest Feature

Ever since we introduced subaccounts back in 2016 we’ve worked hard to enhance the capabilities that functionality provides. This latest enhancement — on the heels of webhooks by subaccount — allows users to limit which subaccounts have access to which templates. This has been one of the most requested enhancements by both our enterprise customers and extended developer community.

With the enhancement, when creating a stored template, a master account can create the template exclusively for its own use. This makes it unavailable to any subaccounts. Alternatively, a master account can create and share the stored template with all subaccounts. This allows subaccounts — using their subaccount API keys — to call that shared template in their messaging but not edit it. This is great for companies who want to create stored templates centrally but allow individual customers or brands — managed as subaccounts — the use of those templates. This aspect of the functionality is similar to how sending domains work and is great for service providers managing their customers or partners as subaccounts. It’s also great for companies where templates are created centrally for brand consistency but where they want to allow different divisions or different message streams to use those templates.

Additionally, the master account can copy the stored templates to one or more specific subaccounts. This makes a copy that those subaccounts can now edit for themselves. This is great for individual business units within a SparkPost account that want to create templates centrally to maintain brand integrity, legal footers, and other aspects of the template. However, they still want allow their subaccounts the ability to edit if they choose.

And lastly, individual subaccounts can create and edit their own store templates that are then only available to that subaccount. For companies where individual divisions and brands operate independently as subaccounts, this provides flexibility to create templates without fear that a different division may accidentally call the wrong templates or make unauthorized edits.

Key Takeaway

We’ve built in flexibility into how you create and manage your stored templates with subaccounts. This allows you to integrate in a way that makes sense to your business.

We expect to start shipping this enhancement this week and out to all customers by the end of the month. You can expect the API docs and related support articles on the website this week.

—Irina Doliov
Senior Lead Product Manager


Related Content

Consuming SparkPost Webhook Events with Loggly - Part 1 of 3

Continuing from my last blog post, How Developers Can Use Transactional Email for Customer Success, I thought it would be best to step through how to quickly setup a Loggly account to act as a SparkPost ...

read more

Subaccounts and How We’re Making SparkPost Even More Awesome

The head of SparkPost’s product team shares details about subaccounts and other features that help developers looking for a Mandrill alternative.

read more

Product Announcement: Webhooks by Subaccount and Multiple Bounce Domains

Webhooks come with a firehose of data that is hard for ESPs to deal with. In this blog, the Product team announce 2 latest features that solve this problem.

read more

Get started and start sending

Try SparkPost and see how easy it is to deliver your app’s email on time and to the inbox.

Try Now

Send this to a friend