We also reject people based on a certain criteria. Mostly because they are vendors who are trying to sneak into our org and sell our members. They should get an automated email telling them that they don't meet the criteria and will not be admitted to events. If they don't get this email, they will certainly just show up.

So, I've been forced to keep a separate spreadsheet with their names and emails to do a mail merge to any new rejections prior to each of our events. It's time consuming and easy to screw up. This should be standard functionality.

Lamees, thanks for posting.

The question is why you need to keep this information if you reject membership?
As the workaround, I can suggest you yo use Suspend function. In this case, the system doesn't delete all this information.

Also, I merged your idea with existing one about tracking rejected applications.

Katya, Astra crew

If a membership application is rejected, the record is changed to Contact instead of Member. The problem with this is that membership information captured in an application is lost.

Please look into revising the workflow for rejecting membership applications. Ideally, the record should be retained as a member and tracked under rejects in the Member Summary report.

Yes, it would be very helpful to track rejected applications. Right now if an applicant get rejected, the record switches to a non-member status. The information submitted in the application are lost in all membership fields for that record since non-members don't have them. This can cause an issue. For example, if the application has qualifying questions and the applicant gets rejected base on this data, the information is lost once the application is rejected and there is no historic data to explain the rejection in the future (unless captured manually by an administrator in the notes field). Not the best solution. I suggest rejects are tracked under member records instead.

Interesting suggestion, thank you.