Allow portal section: Client profile | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/proplix-secure-api-gateway-portal-profiles-tokens-section-client-profile Publisher: Pixie Technologies LLC Client Portal API profiles and one-time tokens Allow portal section: Client profile Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Core customer/account profile. Audience: CRM administrators, integration developers, external portal backend teams and security reviewers; Permission: Administrator; Module v1.0.0; Where to goAdmin Area → Utilities/Tools → API Gateway → Create Client Portal API Before you start - Verify the module is active and use the exact navigation shown above. - Use an account with the stated module and core CRM permissions. - Use known test records when changing statuses, visibility, saved filters or global navigation. What this guide helps you do Core customer/account profile. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow. Follow these steps - Go to Admin Area → Utilities/Tools → API Gateway → Create Client Portal API. - Find the record, endpoint, field or action used to allow portal section: client profile. - Complete the displayed values exactly as described in this guide. - Select the available save, submit, send, upload, create, update or confirm action. - Return to the related register, portal, activity log or API response and verify the expected result. Fields and options Allowed sectionClient profile PurposeCore customer/account profile. Rules and limits - The external session can retrieve the section only when the profile includes its key and the client identity owns the related records. Check it worked - The allow portal section: client profile workflow completes without a validation, permission, ownership or availability error. - The related record, portal view, activity entry, notification log or API response shows the expected state. - Client-visible, public and API data remains limited to the code-backed ownership and visibility rules. Security, privacy and operational checks - Use controlled test records and non-production credentials before wider rollout. - Grant least privilege and protect secure links, personal data, uploaded files, signatures, API tokens, allowed origins and server IPs. Related guides Review detected enabled modules (https://pixiecrm.com/help-centre/proplix-secure-api-gateway-portal-profiles-tokens-enabled)Allow portal section: Contacts (https://pixiecrm.com/help-centre/proplix-secure-api-gateway-portal-profiles-tokens-section-contacts)Client Portal API profiles and one-time tokens (https://pixiecrm.com/help-centre/topic/proplix-secure-api-gateway-portal-profiles-tokens)Browse all Proplix Secure API Gateway guides (https://pixiecrm.com/help-centre/category/proplix-secure-api-gateway)Enterprise integrations (https://pixiecrm.com/help-centre/category/enterprise-integrations)Client portal overview (https://pixiecrm.com/help-centre/client-portal-overview)Apply API request throttling (https://pixiecrm.com/help-centre/apply-api-request-throttling)Understand one-way API-token storage (https://pixiecrm.com/help-centre/understand-one-way-saas-api-token-storage)Manage API-token lifecycle metadata (https://pixiecrm.com/help-centre/manage-api-token-expiry-revocation-rotation-and-usage-metadata)Data, privacy and security (https://pixiecrm.com/help-centre/category/data-privacy-security)