Use a select field | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/client-discovery-project-briefing-form-templates-select Publisher: Pixie Technologies LLC Form templates and custom schemas Use a select field Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Define supported options for a select input. Audience: CRM administrators, project teams, developers, authorised client contacts and public prospects; Permission: Edit; Module v1.1.1; Where to goAdmin Area → Client Discovery Portal → Form Templates 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 Define supported options for a select input. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow. Follow these steps - Go to Admin Area → Client Discovery Portal → Form Templates. - Find the record, endpoint, field or action used to use a select field. - 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 endpointAdmin Area → Client Discovery Portal → Form Templates PurposeDefine supported options for a select input. 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 use a select field 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 Use a number field (https://pixiecrm.com/help-centre/client-discovery-project-briefing-form-templates-number)Enable uploads in a section (https://pixiecrm.com/help-centre/client-discovery-project-briefing-form-templates-upload)Form templates and custom schemas (https://pixiecrm.com/help-centre/topic/client-discovery-project-briefing-form-templates)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)