Multiple record types
Extend tasks, projects, clients, brands and leads.
AMS · Connected business workflows
Custom fields — Your process. Your details.
Extend supported records with the information that makes your way of working specific.
Who this helps
Teams whose tasks need consistent information beyond the standard title, status and due date.
The situation
The collection name, expected asset count and review readiness are easy to overlook when buried in a description.
Fictional example: a task records Autumn collection, 12 assets and a Ready for review checkbox. This website example makes no live changes.
Follow the example, step by step
Define the information the team needs
- What you do
- Create suitable text, number and checkbox fields for the supported task scope.
- What changes
- The sample shows separate Collection, Asset count and Ready for review properties.
- Why it helps
- Each detail has a consistent place instead of relying on free-form wording.
Name the collection
- What you do
- Enter Autumn collection in the text property.
- What changes
- The collection value appears beside the task.
- Why it helps
- The person reading the record can identify the relevant body of work.
State the expected quantity
- What you do
- Set Asset count to 12.
- What changes
- The number property records a concrete quantity.
- Why it helps
- The team can check the intended amount without interpreting a paragraph.
Make readiness explicit
- What you do
- Check Ready for review after the team has assessed the work.
- What changes
- The checkbox changes state while the collection and quantity remain visible.
- Why it helps
- A reviewer can see the recorded readiness signal alongside the other details.
What your team gains
The team can inspect these three details as structured values beside the work.
Add structured information where it belongs instead of hiding it in free-form notes.
Inside Custom fields
Field types
Use text, numbers, selections and other supported property types.
Configurable options
Define labels, choices and required information.
Project scope
Use available task type or project-specific field definitions.
Structured values
Keep information in consistent fields instead of scattered notes.
Field-change triggers
Respond to supported custom-field changes through configured automations.
Questions and requirements
Does checking Ready for review move or assign the task?
Not by itself. It records a field value. A supported field-change trigger can start a separately configured automation when that behavior is needed.
Can I add these fields to every kind of record?
Available field types and scopes depend on the supported entity and configuration. Custom fields do not bypass the record’s permissions.
Requirements and limits
Field types and scope depend on the entity and configuration. Custom fields do not bypass record permissions.
Understand the next tool here
Read how each connection helps before choosing whether to open another page. Moving between tools does not itself configure an automatic handoff.
Automations — read how it fits
Configure a supported field-change rule if a particular value should initiate an action.
Turn repeatable decisions into workflows your team can inspect, test and control.
Fictional example: a high-priority task entering In review is assigned to Layla by a configured workflow.
Before you use it
Automations require a paid plan. Triggers and actions are filtered by permissions, scope, connected account capabilities and configuration.
This page simulates a task-status rule locally; it does not execute a server workflow or send notifications.
Optional: explore the full Automations story ↗Projects & tasks — read how it fits
Use the structured values while planning and reviewing the task.
Give every task an owner, a deadline and the context to move forward.
Fictional example: Nour moves the Autumn launch creative brief from In progress to Review.
Before you use it
Available views and actions depend on your access. Time tracking and automations require an eligible paid plan.
Optional: explore the full Projects & tasks story ↗