Understanding the Requirement

The requirement is to separate content by use case, such as financial advisors and service agents, and to restrict the email templates that each group can access. This is a common use case in Distributed Marketing, where different teams need to send different types of emails to their respective audiences.

Exploring the Options

One option that was considered was using SFMC Business Units to separate content by use case. However, this approach has its own set of pros and cons. Another option that was discussed was using core permissions to change what DM users would have access to.

Using Topics to Organize Quick Sends

Topics can be used to organize Distributed Marketing Quick Sends, and this approach has its own set of pros and cons. By using Topics, admins can restrict access to email templates and ensure that users only see the templates that are relevant to their role.

The root cause of the issue is the lack of a built-in feature to restrict access to email templates by user or profile. However, by using Topics, admins can create a workaround that achieves the desired outcome.

Example Code

// Example code to restrict access to email templates using Topics
// Note: This is a hypothetical example and may not be actual code
var topicName = "Financial Advisors";
var templateId = "123456";
// Restrict access to template based on topic

Heads up: When using Topics to organize Quick Sends, make sure to test the setup thoroughly to ensure that users can only access the email templates that are relevant to their role.

Implementation Checklist

Checklist

• Create Topics for each user group (e.g. Financial Advisors, Service Agents)
• Assign email templates to the relevant Topics
• Restrict access to email templates based on Topic
• Test the setup to ensure that users can only access the email templates that are relevant to their role
• Monitor and adjust the setup as needed

Frequently Asked Questions

Can I use Business Units to separate content by use case?

Yes, you can use Business Units to separate content by use case, but this approach has its own set of pros and cons.

How do I restrict access to email templates using Topics?

You can restrict access to email templates by assigning them to the relevant Topics and then restricting access to those Topics.

Can I use core permissions to change what DM users would have access to?

Yes, you can use core permissions to change what DM users would have access to, but this approach may not be as straightforward as using Topics.

What are the pros and cons of using Topics to organize Quick Sends?

The pros of using Topics include the ability to restrict access to email templates and organize content by use case. The cons include the need to test the setup thoroughly and monitor and adjust it as needed.