nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Ability to List Responsive Teams as Project Primary Contacts

Autumn

Currently our clients can build teams of multiple users in their organizational settings. These team of users can be assigned as authors, reviewers and owners. My client Ticketmaster would like to be able to assign a team of users as a Project Primary Contact. Here is a video clip of their request.

https://zoom.us/clips/share/V6j41m4mQSGVhpCZic3wbg

Find more posts tagged with

Future consideration

Response Projects

Status: Future consideration

Comments

Khalees V

@Autumn Thank you for sharing the feedback. Keep you informed when we consider it in future.

Kimberly Bara

Subject: Feature Enhancement Request – Support Team as Project Primary Contact (PPC) in Intake

Client: Ticketmaster / LiveNation
Feature Area: Intake – Project Primary Contact (PPC)

Overview of Request:
LiveNation requires the ability to designate a Team within Responsive as the Project Primary Contact (PPC) during the Intake process. Instead of assigning an individual user, they want to select a predefined team so that ownership and visibility are shared across a group.

Business Need:

LiveNation manages intake across multiple stakeholders and does not operate with a single-threaded owner model.
Current intake requires naming individual users, which creates operational overhead and risk if individuals are unavailable.
Assigning a team would ensure continuity, shared accountability, and immediate visibility for all relevant stakeholders.
Notifications for new intake submissions should be sent to all members of the assigned team.

Current State:

Responsive supports teams for collaboration within RFx projects (e.g., assigning authors, reviewers)and content library (assigning content owners).
However, teams cannot be assigned as the Project Primary Contact (PPC) in the intake process (inconsistent behavior observed across instances).
Intake currently requires selection of individual users only.

Proposed Functionality:

Enable selection of a Team as the PPC in intake.
Ensure all team members receive notifications for intake submissions and related updates.
Maintain consistency with existing team-based assignment capabilities already present in project workflows.

Workaround Provided:

Proposed that LiveNation create a shared inbox backed by a distribution list and configure it as a user in Responsive.
Intake notifications would then route to this distribution list.

Customer Response to Workaround:

LiveNation declined this approach.
They do not want to manage or monitor a shared inbox and view this as an operational burden.
Their expectation is to leverage native team functionality within Responsive rather than external email-based solutions.

Gap Summary:

Team-based assignment exists within RFx project workflows but is not extended to intake (PPC designation).
This creates an inconsistency in how teams can be leveraged across the platform.

Impact / Urgency:

This is a blocking issue for LiveNation.
They are currently unwilling to adopt or proceed with Responsive for intake workflows (their primary use case) until this capability is supported.
The inability to assign a team as PPC directly impacts their ability to operationalize intake at scale.

Requested Action:

Evaluate feasibility of enabling teams as PPC in intake.
Clarify whether this is a known limitation, roadmap item, or feature flag-dependent behavior.
Provide guidance on timeline or interim solutions if available.

Thank you.

@Autumn @Khalees V @Brendan Soucie @Christopher Dunne @Cory Edwards @Tyler Richard @Brian Lund @Ariana Amplo @Erica Nelson

Kimberly Bara

@Tiffany Guriel sorry, missed you on my distribution! Please see above.