The Public Sector Digital Services (PSDS) app has many fields that reference the csm_consumer and csm_consumer_user tables. It seems like ServiceNow didn't consider the idea that the constituents that need to consume PSDS services are also fulfillers in the PSDS/CSM app, ITSM, etc. The target customers of the PSDS product seem to be state and local governments. In those situations, the vast majority of the "fulfillers" are also "constituents".
What's the right path forward to allow a CSM, IT, etc. fulfiller to be a "consumer" on the PSDS side?
I posed this question in SNDevs Slack. The suggestion I received was to create a separate consumer user/constituent record for each fulfiller. That doesn't seem like a feasible solution to me and I'm looking for guidance on what others have done or what ServiceNow would consider to be the best practice to resolve this issue. Beyond the redundant user records many (most?) government organizations have SSO requirements, so a redundant consumer user/constituent record is not feasible.
