Blog

Version 4.1.4 – Security Change and MORE Spotify Updates

WP Logo - Version 4.1.4

We hope you have been enjoying the new Spotify integration with WP!  It truly is a powerful tool that gives you and your team free and instant access to streaming audio for many of your worship songs, without having to upload anything!  If you haven’t tried Spotify, what are you waiting for?  Learn more and create yourself a free account now! Just browse to Spotify.com.

With version 4.1.4 we’ve added even more awesome Spotify features that you will no doubt find indispensable.  We’ve also made a very important security change regarding Helpers on Worship Flow Sensitive teams, so please be sure to read on.

More Spotify Integration

In just two weeks, we’ve taken access to Spotify songs to the next level in WP with Spotify Playlists and Spotify Searches.  On the Worship Flow page (for both Planners and Helpers), we’ve added a Spotify Icon Play Spotify Playlist link that will open your Spotify app and load your service’s worship songs (that have Spotify links) in a playlist.  Access to the audio of your worship set list has never been easier…or free-er!

But wait, I know what you are thinking.  “That’s great if I have the Spotify links.  But I don’t, and it is kind of a pain to search Spotify for those songs to manually copy the Spotify link to my songs library.”  Well, you will be thrilled to hear that we’ve made searching Spotify songs super easy!

Right in the Add/Edit Song window where you would normall see the Spotify URI/id field (on the Web tab), you can click the binoculars icon and “Find Spotify Track” window will open with a list of matching songs.

Spotify search window

With that list of Spotify search results, simply click the Title you’d like to link to the song you are adding/editing.  If you want to hear the song first, just click the little blue “Play” icon and your Spotify app should start playing the song.

Once you’ve selected the song, you’ll see the Spotify URI/id field is now populated.  Be sure to save your changes!

Important Helper Security Change

With version 4.1.4, an important security change on WorshipPlanning.com has taken place and some of your Helper accounts could be affected.  The change puts in to effect the “Worship Flow Sensitive” setting for each of your teams.  For Helpers to see the worship flow related information (worship flow, service files, virtual stage, and printouts), they must be serving on a team that has the “Worship Flow Sensitive” setting enabled.  If they are not, when they go to the worship flow related tabs in MyWP, they will see a message explaining why they can’t see the information there.

For smaller churches that don’t use the team features of WP, we are providing a small loophole.  If a Helper is not a member of any team, he or she will still have access to worship flow related info.

To adjust this setting for a team, log in to WP and follow these steps:

  1. Go to People >> Teams
  2. Click on the name of the desired team that needs setting to be worship flow sensitive
  3. Click on the “Settings” tab
  4. Click the “Edit these Settings”
  5. Change the “Worship Flow Sensitive:” setting to be Yes and click the “Save” button.

teams-worship flow sensitive.png

The reason for this policy change is due to the fact that many churches are using WP to plan many of their Sunday morning ministries that aren’t directly related to the worship service flow (i.e. children’s ministry, parking team, coffee setup).  Many churches have asked us to restrict those teams from accessing information not relevant to their ministry.  Since we’ve had the “Worship Flow Sensitive” team setting in place for a while, hopefully your team is already configured properly.  We are just now finally putting it into use.

If you have any questions or feedback about this change, please feel free to post a comment below.  If you have technical support issues, please be sure to submit a support request.

Spotify is the registered trade mark of the Spotify Group.

Leave a Reply

Your email address will not be published. Required fields are marked *