Manage Attributes By Entity
Create, edit, reorder, enable, disable, and delete custom fields for each supported record type.
Attribute settings let admins manage custom fields for specific record types. Use them when contacts, deals, invoices, tasks, projects, payments, expenses, or other records need extra structured information.
Open Settings > Attributes, then choose an entity type such as Contact, Deal, Invoice, Payment, Expense, Task, or Project.
Choose The Entity Type
Each entity type has its own custom fields. A field created for contacts does not automatically appear on deals, invoices, or tasks.
Supported entity groups can include:
- Account
- Contact
- Deal
- Estimate
- Ticket
- Form
- Task
- Project
- Invoice
- Payment
- Expense
Choose the entity that owns the information. For example, store contract renewal date on the account when it describes the customer, but store implementation deadline on the project when it describes delivery work.
Create A Field
Use Add to create a field. Define the name, field type, description, default value, required state, enabled state, options, and any field settings.
Before making a field required, confirm the team can provide the value during normal work. Required fields that users cannot answer will slow down record creation.
Edit, Reorder, Or Disable Fields
Edit fields when labels, descriptions, options, or required settings need to change. Reorder fields so the most important ones appear first.
Disable a field when it should stop appearing in active workflows but its past data should remain available. Delete only fields that were created by mistake or are safe to remove.
System Fields
Some fields can be system fields. System fields may not allow deletion or full editing because other parts of Agiled depend on them.
Do not work around a system field by creating a duplicate with a similar name. That usually creates confusion in imports, forms, reports, and API usage.
Field Design Checklist
- Field name is short and clear.
- Description explains when to use it.
- Field type matches the data.
- Options are complete and not duplicated.
- Required setting is justified.
- Field appears on the correct entity.
- Reorder places high-value fields first.
- Disabled fields are reviewed before deletion.