Pipeline Creation Settings

Pipeline creation settings control the default behavior when users create new leads or opportunities directly from the CRM pipeline kanban view. Managers can customize what fields appear, set default values, and choose between quick-create dialogs and full form views.

Important

Permissions Required: Sales / Administrator group to configure pipeline creation settings.

Accessing Pipeline Settings

Navigate to CRM ‣ Configuration ‣ Pipeline Creation Settings

Alternatively, pipeline creation settings may be accessible through the CRM team configuration:

  1. Navigate to CRM ‣ Configuration ‣ Sales Teams

  2. Open the sales team to configure

  3. Look for the Pipeline Settings section or tab

Understanding Pipeline Creation

When a user clicks the + button at the top of a pipeline stage column in the CRM kanban view, Progrid creates a new lead or opportunity. This module lets managers control that creation process.

Without this module, clicking + opens a minimal quick-create dialog with just a name field. With this module, managers can:

  • Add fields to the quick-create dialog

  • Set default values for new records

  • Choose between quick-create and full form view

  • Pre-populate fields based on the stage column

Configuring Creation Behavior

Quick-Create vs. Full Form

Choose what happens when users click + on a pipeline column:

  • Quick-Create (default) – A small inline dialog appears at the top of the column. Users enter minimal information and the lead is created instantly.

  • Full Form – The full lead/opportunity form opens in a new view. Users fill in all desired fields before saving.

Tip

Use Quick-Create for high-volume teams that need to capture leads fast. Use Full Form for teams that need complete information upfront.

Default Values

Set default values that auto-fill when creating from the pipeline:

  • Default Sales Team – Automatically assign the creating user’s team

  • Default Salesperson – Automatically assign the creating user

  • Default Tags – Pre-apply tags for categorization

  • Default Priority – Set initial lead priority level

These defaults save time and ensure new leads have consistent baseline data.

Field Configuration

Configure which fields appear in the quick-create dialog:

  1. Navigate to the pipeline creation settings

  2. Review the available field toggles

  3. Enable or disable fields based on your team’s needs

Common fields to include in quick-create:

  • Contact Name – The person’s name

  • Company – The company name

  • Email – Contact email address

  • Phone – Contact phone number

  • Source – Where the lead came from

  • Expected Revenue – Estimated deal value

Note

Adding too many fields to the quick-create dialog defeats its purpose. Include only the fields your team needs to capture immediately. Additional details can be filled in later on the full form.

Per-Team Configuration

Pipeline creation settings can be configured per sales team, allowing different teams to have different workflows:

Inbound Sales Team:

Quick-create with source and email fields enabled. Default priority set to medium.

Outbound Sales Team:

Full form view for complete lead capture. Default salesperson set to the creating user.

Support-to-Sales Team:

Quick-create with minimal fields. Default tags set to “Referral” for leads created from support interactions.

Best Practices

  1. Match settings to workflow. Teams that process many leads quickly benefit from streamlined quick-create. Teams that need thorough initial data should use the full form.

  2. Set sensible defaults. Auto-assigning the salesperson and team eliminates a common source of “unassigned” leads.

  3. Review field selection. Periodically check whether the quick-create fields match your current sales process. Remove fields that are rarely filled and add ones that are frequently needed.

  4. Coordinate with naming rules. If you have an active naming rule, ensure the quick-create dialog includes the fields that the naming rule depends on (e.g., company, contact name) so that names generate correctly from the start.

Next Steps