<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Trailblazer Community Latest Ideas</title>
		<link>https://trailblazer.salesforce.com/</link>
		<description>Latest Ideas submitted on Trailblazer Community</description>
			<item>
				<title>Scheduled or Automated Subscription Cancellation</title>
				<pubDate>Fri, 11 Jun 2021 20:12:09 +0000
				</pubDate>
				<link>https://trailblazer.salesforce.com/ideaView?id=0874V000000EMYsQAO</link>
				<description>For perpetual gifts, a reminder/auto-scheduling tool is needed, so that either donors themselves or OA can log into SPC and process reccurence cancellation.
					
				</description>
			</item>
			<item>
				<title>Flag or prevent Admins from uploading employees from another country</title>
				<pubDate>Tue, 8 Jun 2021 19:16:12 +0000
				</pubDate>
				<link>https://trailblazer.salesforce.com/ideaView?id=0874V000000wnV2QAI</link>
				<description>Currently SPC does not flag nor prevent admins from uploading employee records whose workplace country/postal code is outside of processeor&amp;#39;s country, in another country. It&amp;#39;d be beneficial if SPC prevents or flags whenever an employee from another country is uploaded. We have a few cross border accounts (sometimes managed by the same person) and it&amp;#39;d be beneficial if an accidental upload can be prevented. 
					
				</description>
			</item>
			<item>
				<title>Multi-factor authentication for Philanthropy Cloud users</title>
				<pubDate>Thu, 3 Jun 2021 21:18:09 +0000
				</pubDate>
				<link>https://trailblazer.salesforce.com/ideaView?id=0874V000000lggGQAQ</link>
				<description>This request was flagged by a client during a security assesment. They would like the ability to turn on MFA for username/password users on the site, espeically admin users. 
					
				</description>
			</item>
			<item>
				<title>Password reset requirements for SPC users</title>
				<pubDate>Thu, 3 Jun 2021 21:16:26 +0000
				</pubDate>
				<link>https://trailblazer.salesforce.com/ideaView?id=0874V000000lggBQAQ</link>
				<description>This request has been flagged as part of a security assesment with one of our clients. They would like the system to require a password update at a regular interval for users with a username/password log-in. 
					
				</description>
			</item>
			<item>
				<title>change order impact fund</title>
				<pubDate>Thu, 3 Jun 2021 20:20:51 +0000
				</pubDate>
				<link>https://trailblazer.salesforce.com/ideaView?id=0874V0000015LjJQAU</link>
				<description>it would wonderful to be able to change the order of Impact Funds. 
					
				</description>
			</item>
			<item>
				<title>REST API should return JSONAPI Format</title>
				<pubDate>Tue, 8 Jun 2021 17:27:31 +0000
				</pubDate>
				<link>https://trailblazer.salesforce.com/ideaView?id=0874V000000lgbKQAQ</link>
				<description>REST API should return JSONAPI Format
					
				</description>
			</item>
			<item>
				<title>Allow users to opt out of campaign</title>
				<pubDate>Wed, 26 May 2021 16:00:29 +0000
				</pubDate>
				<link>https://trailblazer.salesforce.com/ideaView?id=0874V0000003mq0QAA</link>
				<description>It would great if users could opt of a campaign, specifically for their annual campaign. Traditionally compaies running their campaign on ePledge would allow employees the option to opt out of the campaign, but would be counted toward participation. 
					
				</description>
			</item>
			<item>
				<title>Philanthropy Cloud - Suppression Features to Volunteer Content Management</title>
				<pubDate>Wed, 19 May 2021 14:42:25 +0000
				</pubDate>
				<link>https://trailblazer.salesforce.com/ideaView?id=0874V000000M4QIQA0</link>
				<description>&lt;span style=&quot;font-size: 11pt;&quot;&gt;&lt;span style=&quot;font-family: Calibri,sans-serif;&quot;&gt;The ability to suppress certain organization’s volunteer content from appearing on the platform. Since the recent HandsOnConnect (HoC) integration, a number of volunteer opportunities from a now defunct organization are populating in Philanthropy Cloud (originally published to HoC). If we could suppress this organization from appearing in Philanthropy Cloud, it could would prevent users from being led to broken/dead links and unable to register to volunteer.&lt;/span&gt;&lt;/span&gt;&lt;br&gt; 
					
				</description>
			</item>
			<item>
				<title>Set end date for recurring credit card donations</title>
				<pubDate>Tue, 18 May 2021 00:10:28 +0000
				</pubDate>
				<link>https://trailblazer.salesforce.com/ideaView?id=0874V000000M4PZQA0</link>
				<description>Currently, r&lt;span style=&quot;font-size: 11.0pt;&quot;&gt;&lt;span style=&quot;&quot;&gt;ecurring credit card donations do not end until the donor cancels them in their my giving section or submits a cancellation request.  It would be helpful if the donor can choose an end date or specific month to end their credit card charged.  A number of donors will choose to a different impact fund or nonprofit agency annually.   &lt;/span&gt;&lt;/span&gt;
					
				</description>
			</item>
			<item>
				<title>Stop failed credit card notification emails in Demo/Partner</title>
				<pubDate>Wed, 19 May 2021 23:49:55 +0000
				</pubDate>
				<link>https://trailblazer.salesforce.com/ideaView?id=0874V0000015LXcQAM</link>
				<description>&lt;p&gt;The failed/expired credit card notification emails in the Partner/Demo ennvironments are causing significant user confusion and extra effort for Processor OAs. Processor Admins indicate that they are spending a lot of time educating colleagues about this issue including the workarounds, and there is a chance that a Production notification will be missed because it is mixed in with all the test environment notifications.&lt;/p&gt;
					
				</description>
			</item>
	</channel>
</rss>