The combination of the user and the assigned portfolio must be unique when adding a user to which registry?

The Stakeholder Registry is a feature within ServiceNow Strategic Portfolio Management (SPM) used to identify and manage stakeholders for portfolios, programs, and demands. When adding a user to a specific portfolio as a stakeholder, the system enforces a uniqueness constraint. This means a single user can only be associated with a particular portfolio once within the registry. This prevents redundant entries and ensures clear, accurate tracking of stakeholder roles and responsibilities for each strategic entity.

A. Application Registry: This registry is part of Application Portfolio Management (APM) and tracks business applications, not the relationship between users and portfolios.
B. Event Registry: This is a core platform feature for defining and processing system events; it is not related to SPM portfolio or stakeholder management.
C. UX Page Registry: This is part of the Now Experience UI Framework and is used to register and define properties for user interface pages, not for managing user data.

1. ServiceNow Product Documentation: "Stakeholder Register". This document outlines the purpose of the stakeholder register, which is to "associate them [stakeholders] with a portfolio, program, or demand." The inherent function of this registry requires a unique association between a user and the entity (e.g., portfolio) they are a stakeholder for. See: Strategic Portfolio Management > Portfolio Planning > Stakeholder Register.

2. ServiceNow Product Documentation: "Add a stakeholder to the stakeholder register". The procedure for adding a stakeholder involves selecting a 'User' and a 'Portfolio' (or other parent entity). The underlying table, spmstakeholderregister, is designed with a unique index on the combination of the user and the parent record to maintain data integrity. See: Strategic Portfolio Management > Portfolio Planning > Stakeholder Register > Add a stakeholder to the stakeholder register.