Please submit all product enhancement ideas below. We welcome your feedback; your ideas will be reviewed by the Product Manager that oversees the development of that part of the product on an ongoing basis and updated with its current status monthly based on our product planning process. Ideas you submit could help us shape features currently in development or grow our repository of requirements for our next big enhancement. Thank you for taking the time to share your thoughts and expertise with us.
If you believe you are experiencing a defect please contact Support.
Just as we are able to mark participants as private, we'd like to be able to mark teams as private. It seems reasonable to have parallel functionality at both the participant and the team level.
When using TeamRaiser as a replacement for Tribute/Personal Giving, there are sometimes cases where a team shouldn't be "searchable", but we still want the team to be able to have a landing page.
When using TeamRaiser for satellite/community events, we use teams as makeshift "event landing pages", where participants can register. Sometimes these are closed events, so though we can limit registration by using team passwords, the teams still show up in the search and on any top-team lists.
The lack of this setting also presumably dictates the lack of the parallel functionality of being able to force a personal page to be private until it's approved by an administrator (Advanced Options > b. Define Event Options > 3. Participant Personal Page Availability after Registration. We want to approve team pages as they are used as community events, but we can't do that if they are team pages because they can't be marked private.
We also sometimes have high profile teams, where we still want the participants to be able to fundraiser, but we don't want the team page to be searchable.
|Area of the Product||TeamRaiser|