Create A Custom Attribute

Custom attributes store extra structured data on supported records.

Use custom attributes for data your team needs to search, filter, report, or reuse in workflows. Do not create a custom attribute for information that already has a standard field in Agiled.

Choose An Entity

Open the attributes page for the entity you want to customize. Supported entity types include accounts, contacts, deals, estimates, tickets, forms, tasks, projects, invoices, payments, and expenses.

Choose the entity where users will naturally enter and maintain the data. For example, store industry on accounts, renewal date on deals or subscriptions, and delivery preference on contacts when it belongs to a person.

Create The Attribute

1. Open Settings.
2. Go to Attributes.
3. Choose the entity type.
4. Select Add new.
5. Choose the attribute type.
6. Enter the name and optional description.
7. Configure options, precision, or currency settings when the type requires them.
8. Choose whether the field is required.
9. Add a default value if needed.
10. Create the attribute.

Start with one low-risk attribute when building a new process. It is easier to teach the team and clean imports when the first field is proven before adding several related fields.

Choose The Right Type

Use:

• Text for short free-form values.
• Number or currency for values users need to compare or calculate.
• Date for deadlines, renewal dates, and scheduled events.
• Select options when teams should choose from a controlled list.
• Boolean fields when the answer is yes or no.

Required fields are useful for critical data, but they can slow down quick record creation. Make a field required only when users truly cannot save a good record without it.

Choose select options when values must be consistent for filters, imports, reports, or workflows. Use text only when the answer genuinely needs free-form wording.

Naming Guidance

Use names users will understand on forms, tables, imports, and reports. Avoid abbreviations that only one team knows. If the field is customer-facing through a form, use customer-safe wording.

Use the same wording across forms, CSV templates, saved views, and internal process notes. Slightly different labels make mapping and training harder.

After Creating

Open a real record for the entity and confirm the new field appears where users expect it. Then update import templates, forms, workflows, saved views, or reports that should use the new attribute.

Create one test record or edit a low-risk existing record before announcing the field. Confirm required behavior, default value, option labels, formatting, and where the field appears in tables or detail pages.

Before Making It Required

Check existing records first. If many records are missing the value, populate or import the data before making the attribute required, otherwise normal record editing may become harder for the team.

Also check automated creation paths such as forms, imports, workflows, and integrations. Required fields can block or complicate record creation when those paths do not provide the value.

Downstream Review

After creating an attribute, update forms, imports, saved views, workflows, and reports that should use it. A field is only useful when it appears in the workflow where users actually make decisions.

Attribute Launch Checklist

Before announcing a new attribute:

• test it on one record
• add it to needed table views
• update import templates
• update public or internal forms
• check workflow conditions
• document who owns cleanup and future option changes

Related Docs

• Attributes
• Manage Custom Attributes