Agiled Docs

Custom attributes let you store additional structured information on supported records.

Use attributes when the value needs to be searchable, filterable, importable, or usable in forms and workflows.

Where Attributes Are Used

Attributes can support CRM records, imports, saved views, filters, and structured data capture. Use them when the built-in fields do not cover a real business process.

Attributes are best for information the team will maintain repeatedly. Do not create an attribute for one note that belongs in a comment, task, ticket, or document.

Create An Attribute

Open Settings.
Go to Attributes.
Choose the record type.
Select Create attribute.
Enter a clear label.
Choose the field type.
Save the attribute.

After saving, open one supported record and enter a real test value. Then return to the list or filter view where the team expects to use the attribute. This confirms the field is not only configured but also useful in the workflow.

Good Attribute Design

Use clear names, consistent field types, and only add fields your team will actually maintain. Too many custom fields make forms and imports harder to use.

Choose the field type based on how the data will be used. Use dates for dates, numbers for measurable values, select fields for controlled options, and text only when the value should remain flexible.

Use select fields when values need consistent reporting, such as region, tier, source, contract type, or customer segment. Use text fields only when many different values are expected and filtering is less important.

Avoid attributes that duplicate built-in fields. If Agiled already has a status, owner, due date, amount, email, or relationship field, use the built-in field so tables, reports, workflows, and imports stay consistent.

Attribute Examples

Contact source for CRM segmentation.
Account tier for customer-success review.
Renewal date for contract follow-up.
Industry for account filtering.
Onboarding status for workflow conditions.
Employee certification date for HRM follow-up, when supported by the record type.

Before Importing Data

Create required attributes before importing records. Match CSV column names to attribute labels where possible so mapping is easier during import.

Also update public forms, saved views, report filters, and workflow conditions after adding or changing attributes.

Test with one record before a large import. Create the attribute, edit a record, filter by the attribute, and confirm the value appears where the team expects to use it.

Review Existing Attributes

Disable unused attributes before deleting them. This gives your team time to confirm no forms, imports, workflows, or reports still depend on the field.

Set a review cadence for attributes used in public forms, CRM imports, finance handoffs, or HRM processes. These fields tend to drift as teams rename stages, services, regions, or approval steps.

Before Changing Field Type Or Options

Changing the way a field is used can affect imports, filters, workflows, and forms. Before changing options or replacing a field:

export or review existing values
check public forms that map into the attribute
check saved views that filter on it
check workflow conditions or variables that reference it
update CSV templates used by the team

If historical values matter, create a replacement attribute and migrate records carefully instead of deleting the original field immediately.

Troubleshooting Attributes

If an attribute does not appear where expected, confirm the record type, user permissions, and whether the page was refreshed after setup.

If filters return inconsistent results, check blank values, old option names, and imported spelling variants before changing the field definition.

Custom Attributes