Hi John,
The portal will be accessed by public users and if you are going to have a API key out there it might be a security vulnerability, however if you think the company information can be viewed by all users then in that case you can create a custom json object file where it has a list of all the companies in your account. By linking that to your portal we'll be able to get all the companies. That can be populated as a dropdown in the UI and stored inside a text field internally when the form is saved.
Let me know if this helps.
Regards
Jerry
Jerry
Let me just get a couple of things clarified, when you say; "The portal will be accessed by public users and if you are going to have a API key out there it might be a security vulnerability"
I'm aware that the public portal is available to the public, but the way we are using it means that you can only submit a ticket (and therefore see any data in the form) after you authenticate with a corporate Google account. Does that negate the concerns that you raised using this method?
"however if you think the company information can be viewed by all users then in that case you can create a custom json object file where it has a list of all the companies in your account. "
The list of companies to appear in the drop down can be visible to all authenticated users, but not un-authenticated users
By linking that to your portal we'll be able to get all the companies. That can be populated as a dropdown in the UI and stored inside a text field internally when the form is saved.
So, ultimately this sounds promising, but could you clarify the points I've raised and we'll see if we can go forward with this?
Thanks and Regards
John