Concept: Functional Profiles are created primarily to support background, automated system interactions with WSOWeb (such as interfaces, batch requests, or direct API data pipelines). They are designed for programmatic access and are never assigned to a single, discrete internal user.
Step-by-Step Profile Provisioning:
- Navigate to Legacy WebAdmin, open the Manage Profiles tab, and select Profiles.
- Click Add New Profile and establish the configuration attributes:
- Profile Type: Must always be specified explicitly as
Functional. - Profile Name: Construct uniquely using a combination of the destination function and target client name (e.g.,
APISampleCo). - Password Management: Generate a string containing a minimum of 12 characters completely devoid of special characters to ensure robust backend parsing.
- Email: Assign the routing placeholder
noreply@wsoweb.com.
- Profile Type: Must always be specified explicitly as
- Security Controls: Leave the core Security Profile dropdown blank (do not assign an entitlement profile package here) and ensure that the credential control option is flagged to Password Never Expires.
- Entitlements & Scope: For standard data retrieval pipelines, assign the designated
Web Custom - Reporting APIrole. For transactional integrations (Trade-In pipelines), provision the profile withWeb Primary - Trades: FullandWeb Primary - UDFs: Fullroles. Finally, declare and explicitly bind the necessary Assigned Portfolio Groups.
Quality Control Pipeline: To meet audit standards, any functional user configuration requires a strict **4-Eye Check review**. Forward the configuration request ticket to dl-wsocspodleads@spglobal.com. A senior Quality Control reviewer must walk through the entire technical verification chain to confirm settings, check off the WSO 4-Eye Check box in Freshdesk, and tag themselves as the official CSS Approver before releasing credentials.