Kindoo - Best Practices & things to avoid

[dbhull1]

Our stake is new to Kindoo and going through implementation pains. I've spoken to individuals in several stake and am finding the some things are just a challenge and I am not hearing much in the way of solutions - folks are trying to figure things out.

I've read comments in other posts that some stakes have developed their own guides (I assume for specific procedures). I would love to know if anyone has developed or can share feedback on:

1) Best practices - including processes for handling temp. license requests, building lockup, emergency requests requiring someone to meet the requester at the building, pushing management to the ward level, etc...
2) Things to avoid - practices/procedures that just don't work well; situations you found yourself in that were painful and you've found a way to avoid now.

Thanks!

[swigginton]

I would love to know if anyone has developed or can share feedback on:
1) Best practices - including processes for handling temp. license requests, building lockup, emergency requests requiring someone to meet the requester at the building, pushing management to the ward level, etc...
2) Things to avoid - practices/procedures that just don't work well; situations you found yourself in that were painful and you've found a way to avoid now.

I’ve worked with several stakes in their Kindoo installations. Here are common things I see.
Temp Licenses - there are a few different types:

• Private events (wedding receptions, etc.) - If these are infrequent, the meetinghouse scheduler forwards the temp access request to the stake Kindoo manager. If they get a lot of requests, the meetinghouse scheduler can be added as a Kindoo manager to enter those. That’s what we do in our stake. We have 4 buildings and 2 schedulers. Those schedulers only add temporary users for their buildings. They don't add any permanent users.
• For lockup/security, wards in the meetinghouse typically rotate responsibility on a monthly basis and have 1 or 2 people who do the nightly checks. They are added as permanent Kindoo users.
• For emergency requests (extremely rare), they can be given temp access by the Kindoo manager on the fly. Access approval should be given by someone with proper authority. Kindoo managers don’t provide access without that request coming through proper channels.

For callings not automatically synchronized with Sentry, requests are sent from the bishoprics or stake presidency to the stake Kindoo manager. We require the request to include, name, email address, calling and the name of the person being released.
Pushing Kindoo management to the ward level is not recommended. Kindoo is configured by stake. Anyone with manager rights has access to all users for the stake, so not a good idea to give that to wards.
You didn’t mention it, but full-time missionaries should only be added using their area email address. That email address is linked to their service area. By doing that, you don’t need to change users in Kindoo at transfer time. The incoming missionaries simply log into Kindoo using the area email address and the license is transferred to the new phone.
I hope that helps. We have other specific training we give to stake Kindoo managers, but the info above is generic to the stake as a whole.

[MurdockM]

"Church Access Automation" keeps changing access permissions given to a Bishop by a human.

1) In my stake the Bishops travel to (a different from their own meeting house) Stake Center for PPIs with the Stake President.

Tonight is the 3rd month now that my wards Bishop has discovered his access to the Stake Center revoked, apparently by "Church Access Automation". So far he has texted me (Ward Clerk) and I've gone in, (while he waits outside the Stake Center Door), and re-assign him access to the Stake Center door.


2) My ward also has a few Kindoo entries that I set up when it was first rolled out, and now those people have been released however the system won't let me remove them. I see that "Church Access Automation" has taken over the entries I entered and that's why I can't remove those users. Thus, "seats" are unnecessarily being used by people who have been released and can't be removed from Kindoo!

3) And, "Church Access Automation" has added a <ward> (Relief Society President) calling with a weird and not valid email address. So another "seat" unnecessarily used up there as well.

How can these issues be fixed? Kindoo seems like a good system and automatic sync sounds like a good idea.

Best Practices?
Is there a syntax that the 'system' understands, so that when callings are entered by a human the auto-sync will correctly update that calling in the future?
Do we delete our manually entered callings, and let the system automatically reenter them over night?