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.
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.
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.
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



