Recommend overview
Understand the public Recommend a GP form, its sign-in boundary, and what happens after a signed-in visitor submits a recommendation.
Recommend is one public Recommend a GP form tied to an organization link. It is not a recommendation feed, deal-recommendation browser, or organization-facing recommendation history.
One public page
The customer-facing route is https://recommend.infra.one/<org-slug>. The organization in the link receives the recommendation association, but the visitor does not need to belong to that organization.
An anonymous visitor sees Recommend a GP and Log in. Authentication returns the visitor to the same organization path. Any signed-in Infra One user can then open the form, including a user with no membership in that organization.
The page uses a header-only public shell. There is no Recommend sidebar because the service has no other customer-facing page.
What the form sends
Each GP row collects:
- First name;
- Last name;
- Email.
The signed-in recommender can also edit the invitation email’s Subject and Message. Recommend commits all valid GP records in one database transaction, then attempts an invitation to each GP and a copy to the recommender. The success message confirms the records and delivery attempts, not receipt by every mailbox.
The form starts with one GP row and supports up to 10. Add GP adds a row, Remove GP removes an extra row, and Send recommendation(s) submits the complete set.
What Recommend does not show
Recommend does not expose a customer list of submitted recommendations, GP statuses, or other investors’ recommendations. The form resets after a successful submission and reports Sent the recommendations.
The normal duplicate check reports You have already recommended this person. when the same signed-in account submits the same email again. This check runs before insertion and is not a database uniqueness guarantee under concurrent submissions. Another recommender can recommend that person independently.