Accessing CNM & CDOL

[natet]

I want to figure out who to reach out to about extending access to CNM to ward tech specialists. With the move to Kindoo, our stake moved several of our STS' to WTS to save on the number of kindoo licenses being assigned at the stake level. We had 7 or 8 STS' at the time, and they cut it down to 4, and now the ones who were moved can't manage the Lehi network or use CNM to troubleshoot and resolve connectivity issues.

You cannot. Like most things in the church, CNM assess is based on calling, not someone granting rights to them.

I assumed that was the case. I want them to add Ward Technology Specialist to the list of callings that can access CNM. I sent an email to MHT and they said they would forward my request to the network team. I'll update on what I hear back from them.

[russellhltn]

I assumed that was the case. I want them to add Ward Technology Specialist to the list of callings that can access CNM. I sent an email to MHT and they said they would forward my request to the network team. I'll update on what I hear back from them.

But keep in mind that whatever change they do would be global to the whole church. Since many meetinghouses are shared between wards, that can create conflict. I've always interpreted it as the network (along with the ward computer) is a stake responsibility, even if only one ward uses it.

Your request might have a better chance if you could explain what limited (preferably read-only) access the WTS would need to do their job.

You might have better luck working with the Kindoo people to find another way to limit the number of licenses used.

[natet]

I assumed that was the case. I want them to add Ward Technology Specialist to the list of callings that can access CNM. I sent an email to MHT and they said they would forward my request to the network team. I'll update on what I hear back from them.

But keep in mind that whatever change they do would be global to the whole church. Since many meetinghouses are shared between wards, that can create conflict. I've always interpreted it as the network (along with the ward computer) is a stake responsibility, even if only one ward uses it.

Your request might have a better chance if you could explain what limited (preferably read-only) access the WTS would need to do their job.

You might have better luck working with the Kindoo people to find another way to limit the number of licenses used.

Based on the document linked earlier, individual ward access is already granted via Bishops and Ward Clerks. I'm just asking to extend that a bit, but I can understand if they reject my request. You never know until you ask. The problem with Kindoo licenses is that has a cost associated with it. I'm also not sure how granular their control of licenses is. Can we just request a few extra licenses for our stake, or is that something that ends up having broader implications? CNM seemed like the path of least resistance to me.

[russellhltn]

The problem with Kindoo licenses is that has a cost associated with it. I'm also not sure how granular their control of licenses is. Can we just request a few extra licenses for our stake, or is that something that ends up having broader implications? CNM seemed like the path of least resistance to me.

As long as the STS calling isn't "hard coded" for access, they could remove that calling and just add the individuals who need access.

If that's possible, then that can be done in the next day or two. Any change to "the system" is likely to take months as it goes though all kinds of reviews and finally gets added to the developer's tasks when CNM's turn comes for updates.

[natet]

The problem with Kindoo licenses is that has a cost associated with it. I'm also not sure how granular their control of licenses is. Can we just request a few extra licenses for our stake, or is that something that ends up having broader implications? CNM seemed like the path of least resistance to me.

As long as the STS calling isn't "hard coded" for access, they could remove that calling and just add the individuals who need access.

I tried to edit my post, but it ended up losing my edits. I misread your earlier suggestion, but this is the gist of what I wrote once I realized that. Yeah, I don't know how easy it is for them to manage the ward level entries. The reason they made the switch was so that the allocations for the 3 that didn't need all building access could get their license from the ward allocation and not the stakes, and it means managing 7 individual accesses instead of 2 groups access. Having not seen the Kindoo management interface, I don't know how painful that is. Personally, I feel that if you are already going to grant the Ward Clerk access to CNM, it makes sense that your WTS would have access. At least in our stake, the WTS is just as likely to need access to network resources as the ward clerk if not more so. But I get it. I'm asking for something that can have broad implications vs some localized pain for our Kindoo admin in our stake. Frankly, if its localized pain, I'll end up just managing all the building Lehi passwords myself.

[russellhltn]

The instructions I'm reading says the licenses are assigned to the stake. How the stake wants to allocate them it up to them. So, the whole ward vs. stake license is just how the stake is slicing the pie.

You might want to look at this page: Stake Kindoo Manager Instructions. Start with the section "Synchronized Callings".

[swigginton]

The problem with Kindoo licenses is that has a cost associated with it. I'm also not sure how granular their control of licenses is. Can we just request a few extra licenses for our stake, or is that something that ends up having broader implications? CNM seemed like the path of least resistance to me.

The issue is your FM manager has enabled Sentry to synchronize STS callings in KIndoo. That means anyone with that calling will automatically have Kindoo access. The stake president may have requested that, not realizing how many you have, so they moved some to WTS to free up licenses. Adding WTS to CNM probably won't happen, since it gives too much access to stake-level functions. A better solution would be to have your stake Kindoo manager or stake president notify the FM manager to turn off Sentry sync for STS callings. That's very easy to do. You can then move the appropriate WTS back to STS. Then, your stake Kindoo manager can manually grant Kindoo access to only those STS who actually need it.

[natet]

For those interested, the message I got back from MHT is that the product manager for CNM has granting Ward Techs access to CNM "high on their list".