Kindoo Access Control System

[mmacconnell]

Hello. I am looking for the approved callings list but am getting a message "The requested URL was not found on this server.", however just last week it was there on https://www.churchofjesuschrist.org/too ... w?lang=eng. Does anyone know why that message is popping up on any of the links I click?

My question is the article implies that integration has been done now to automatically assign access based on callings. How does the transition work for those of us that have had to manually update access? When will they be transitioned, and will we get instructions and/or notification of this change?

[GMMHero]

Hello. I was planning to ask the same questions about how to automatically assign access based on callings, once I became a touch more familiar as I am still new. How does the transition work for those of us that have had to manually update access? When will they be transitioned, and will we get instructions and/or notification of this change?

I am hoping there is a way to give permanent names to some and then change users or like "floating access" that can be assigned to members on an as needed basis, such as organist needing to practice or activity day set up. I still need to also research more about the user types. In my mind ideally, some have permanent access and then units have a few "floaters" that are for others to use when needed.

[waymana]

The automatic calling synchronization is turned on individually by Stake by the Facilities Manager. Your stake will be notified by your Facilities Manager before this synchronization takes place. Functionality is being tested now for the FM to customize a list of 110 standard callings for a stake that will receive automatic building access. When a calling is enabled, it applies to all relevant units within the stake. For example, enabling “Relief Society President” will automatically assign licenses to everyone with that calling in all wards and branches. This is not customizable by ward. If multiple individuals hold the same calling in a unit, each will receive a license. Access is automatically assigned and revoked based on calling changes in LCR. All other callings must be managed manually in Kindoo by the Kindoo Manager.

For existing Kindoo sites, when the synchronization is initially turned on the system will check to see if individuals on the list already have access and update their records. Any current users that are not on the default calling list will still have access. So there is a risk that a stake may use up the remaining licenses if too many callings are selected.

If you have questions or want to help us test this functionality please reach out to your Facilities Manager.

[greenwoodkl]

If multiple individuals hold the same calling in a unit, each will receive a license. Access is automatically assigned and revoked based on calling changes in LCR. So there is a risk that a stake may use up the remaining licenses if too many callings are selected.

I am in the process of requesting new electronic key fobs for our ward. I was told by our FM Facilities Coordinator/Admin Assistant that Kindoo is likely to be coming soon for our FM group. I was counseled to prepare our Ward Council that some leaders who currently have fobs could likely lose access in the future with more limited licenses and user seats. The FM admin didn't have more details at this time.

I did find the Kindoo pages on the Tech Wiki. I'm encouraged by the discussion of automatic calling synchronization. Some of my questions were addressed in the quote above. Namely, what is done when we have multiple members holding the same calling. Would only one of them get a license and the others have to coordinate with them? A lingering question is whether wards could use ward budget funds via transfer to obtain additional licenses or user seats? It feels like the standard callings that allow multiple individuals could quickly use up a quota of licenses. An unsuspecting or untrained clerk could cause trouble by adding callings in LCR. 20 licenses per ward go quickly - nearly half to a fully-staffed Bishopric leaves very few for organizations.

Some of the callings that currently have fobs in our ward that I can't find on the wiki list include youth advisers and materials center (library) specialists

[waymana]

If multiple individuals hold the same calling in a unit, each will receive a license. Access is automatically assigned and revoked based on calling changes in LCR. So there is a risk that a stake may use up the remaining licenses if too many callings are selected.

I am in the process of requesting new electronic key fobs for our ward. I was told by our FM Facilities Coordinator/Admin Assistant that Kindoo is likely to be coming soon for our FM group. I was counseled to prepare our Ward Council that some leaders who currently have fobs could likely lose access in the future with more limited licenses and user seats. The FM admin didn't have more details at this time.
I did find the Kindoo pages on the Tech Wiki. I'm encouraged by the discussion of automatic calling synchronization. Some of my questions were addressed in the quote above. Namely, what is done when we have multiple members holding the same calling. Would only one of them get a license and the others have to coordinate with them? A lingering question is whether wards could use ward budget funds via transfer to obtain additional licenses or user seats? It feels like the standard callings that allow multiple individuals could quickly use up a quota of licenses. An unsuspecting or untrained clerk could cause trouble by adding callings in LCR. 20 licenses per ward go quickly - nearly half to a fully-staffed Bishopric leaves very few for organizations.

Some of the callings that currently have fobs in our ward that I can't find on the wiki list include youth advisers and materials center (library) specialists

Thank you for your questions.
Kindoo devices are being installed to improve the security of our buildings. Currently, with the fob system it is more difficult to track who has the fobs and they are easy to lose. With Kindoo you will be able to track who has access to the buildings and a stake Kindoo manager will be able to grant temporary access to individuals that are not part of the callings that are automatically synchronized from the available pool of licenses. The initial set of licenses allocated to a stake is meant to be a reset to the security of the buildings. Using the initial set of licenses for a few months and you can then review access logs and see who is or isn't accessing the buildings and request additional licenses. Just because someone currently has a fob doesn't mean that they need to have regular access going forward. Often if members only access the building on Sunday, after one person is in the building the exterior doors are unlocked. If someone only needs to open the building once every few months for an event or ward cleaning a stake Kindoo manager can grant them access temporarily when needed. The licenses are paid for out of the FM group budget and not from the ward budget. Once Kindoo licenses are purchased and associated with a stake, they are permanent and cannot be returned. As the licenses are permanent, we just want to be cautious of purchasing too many that won't be used.

