Welcome to the Netflix Partner Help Center. Have a question or need help with an issue? Send us a ticket and we'll help you to a resolution.

Content Localization Portal: Comms


The communication (or Comms) function within the Content Localization Portal is a portal wide, persistent messaging system. The aim of this functionality is to bring conversations relating to projects into our tooling to increase the visibility to both Netflix and our Partners.

Broadcasting & Direct Messaging

With the introduction of Comms in the Content Localization Portal Netflix now has the ability to easily communicate project pertinent information to all partners working on it. This unidirectional communication is referred to as “Broadcasting”.


Fig.1 - Broadcasting

As seen in the example above Netflix has sent the same message, simultaneously, to all partners from A to Z. This will help ensure all partners stay aligned with Netflix with regards to things such as a launch date being pushed, reminders around bid submissions, the QC status of the Final IMF etc.

In addition the Comms function will help facilitate direct communication between Netflix and our partners.


Fig.2 - Direct Messaging

In the example above we can see that Netflix has sent unique messages to Partners A, B and C only, with Partner Z not receiving any message. Direct messages are language specific in nature and as such they are tailored and directed towards only the partner working on the language(s) in question.

Inter-partner communication (i.e. Partner A talking to Partner B) is not supported at this time.

Using the Comms Function

It is strongly recommended that users ensure they are “Following” the projects they are working on in order to take full advantage of the Comms functionality.

When you log into the Content Localization Portal you are first presented with a projects list. This page lists projects being worked on by a partner.


Fig.3 - Project List View: Unread Message Count

If there are any unread messages for a project you are following a blue icon with a number will appear on the project row [Fig.3 (1)]. To read the messages simply click on the icon to reveal a project messages window towards the right hand side of the screen.


Fig.4 - Project List View: Message Window

From here you can see the messages relating to the project [Fig.4 (1)] and the project name is confirmed towards the top of the list. Towards the bottom of the list is a place for users to add additional messages [Fig.4 (2)]. To close the project messages window simply click on the “X” towards the top right hand corner.

If there are no unread messages then no icon will appear in this Project List view. In order to read previously read messages a user must first click on a project.


Fig.5 - Project Page: Unread Message Indicator

Towards the bottom right hand corner of the screen a speech bubble icon will be present [Fig.5 (1)]. This will be present at all times and visible to “followers” and “non-followers” alike. If there are unread messages, a blue icon will also appear with a count.

Clicking on this icon will reveal the same project messages window seen previously in [Fig.4], and the behavior is the same.

The count communicated to users (via the blue icon with a number) is reset each time a user opens the project messages window.


It is possible to tag people in a message.


Fig.6 - Tagging

To do this use the “@” symbol and start typing the name of the person that should be tagged. As the user types, the system will start to show viable users in the list. A user can either continue to type the name or click on the name presented and then proceed to enter their message.


Fig.7 - Message With Tagging

The image above shows an example of a message where a user has been tagged. It is possible to tag both “followers” and “non-followers” in a message.

If a user tries to tag someone but the desired name does not appear in the UI as an option, as seen in [Fig.6], this means the intended recipient does not have the correct privileges set in their Starship account. To resolve this simply add the person in question as a “Follower” to the project. This will grant them the required privileges and it will then be possible to tag them in messages.

System Generated Messages

In addition to user generated messages, the new Comms functionality also accommodates system generated messages such as when a new proxy becomes available.

Email Notification Logic For Messages Sent Via Comms

In addition to receiving prompts within the Content Loc Portal UI email notifications are also generated for each message. The section below outlines the logic used for these email notifications.

New broadcast:

  • All external followers on the series project, across all vendor channels, will receive a notification.

New message:

  • If from an external user: All internal followers will receive a notification.
  • If from a Netflix user (vendor channel): All external followers, within the specific vendor channel the message was sent, will receive a notification.
  • If from a Netflix user (internal channel): All Netflix followers will receive a notification.

Mentioned (tagged user):

  • Only the mentioned user will receive a notification.

Change Log:


  • Added the email notification logic relating to new messages in Comms to assist users with identifying when email notifications are sent and who receives them.
Was this article helpful?
2 out of 2 found this helpful
Powered by Zendesk