SecureGive

Question

0

SecureGive

James Trow posted 8 Years Ago

Where can I find instructions how to integrate SecureGive with Rock?

Michael Garrison · Answer 1 · 2016-07-27T21:30-07:00

0

Michael Garrison replied 8 Years Ago

Hey James!

We use SecureGive but I was helped through on a 1-on-1 basis when they were testing it out so I don't know that they've created any one central documentation location.

Here's how it works, from memory:

- Download the plugin from the Rock Store- it will create an API user. I think it will add that user to the RSR - Rock Administration security group, which is necessary.
- Then inform SecureGive that you are using Rock- they will manually change your SG portal over to support Rock
- Once they've done that, you'll need to provide the interface with your Rock URL so it can connect to your API
- Once that's stored, you'll need to "link" your Rock accounts with the accounts you've got already in SG (General Fund, Missions, Camp Payments, etc) - on the SG accounts page you'll "edit" each account and at the bottom is a drop-down to select the equivalent account from the list it pulls from your Rock installation.
- You do the same linking for your campus(es), even if you've only got one.
- Finally, you need to go through each of your contributors in the SG portal and "link" them up in a similar manner. Nicely, SG does a search and recommend when you load the page, but you can confirm or change what they found and then store it

Once that's all done, it will do a nightly push to Rock automatically- no need to set up the "Download Contributions" job in Rock. It will create a different batch each night, load the contributions for the day and leave the batch open for you to provide the control value and close it out.

Let me know if you're seeing anything that doesn't agree with what I'm remembering and I'll help you through. Alternately, they were wonderfully responsive in the rockrms.slack.com channel using their @SecureGive username- DM them or jump into the #Contributions channel and I'll bet they'll get back with you.

Edit Answer

Hey James!We use SecureGive but I was helped through on a 1-on-1 basis when they were testing it out so I don't know that they've created any one central documentation location.Here's how it works, from memory:- Download the plugin from the Rock Store- it will create an API user. I think it will add that user to the RSR - Rock Administration security group, which is necessary. - Then inform SecureGive that you are using Rock- they will manually change your SG portal over to support Rock - Once they've done that, you'll need to provide the interface with your Rock URL so it can connect to your API - Once that's stored, you'll need to "link" your Rock accounts with the accounts you've got already in SG (General Fund, Missions, Camp Payments, etc) - on the SG accounts page you'll "edit" each account and at the bottom is a drop-down to select the equivalent account from the list it pulls from your Rock installation. - You do the same linking for your campus(es), even if you've only got one. - Finally, you need to go through each of your contributors in the SG portal and "link" them up in a similar manner. Nicely, SG does a search and recommend when you load the page, but you can confirm or change what they found and then store itOnce that's all done, it will do a nightly push to Rock automatically- no need to set up the "Download Contributions" job in Rock. It will create a different batch each night, load the contributions for the day and leave the batch open for you to provide the control value and close it out. Let me know if you're seeing anything that doesn't agree with what I'm remembering and I'll help you through. Alternately, they were wonderfully responsive in the rockrms.slack.com channel using their @SecureGive username- DM them or jump into the #Contributions channel and I'll bet they'll get back with you.

<p>Hey James!</p><p>We use SecureGive but I was helped through on a 1-on-1 basis when they were testing it out so I don't know that they've created any one central documentation location.</p><p>Here's how it works, from memory:</p><p>- Download the plugin from the Rock Store- it will create an API user. I think it will add that user to the RSR - Rock Administration security group, which is necessary.<br>- Then inform SecureGive that you are using Rock- they will manually change your SG portal over to support Rock<br>- Once they've done that, you'll need to provide the interface with your Rock URL so it can connect to your API<br>- Once that's stored, you'll need to "link" your Rock accounts with the accounts you've got already in SG (General Fund, Missions, Camp Payments, etc) - on the SG accounts page you'll "edit" each account and at the bottom is a drop-down to select the equivalent account from the list it pulls from your Rock installation.<br>- You do the same linking for your campus(es), even if you've only got one.<br>- Finally, you need to go through each of your contributors in the SG portal and "link" them up in a similar manner. Nicely, SG does a search and recommend when you load the page, but you can confirm or change what they found and then store it</p><p>Once that's all done, it will do a nightly push to Rock automatically- no need to set up the "Download Contributions" job in Rock. It will create a different batch each night, load the contributions for the day and leave the batch open for you to provide the control value and close it out.</p><p><br></p><p>Let me know if you're seeing anything that doesn't agree with what I'm remembering and I'll help you through. Alternately, they were wonderfully responsive in the rockrms.slack.com channel using their @SecureGive username- DM them or jump into the #Contributions channel and I'll bet they'll get back with you.<br></p>

<p>Hey James!</p><p>We use SecureGive but I was helped through on a 1-on-1 basis when they were testing it out so I don't know that they've created any one central documentation location.</p><p>Here's how it works, from memory:</p><p>- Download the plugin from the Rock Store- it will create an API user. I think it will add that user to the RSR - Rock Administration security group, which is necessary.<br>- Then inform SecureGive that you are using Rock- they will manually change your SG portal over to support Rock<br>- Once they've done that, you'll need to provide the interface with your Rock URL so it can connect to your API<br>- Once that's stored, you'll need to "link" your Rock accounts with the accounts you've got already in SG (General Fund, Missions, Camp Payments, etc) - on the SG accounts page you'll "edit" each account and at the bottom is a drop-down to select the equivalent account from the list it pulls from your Rock installation.<br>- You do the same linking for your campus(es), even if you've only got one.<br>- Finally, you need to go through each of your contributors in the SG portal and "link" them up in a similar manner. Nicely, SG does a search and recommend when you load the page, but you can confirm or change what they found and then store it</p><p>Once that's all done, it will do a nightly push to Rock automatically- no need to set up the "Download Contributions" job in Rock. It will create a different batch each night, load the contributions for the day and leave the batch open for you to provide the control value and close it out.</p><p><br></p><p>Let me know if you're seeing anything that doesn't agree with what I'm remembering and I'll help you through. Alternately, they were wonderfully responsive in the rockrms.slack.com channel using their @SecureGive username- DM them or jump into the #Contributions channel and I'll bet they'll get back with you.<br></p>

Save Cancel

Craig Mashburn · Answer 2 · 2018-11-02T08:28-07:00

0

Craig Mashburn replied 6 Years Ago

Hey guys. We are looking at trying to stay with Securegive when we move to Rock Jan1. I was wondering if y'all were still doing this and seen any problems.

Question

0

SecureGive

0

0