PRS Community Management

The CPA groups users into Communities based on the similarity of their PRS requirements. Where possible, users grouped in a Community will share similar needs (organizational, operational, security, etc.). A User Community must have a demonstrable common purpose, supported by its own operational concept and procedures.

The Community-Subcommunity structure is a dynamic framework that evolves based on the organizational needs established by the CPA, the Communities, and the requests of PRS users. The structure of Sub-Communities within a Community is the responsibility of the Community's Proof of Concept (PoC). The CPA is unaware of any existing Sub-Community structure within each Community. All user interactions with the CPA will be conducted through the Community's PoC.

Initially, a Community Structure is created to establish a conceptual, technical, and operational organization of the Users.

Subsequently, the progressive operation and evolution of the service (registration of Communities, registration of Users, new functionalities, etc.) may reveal that the defined scenario is not completely adequate and, consequently, its review and modification may be necessary.

Therefore, this structure is expected to be subject to review:

1. As a result of a risk assessment.
2. As new PRS user categories are added.
3. As important functionalities of the PRS service change.
4. At the express request of a current or potential PRS user.

To request the creation, deletion, or modification of a Community, please use the "PRS Community Request Form" through the Private Area of this website.