Continue a brief from the client area | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/client-discovery-project-briefing-client-portal-customer-tab-secure-form Publisher: Pixie Technologies LLC Client portal and customer-profile access Continue a brief from the client area Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Follow this guide to use the secure form action for an owned request. Audience: CRM administrators, project teams, developers, authorised client contacts and public prospects; Permission: Authenticated linked client contact; Module v1.1.1; Where to goClients Area → Client Briefs → Brief 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 Use the secure form action for an owned request. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow. Follow these steps - Go to Clients Area → Client Briefs → Brief. - Find the record, endpoint, field or action used to continue a brief from the client area. - 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 Workspace or endpointClients Area → Client Briefs → Brief PurposeUse the secure form action for an owned request. Rules and limits - The action is available only where the supplied module exposes it and the signed-in user or API client meets the stated access conditions. - Internal helpers are documented under the visible workflow or endpoint they support rather than presented as invented menu pages. Check it worked - The continue a brief from the client area 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 Understand client ownership checks (https://pixiecrm.com/help-centre/client-discovery-project-briefing-client-portal-customer-tab-ownership)Use the administrator customer tab (https://pixiecrm.com/help-centre/client-discovery-project-briefing-client-portal-customer-tab-customer-tab)Client portal and customer-profile access (https://pixiecrm.com/help-centre/topic/client-discovery-project-briefing-client-portal-customer-tab)Browse all Client Discovery & Project Briefing Portal guides (https://pixiecrm.com/help-centre/category/client-discovery-project-briefing)Client portal overview (https://pixiecrm.com/help-centre/client-portal-overview)Add and manage customer contacts (https://pixiecrm.com/help-centre/add-and-manage-customer-contacts)Configure customer contact permissions (https://pixiecrm.com/help-centre/configure-customer-contact-permissions)Upload and share customer files (https://pixiecrm.com/help-centre/upload-and-share-customer-files)Configure SMTP email delivery (https://pixiecrm.com/help-centre/configure-smtp-email-delivery)Review email delivery issues (https://pixiecrm.com/help-centre/review-queued-email-and-delivery-issues)