If your stake received initially 170 licenses, you would want to make sure that the callings that needed access the most would be synchronized and that there are around 20 left over to grant temporary access as needed. This might mean initially that the Stake President decides to not include some callings that could have many people assigned such as technology specialists or assistant clerks and to have those individuals be granted access manually. All individuals that are in a calling that can be assigned to multiple people will receive access if that calling is enabled. Current functionality also is that the calling list is set at a stake level for all stake and ward callings by the FM in a Church system and is not customizable at a ward level. So it may be best to limit the amount of callings that are synchronized at first before adding additional.
Not all callings are available for synchronization right now. Other callings such as youth advisers and materials center (library) specialists maybe added in the future.

Let me know if you have additional questions. You can also see these two articles on the TechWiki that have more information and let us know if there is anything we can clarify.
https://tech.churchofjesuschrist.org/wi ... structions
https://tech.churchofjesuschrist.org/wi ... ndooAccess

[BrianEdwards]

One aspect I couldn't quite follow was the relationship between automatic calling access, and the percentage of buildings in a stake with Kindoo access. My assumption is that for many stakes, only one or two buildings have Kindoo access and the others remain normal key usage. But perhaps when a stake gets Kindoo access it's installed in every building throughout the stake (and if that's the case, I think the Wiki could benefit from including that clarification).

So under my assumption (which may not be correct) -- if for example a stake has 10 buildings and only one (the stake center used by only one ward) has Kindoo enabled, wouldn't granting automatic calling access to something like "Bishop" end up consuming 10 user seats for Bishops, and 9 of those user seats would be for Bishops that wouldn't ever use Kindoo in their buildings?

I'm just thinking that automatic calling access might lead to the overall pool of licenses, having a large portion taken up by members who will never use Kindoo because their buildings don't have it installed. But again, I may not have correctly understood how this is implemented, so hopefully somebody can set me straight.

[mmacconnell]

Our Stake has it installed at every building. They started first by installing Kindoo but keeping the key access to allow leaders to get used to the system. The FM group just completed this week rekeying all the outside doors at the last two building, so no Kindoo is the only form of access to allow leaders of our buildings. There is one door with a key, but that is stored in a special box for the fire department to gain access.

[BrianEdwards]

Our Stake has it installed at every building. They started first by installing Kindoo but keeping the key access to allow leaders to get used to the system. The FM group just completed this week rekeying all the outside doors at the last two building, so no Kindoo is the only form of access to allow leaders of our buildings. There is one door with a key, but that is stored in a special box for the fire department to gain access.

Automatic calling access makes sense for situations like yours. I just wasn't sure if this was standard practice everywhere, or if there are stakes out there with partial Kindoo coverage, where they would want to take that into account when deciding what callings should have automatic access enabled.

[swigginton]

I have been installing Kindoo and training stake leaders and Kindoo managers, so I’m very familiar with its functionality. The rollout has been extremely successful in the FM groups I’ve worked with. I’m wondering why the responsibility is placed on the FM managers to determine which callings get synchronized for a stake. It would seem more appropriate for the stake to make that determination, since they have greater visibility to the actual use of their buildings. Can you clarify why that was determined?
Also, is it possible to override the synchronization? For example, in most wards, an organization leader may need access, but in other wards, that same leader position may not. In those cases, the stake Kindoo manager would typically pull the unused license and allocate it elsewhere. This might also resolve the earlier question about Kindoo only being in some of the stake buildings.

[greenwoodkl]

Some comments and further questions:

It seems that Kindoo will rely on a proactive and responsive stake manager, or the experience could quickly degrade for the members. Especially if or when temporary access is relied upon more heavily than expanding licenses. Have stakes who already use the system tied the Kindoo manager assignment to particular callings, such as building scheduler, stake building rep, or high councilor?

It also seems that there is an assumption that building usage patterns are or should be driven primarily by calling responsibilities. I have a feeling individual agency coupled with delegation and unique cultures of wards and organization presidencies will introduce variability. I could imagine some members who prefer to do all their building specific work on Sunday (less need for Kindoo) and others who prefer to come in during the week. So the building access technology with associated costs could start driving behavior more than the flexibility and agency of today.

Does the automatic synchronization only apply to licenses? I hope the schedules can be applied differently to each user or ward? Thinking through situations such as how wards have different assigned weeknights for youth activities, or how Valiant Activity Leaders may have different meeting times for boys vs girls. We currently have Building Reps for cleaning that only need Saturday daytime and other building reps for security that need night access.