Question

Photo of Don Smallman

0

Changing the "Account Registration" Page

2

Hi,

I was wondering how easy it would be to convert the "Account Registration" page to an "Email Newsletter" page?  And, if I changed this page, would future upgrades mess with my changes?

The reason I ask, is that we do not create user names for everyone in our congregation. So, it would be nice to change this somehow to a Newsletter signup page.  Or if there is a better way to do, I'm open.  It would also be nice to have something like this, so that eventually we can get rid of the connection cards we TRY to get people to fill out :-)  Thanks!

  • Photo of Jim Michael

    0

    Thinking out loud here, but I think your "email me the newsletter" could be done more appropriately with a workflow. Workflows can present a form to grab the email address, and can send emails... which is pretty much what you want to do. Alternatively, you could do a workflow that lets a user join a group, then you periodically email the newsletter to that group when it's published. 

    I don't think messing with the registration page to alter its intent is a good idea. When you say you don't create logins for everyone... Are you saying there are NO functions on your Rock web site where a user would need to log in (give online, register for an event, etc?) Or are you saying you're wanting to actively prevent users from creating accounts? (Which would mean they can't really takeadvantage of much of Rock's power)

    • Don Smallman

      Don Smallman

      Thanks Jim. No right now we don't use the RockRMS giving and I allow people to register for events without having to login. Other than those 2 things, why would they need a login? The registration page is still there and functions as designed, we just don't promote it. and so far, very few people have found it. I assume that you allow people to register on your Church site. What is the advantage?

      • Jim Michael

        Jim Michael

        Here we have lots of reasons for people to have accounts: event registration (making people log in for many events means we don't have a bunch of duplicate records to merge), online contribution statement (we don't mail statements out anymore), online giving, and to support various processes... For example, we have an application we call a "ministry application" that anyone who wants to volunteer must fill out. This is done online, and naturally must be filled out by a logged-in user in order to out the application on their record.

      • Photo of Jeremy Hoff

        0

        Hi Don!

        Don Smallman wrote:

         Other than those 2 things, why would they need a login? The registration page is still there and functions as designed, we just don't promote it. and so far, very few people have found it. I assume that you allow people to register on your Church site. What is the advantage?

         

        Having a login essentially provides self-service options for the congregation.  As the sophistication of the RockRMS install increases, the needs for login increases.  Self-service contribution statements, kicking off workflows relative to specific people, dealing with any data even somewhat sensitive... or if you were to power your website with RockRMS you could use Lava for some really clever tailoring of the content to match the logged_in user.  (The documents describe a way to tailor the baptism page depending on the logged_in users' baptism status.)  

        Rock provides a couple methods for identification (such as the photo updater) but that really is identification rather than authentication.  What's more, providers like Facebook for authentication offers the church some information that may not be gathered otherwise. . .

        • Ken Roach

          Ken Roach

          Hi Don. How did you end up resolving this? I'm trying to set up a 'devotion' email list that people can subscribe/unsubscribe to, and I'm wondering what's the best way to do this.

          • Don Smallman

            Don Smallman

            Hi Ken! I didn't... The only way I can think of is to use something like constant contact and continue to migrate users over to that system to send news letters. That way you can create categories to allow people to opt in/out of. With RMS, it is all or none, unless I am missing something. A once a week migration should not be that cumbersome, especially if you can have SQL automatically create an upload file for you that is already in the format needed for your Newsletter email system.