🧰Tools - Ability to add custom fields

📍 Today: Tools appear to have a fixed set of attributes with no way for admins to add their own custom fields. For large enterprises, that breaks down quickly. We often need to track internal metadata on every application or tool, such as:

• EPR ID

• Internal application ID

• Owner organization

• Compliance classification

• Support tier

Without custom fields on Tools, that information has to live somewhere else or be managed manually outside the platform. That creates duplicate admin work, inconsistent records, and weakens the Tool object as a reliable source of truth.

✨ Desired:

Allow workspace admins to create and manage custom fields on Tools the same way mature enterprise platforms support extensible object metadata.

At a minimum, admins should be able to:

• Add custom fields to Tools

• Choose field types such as text, dropdown, number, date, checkbox, and relationship fields where applicable

• Mark fields as required or optional

• Control who can edit those fields

• Filter, search, and report on Tools using custom field values

• Expose those fields in imports, exports, and API responses

This would let enterprises adapt the Tool object to their own governance model instead of forcing every customer into the same fixed schema.

📊 Business Justification:

For enterprise customers, extensibility is table stakes. Platforms like Salesforce and ServiceNow are widely adopted because admins can extend core objects to match internal operating models without waiting for a vendor to hardcode every field.

Adding custom fields to Tools would help with:

• Governance: Store internal identifiers like EPR ID directly on the Tool record

• Compliance: Track classifications, review dates, or ownership attributes needed for audits

• Data quality: Reduce spreadsheet sprawl and duplicate system maintenance

• Scalability: Support large application portfolios with different business and technical metadata requirements

• Change management: Let admins roll out structured metadata as enterprise needs evolve

For large organizations, the lack of custom fields creates avoidable manual work and makes it harder to use Tools as an enterprise-grade inventory object.

✅ Acceptance Criteria

• Admins can create custom fields on Tools without product team intervention

• Tool-level custom fields support common field types, including text, dropdown, number, date, and checkbox

• Admins can edit field configuration, including field name, required status, and available options where relevant

• Custom field values are visible on each Tool record

• Users can filter and search Tools by custom field values

• Custom field data is available in reporting, export, and API access

• Existing Tool records can be bulk updated or imported with custom field values