Users/Roles – TouchPoint Software

New Setting to Hide Member Status for My Data Users

We have recently added a new setting that will prevent a My Data user from seeing the specific Badge displaying his Member Status as well as the Member Status that normally displays in the list of Family Members.

See the image below for the places a My Data user would normally see the Member Status. These will be removed if you add the Setting named HideMyDataMemberBadge = true.

This new Setting goes hand-in-hand with another Setting that will hide the Profile tab for a My Data user. You would probably want to also use that Setting in conjunction with this new Setting. It is named HideMemberStatusFromMyData = true.

Thank you to our friends at Cokesbury UMC in Knoxville, TN for sponsoring this new Setting.

New User Role: FinanceViewOnly

This new role is designed for staff who need to view summary reports for contributions, but not perform data entry or view contribution data for any individuals. You assign this role – FinanceViewOnly – without the Finance role as that will override the ViewOnly role. This will simplify the view for your church staff members that do not need (or want) all the other options that are available for someone with the normal Finance role. With this role, they will just see those reports. This will also allow you to give this role to staff members who previously have not been able to access financial reports because it was not appropriate for them to have full finance capabilities.

This is perfect for a minister that needs to see the income/contributions for various funds but does not need to see individual contributions.

This is the list of reports this user will see.These are under Administration in the main menu.

Read more…about the roles related to Finance/Contributions.

October 19, 2017/0 Comments/by Steele Billings

SQL Reports, Users/Roles

New SQL Recipe – User Roles Report

If you have ever wanted run a report for people in a specific Organization, or a Tag, or Search Builder results and see of all those that are TouchPoint users and see their roles, then you will be very happy about this new report.

This is one of those “Recipes” we’ve told you about before. That means that we wrote the SQL code for you and all you need to do is copy and paste it into your database. Of course this must be done by the System Admin user. However, once it is created and added to the blue Toolbar, any user with Edit role can run the report.

Best Practices-Managing User Accounts

Every church has a certain amount of turnover, whether it is staff members, seasonal interns, or even lay leaders. So, the questions become these:

What do you do as the System Admin when someone leaves their position?
What should you do as a staff user before a new user account can be created for your new hire?

We get questions about this (and more) from time to time, so we created a help article to offer some advice in this regard. We have a sample email you might want to use as a guide to create an email draft. Then you can send that additional email to new staff members (apart from the New User Welcome). You can give them basic information a staff member needs to know about TouchPoint, links to some help articles that pertain specifically to their jobs, and what ever you think they need to know.

The article outlines the information a staff member needs to provide to the Admin user when 1) you need a new user account created, or 2) when one of your staff members is leaving.

New Options for Editing “Campus”

The default requirement for editing the Campus selection on someone’s people record is for the user to have Access and Edit roles. However, we have just added a new user role with an accompanying Setting and another new Setting – all of which relate to which users can edit the Campus on a person’s record.

If you add this new role named EditCampus to your database and the Setting EnforceEditCampusRole = true, only a user with the role EditCampus can edit a person’s Campus.

If you add the Setting MyDataCanEditCampus = true a MyData user (and any other user) can edit his own Campus.

So, you have some options:

If you like the user roles as they are currently, do not do anything.
If you want users (My Data included) to be able to change the Campus on their own records, add the Setting MyDataCanEditCampus = true.
If you do not want all users with Edit role to be able to change the Campus on other people’s records, then add the user role EditCampus to your database and assign it to those few users that you want to be able perform this function. Then add the Setting EnforceEditCampusRole = true.
If you want people to edit their own Campus settings and you want to limit which staff can edit someone else’s Campus settings, then add both the new Role and both Settings.

Thank you to Redeemer Presbyterian Church in New York City for sponsoring these projects.

New Setting to Hide Member Status for My Data Users

New User Role: FinanceViewOnly

New SQL Recipe – User Roles Report

Best Practices-Managing User Accounts

New Options for Editing “Campus”

RESOURCES

Documentation

Blog

Newsletter

CONNECT

Facebook

Twitter

YouTube

CONTACT SALES

1-888-788-6348

Email Sales

RESOURCES

CONNECT

CONTACT SALES

Cookie and Privacy Settings