List Names - front end versus back end names

[user1152]

There should be an option to name your Lists in the backend so that subscribers cannot see your internal data. But then we should also be able to name them differently so that subscribers are able to properly choose what lists they want to be on. We use certain verbiage for lists with our team, but we use a totally different naming of lists for our subscribers to make it easy for them to choose what topics they want to hear from us on.

[William_A]

Hello @user1152 ,

Are you able to provide any further context or specific use cases on what it is you're looking for? Any general examples of what you're trying to avoid in regards to what contacts see for list selections, versus what your organization is expecting to see in the account?

[William_A]

Thank you for taking the time to leave us your feedback. We haven't heard back from you so we are going to close this idea. We will leave it open for comments in case you are able to provide us with the requested information.