One-time Password

For an extra layer of security, you may now take advantage of our one-time password capability.

One-time password? What’s that? Until now, logging into ShalomCloud was a matter of entering an email address and a password. That is still the default.

However, if you enter the synagogue options panel, you’ll see three choices: To not use OTP, or to require OTP for all, or to have OTP be an individual option.

If you opt to require OTP, everyone logging into ShalomCloud will see a second login screen. At the same time, the system will send that user a numeric code, to the logon email; and, if there is a cell phone in the user’s profile, the system will also send the code via text message.

If you make the second factor an option for your synagogue, then you’ll use a checkbox for each individual who prefers to log on via both email/password, and the six-digit number sent via email and/or cell.

Please follow this video to see how to put this capability into action.

One-time password
Process Flags

Some possible future enhancements:

Offering a preference between cell phone and email, to receive the code. For now, since cell phone is a new field in the user record, we’ll send to the email always, and the cell phone if it’s there.

Offering authentication via a phone app, such as Google Authenticator or Twilio Authy. This would mean scanning a bar code with your phone, and then using the phone app to retrieve the login code. This is considered a more secure way to implement MFA (Multi-Factor Authentication), but more complex.

Small Enhancements

Here are described several small enhancements. Most of the time, we include a video. However, in this case, a screen snapshot should serve well to illustrate these changes.

When you’re doing Yahrzeit maintenance, you will now see a search box to jump right to the last name in question. This saves you from scrolling through several pages of Yahrzeits.

Yahrzeit search
Yahrzeit search

Second of the small enhancements: in the area of financial categories. If you use our contribution portal, you’re probably aware that you can select which categories appear in the drop-down box. You’d select “public” for those; the rest are internal, or private. If you have dozens to hundreds of categories, but want only a handful to appear in the portal, you can use the new button to declare all categories non-public. After using that button, you would flip to public the relatively small number of categories to appear in the portal.

Make all non-public

Third thing — if you use our form builder, and specifically radio buttons and check-boxes — you now have up to sixteen choices for each, up from five.

While we’re on the subject of the form builder — if you’d like to see responses from prior forms, you can now select which set of forms or registrations you’d like to review:

Select a registration

Display Children in the Directory

This article announces a change in how to display children in the directory.

First, some background — please read this previous article on a few changes that preceded this one.

Now, for this change. Until now, if you wanted to list children in the directory, you would select their roles, along with adults and parents. With that choice, children would appear if they had a cell phone or email. If they had neither, their names would not appear. Moreover, if you wanted to show children’s names, but omit the cell and email, you would have to individually check that option per child.

It’s simpler now. Basically, you can follow two rules. Rule one — the Role within family determines whose names appear with their personal contact information. Rule two — by adding the phrase {children} to the letter template for the Directory, you’ll display children in the directory. First names only, as a list.

Here’s a short (3m, 36s) video showing this change in action.

How to add a list of children within the directory.

Notification Flags

Now available — email notification flags, to control who receives any of various notifcations.

Until this change, the system used three rules to determine who received email notifications:

  1. Anyone with read or write permission for financial activity would receive an email whenever a payment occurred.
  2. Anyone with read or write permission for schools would receive an email whenever a school registration occurred.
  3. Anyone with read or write permission on families would receive a notification whenever any other type of form arrived.

With this change, you can designate which of these notifications go to each user. You’ll see a yes/no choice, when you edit the profile for any user.

Be it noted that, initially, we’ve set the flags such that there is no change in who receives what. Thus, we recommend that you have a look at your profiles, and turn off the flags for those who are receiving extraneous email notifications.

Feel free to look over this short (2m, 50s) video showing how to edit these three new flags.

Allocate Recurring Payments

We now offer the ability to allocate recurring payments. That is, within a single payment, to specify exactly what to apply to any and all outstanding items. Thus, you can now pay against categories such as pledges, school tuition, and a security fee, concurrently.

A little background: When we first rolled out recurring payments, the only method available was “waterfall.” Meaning the entire payment would go against whatever item was at the top of the list of owed items. After the top item went to a zero balance, the recurring payment would proceed to the second item, etc.

With this ability to allocate recurring payments, you can declare exactly how much to go against each outstanding item. You can concurrently pay pledges, school tuition, security fees, and the like.

