Upload examples and references | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/client-discovery-project-briefing-custom-software-brief-examples Publisher: Pixie Technologies LLC Custom software development brief Upload examples and references Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Provide sample outputs, competitor references or design examples. Audience: CRM administrators, project teams, developers, authorised client contacts and public prospects; Permission: Secure-link recipient; Module v1.1.1; Where to goSecure recipient link → Custom Software Development 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 Provide sample outputs, competitor references or design examples. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow. Follow these steps - Go to Secure recipient link → Custom Software Development Brief. - Find the record, endpoint, field or action used to upload examples and references. - 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 endpointSecure recipient link → Custom Software Development Brief PurposeProvide sample outputs, competitor references or design examples. 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 upload examples and references 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 Upload spreadsheets (https://pixiecrm.com/help-centre/client-discovery-project-briefing-custom-software-brief-spreadsheets)Review the custom software brief (https://pixiecrm.com/help-centre/client-discovery-project-briefing-custom-software-brief-review)Custom software development brief (https://pixiecrm.com/help-centre/topic/client-discovery-project-briefing-custom-software-brief)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)