Recommend access and form states

Recommend separates public page access from authenticated submission. It does not use organization membership as the submission permission.

Access matrix

Visitor	What the page shows	Can submit?
Anonymous visitor with a valid organization link	Recommend a GP, an explanation that recommendations carry the visitor’s name, and Log in	No
Signed-in user without membership in the linked organization	The full recommendation form	Yes
Signed-in organization member or admin	The same full recommendation form and header-only shell	Yes
Any visitor with an invalid organization slug	No form; the organization lookup fails	No

The route deliberately has no Recommend capability check. A valid signed-in user can submit for the organization named in the link even when that user is not one of its members.

Organization and identity association

Recommend assigns the organization from the URL, the recommender from the signed-in account, and the GP identity from the submitted first name, last name, and email. Client-supplied organization or recommender identifiers are not accepted as substitutes for those server assignments.

The sign-in link carries a return path for the same organization page. Anonymous visitors cannot type GP data before authentication because the form is not rendered in that state.

Customer-visible states

State	Visible result
Signed out	Log in prompt; no recommendation form.
Ready	One empty GP row, Add GP, Recommendation email, and Send recommendation(s).
Editing	One to 10 GP rows; extra rows have Remove GP.
Validation failed	Fix the highlighted fields before submitting and field-specific errors; typed rows remain.
Duplicate rejected	You have already recommended this person. and an error on that row’s email.
Submitted	The records were committed and delivery was attempted; Sent the recommendations appears and the form resets.

No customer status tracker

The customer Recommend surface has no list, detail page, or lifecycle tracker for submitted recommendations. Recommendation workflow statuses used by internal operations are not exposed through this product page. Do not describe Recommend as a place to browse deals, tips, or another investor’s recommendations.

Duplicate scope

The normal duplicate check combines the GP email with the signed-in recommender, including across different organization links. It is a pre-insert check rather than a database uniqueness constraint, so simultaneous submissions can still create duplicates. A different recommender can submit the same GP independently.