You can change an existing waterfall to an allocation if you’d like. In doing so, you needn’t re-enter any the payment information; but rather just change from waterfall to allocation, as illustrated in this video.

allocation recurring payments
Recurring Payment Allocations

Payment Tear-off

Monthly statements now have an option to include a payment tear-off at the bottom of the statement.

We at ShalomCloud have done much to enable electronic statements and electronic payments.

However, inevitably, a segment of your congregation prefers to deal with paper statements and paper payments. Accordingly, you now have the option of including a stub at the bottom of your statements.

The left side of the tear-off shows the amounts owed for the household. Items such as pledges, school tuition, security fees, Bar/Bat Mitzvah fees. Then, the right side has the family name and address, along with a place to record payment information. That payment information could be a check number and amount, or card information.

Payment Tear-off
Payment Tear-off

Feel free to peruse this video demonstration of this feature.

Five Enhancements

We have five enhancements to show and explain. In no particular order, they are as follows.

On the member query, you can now enter part (or all) of a family code as your search criteria. This might be especially useful if you’re intending to send an email via ShalomCloud to members of a specific family, who may have different last names.

Also on the member query, specifically the part of the screen used to send emails. Until now, the email addresses were placed into a text box. If you wanted to avoid sending content to one or several of the selected members, you had to find the respective email addresses and delete them from the screen. Now, you can use the check-boxes on the right of the screen to effect that selection.

Turning our attention to Yahrzeits — in the case where

  • the person passed away on February 29 (of a leap year, of course), and
  • there are observers by Gregorian date, and
  • the current year is not a leap year

the system works correctly if you pull a list for February 1 through February 28.

The “all-children report” now includes a record count.

For those who use our QuickBooks Desktop integration — you can now query financial transactions by the batch code. Furthermore, the batch code appears on the CSV exports. The batch code does not have to be complete. For example, you could query on something like 2020-12-20, and that will pick up all all batches from that day, such as 2020-12-20-1-CHK, 2020-12-20-2-CRD, etc.

If you’d like to see any or all of these changes in action, have a look at this presentation.

Automated Emails to Contributors

ShalomCloud now creates automated emails to contributors. Well, not only contributors, but also people paying any kind of commitment. And, also, payments made from the ShalomCloud shopping cart.

Some background: originally, ShalomCloud was strictly a back-office utility. Appropriately, it tracked membership, Yahrzeits, and commitments and payments. Primarily, office personnel recorded those payments, most of which arrived via paper check. Also, ShalomCloud offered, and continues to offer, a way to produce acknowledgement letters.

However, as people have become more and more accustomed to making online payments, ShalomCloud has expanded beyond a back-office program. Accordingly, we offer three different windows for payments. There is a pure payment portal (login not required), a logged-in member portal, and a shopping cart. Again, to keep pace with what perhaps has become an expectation in this digital society, we now generate immediate acknowledgements via email, for each of those three windows into ShalomCloud.

Payment Acknowledgement
Payment Acknowledgement

Here is a somewhat verbose video, that, in the end, shows the automated emails to contributors.

One thing more, not shown in the video. You can designate the sender of those emails. By default, the sender will be [email protected] However, after logging into the system, if you go to Home -> Declare synagogue options, you’ll see a place to declare the “Default email from.” We will need to verify that sender email address, just be aware.

Tax Statements by Email

You can now send links to your memberships’ tax statements by email.

For some time, ShalomCloud could send tax statements by printed letter. As with the periodic statements, you can now send links by email to your members. By accessing the link, each member can see, print, or download the tax statement.

There are two “must-have” items for this process. One — the actual tax letter. Two, an email template entitled, specifically, “send_tax_statement_link.” If you already have a “send_statement_link”, you can copy that one, and change it for tax purposes.

Here is a video showing the tax email process in action:

Tax statements by email

Tax Letters by Email
Tax Letters by Email

Recurring Payments

There’s a new feature available in regard to recurring payments.

Previously, there were only two time periods for recurring payments–weekly or monthly. Now, though, you can specify the number of weeks or months between payments.

For example, if you specify a month-type payment, but with an interval of 3, that charge will happen every 3 months.

If you’re unfamiliar with the whole idea of recurring payments, as implemented within ShalomCloud, you’ll likely find this video helpful.

List of payment plans
Payment Plans