[GH-ISSUE #1347] expose custom fields in the frontend, not just in the agent list #2784

New issue

Open

opened 2026-03-14 05:28:40 +03:00 by kerem · 4 comments

kerem commented

2026-03-14 05:28:40 +03:00

Owner

Originally created by @sharkpd on GitHub (Nov 9, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1347

Custom fields have been foreseen on: customers, sites and agents and they are very useful, in the issue #308 are asked to be able to expose the custom fields only on agents, why not outsource the exposure also on customers and sites?
with a view to integrating with other software, it might be useful to have vision of some information without entering the customer or site modification window to view the data.

Originally created by @sharkpd on GitHub (Nov 9, 2022). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1347 Custom fields have been foreseen on: customers, sites and agents and they are very useful, in the issue #308 are asked to be able to expose the custom fields only on agents, why not outsource the exposure also on customers and sites? with a view to integrating with other software, it might be useful to have vision of some information without entering the customer or site modification window to view the data.

kerem added the

enhancement

label

2026-03-14 05:28:40 +03:00

kerem commented

2026-03-14 05:28:51 +03:00

Author

Owner

@wh1te909 commented on GitHub (Nov 9, 2022):

not sure I understand. if you are trying to integrate with other software this has nothing to do with the frontend, you just get the custom fields or whatever else you need by querying the API: https://docs.tacticalrmm.com/functions/api/

@wh1te909 commented on GitHub (Nov 9, 2022): not sure I understand. if you are trying to integrate with other software this has nothing to do with the frontend, you just get the custom fields or whatever else you need by querying the API: https://docs.tacticalrmm.com/functions/api/

kerem commented

2026-03-14 05:28:56 +03:00

Author

Owner

@sharkpd commented on GitHub (Nov 10, 2022):

I do not consider reading by third parties but reading data written by third parties. Let me explain better with an example:
TacticalRMM is in use by an IT company and a customer custom field refers to an alert for operators such as a trivial "there are administrative pending".
this alert or flag or simple string to be displayed is populated by the ERP management system of the company that when "there are administrative pending" makes a call to tactical to populate this field (I expect a custom field containing the ERP customer code in the example just described ...).
I don't know if it could be of common interest to expose this info to help or alert operators

@sharkpd commented on GitHub (Nov 10, 2022): I do not consider reading by third parties but reading data written by third parties. Let me explain better with an example: TacticalRMM is in use by an IT company and a customer custom field refers to an alert for operators such as a trivial "there are administrative pending". this alert or flag or simple string to be displayed is populated by the ERP management system of the company that when "there are administrative pending" makes a call to tactical to populate this field (I expect a custom field containing the ERP customer code in the example just described ...). I don't know if it could be of common interest to expose this info to help or alert operators

kerem commented

2026-03-14 05:29:01 +03:00

Author

Owner

@silversword411 commented on GitHub (Nov 10, 2022):

Custom fields are in the frontend and api

We still don't understand the request

@silversword411 commented on GitHub (Nov 10, 2022): Custom fields are in the frontend and api <img width="408" alt="2022-11-10_102937 - custom fields" src="https://user-images.githubusercontent.com/13395348/201137161-61d1e01d-4fd3-48f3-ab84-8bb3ba0f16dd.png"> We still don't understand the request

kerem commented

2026-03-14 05:29:06 +03:00

Author

Owner

@sharkpd commented on GitHub (Nov 15, 2022):

My proposal referred to the possibility of having some custom fields in the dashboard in the list of clients and sites (having custom fields on them) and I was not referring to custom fields on agents.

I understand that it may not be a useful proposal for most users but it would give a way to have a view of the most important personalized data that you want to expose to users who use the dashboard.

@sharkpd commented on GitHub (Nov 15, 2022): My proposal referred to the possibility of having some custom fields in the dashboard in the list of clients and sites (having custom fields on them) and I was not referring to custom fields on agents. ![image](https://user-images.githubusercontent.com/24247590/202031160-79352c41-c81c-4961-96e1-99e396d35b5b.png) I understand that it may not be a useful proposal for most users but it would give a way to have a view of the most important personalized data that you want to expose to users who use the dashboard.