Skip to main content

Configure project, pipeline, and custom-field rules

Shape project workflows, sales stages, default to-dos, and business-specific record fields.

Written by Geoff Mina

Project settings, sales-pipeline stages, and custom fields define the language and rules Moxie uses to fit your particular business.

Configure project types

Create a separate project type only when the work genuinely needs its own task statuses, project fields, task fields, approval behavior, or client notifications. Keep one type as the default for general work.

Moxie Project settings showing the default project type and counts for statuses and custom fields

Open a project type to configure its Overview, fields, task statuses, and client notifications.

Design the sales pipeline

Name, color, classify, and reorder the stages opportunities move through. Stage type matters: won and lost stages change how opportunities behave, and default to-dos can create a consistent follow-up checklist when a deal enters a stage.

Moxie Sales pipeline settings showing ordered, color-coded stages and stage types

Keep the pipeline detailed enough to guide work without adding stages that do not change what your team does.

Add global custom fields

Create global fields for Clients, Contacts, or Sales opportunities when Moxie's standard fields do not capture an important business detail. These fields can become available in records, lists, filters, imports, tokens, and automations.

Moxie Custom fields settings with Client, Contact, and Sales opportunity scopes

Project and task fields belong to their project type; they are not managed in this global library.

Changing shared configuration can affect active records and everyone using the workspace. Review status deletions, stage behavior, field types, and API keys before saving.


Continue exploring Settings & administration

Did this answer your question?