Kindoo Access Control System

[jcleona]

Kindoo management option

One additional option for the Kindoo management interface would be an option to display/list all temporary users.
I have been using three leading 000 in the description of each temp user which makes it easier to do a search for temp users, but an option on the site dashboard to list all temp users would be very handy.

For all non-automatically assigned users, we currently put this in description for easy searching:
FLOAT-RECUR <building> <activity> <contact info> -- recurring events like pickleball, employment class
FLOAT-PERM <building> <activity> <contact info> -- permanent users like missionaries
FLOAT-ONCE <building> <activity> <contact info> -- one-time users like for a funeral
FLOAT-GENCONF <building> <activity> <contact info> -- users like accompanists, etc to review every 6 months - maybe general conference

Of course we are new at this, so this might change, but maybe this will be helpful to others.

[ELHawkes]

Resend Email (All)

One more thing that would be handy would be to have a function/button that would resend the invite email to all users that have not yet accepted the invite.
I know you can export the list and then copy all of the email addresses and then use your own personal email to send out additional invites, but it would be much nicer if it was automated within the Kindoo system so it was just a click of a button somewhere in the management interface.
This would give those users several opportunities over a month or two with repeated invites, and then licences could be freed up from those who are not interested in using Kindoo to access the meetinghouse. They would then still be free to request access if they decide they really need access sometime down the road.

[rknelson]

Resend Email (All)

One more thing that would be handy would be to have a function/button that would resend the invite email to all users that have not yet accepted the invite.
I know you can export the list and then copy all of the email addresses and then use your own personal email to send out additional invites, but it would be much nicer if it was automated within the Kindoo system so it was just a click of a button somewhere in the management interface.
This would give those users several opportunities over a month or two with repeated invites, and then licences could be freed up from those who are not interested in using Kindoo to access the meetinghouse. They would then still be free to request access if they decide they really need access sometime down the road.

Click on "Site Dashboard" scroll to the bottom and click on the Green portion of the "Site Invitation" pie chart. It will display all users who have not yet accepted the invite and each has a "Resend Invite" button. Not quite the same as your request, but almost as easy.

[ELHawkes]

Resend Email (All)

One more thing that would be handy would be to have a function/button that would resend the invite email to all users that have not yet accepted the invite.
I know you can export the list and then copy all of the email addresses and then use your own personal email to send out additional invites, but it would be much nicer if it was automated within the Kindoo system so it was just a click of a button somewhere in the management interface.
This would give those users several opportunities over a month or two with repeated invites, and then licences could be freed up from those who are not interested in using Kindoo to access the meetinghouse. They would then still be free to request access if they decide they really need access sometime down the road.

Click on "Site Dashboard" scroll to the bottom and click on the Green portion of the "Site Invitation" pie chart. It will display all users who have not yet accepted the invite and each has a "Resend Invite" button. Not quite the same as your request, but almost as easy.

Correct, that is the other way I would like to avoid.
We currently have 27 users that have not accepted the invite yet after 2 weeks of having Kindoo implemented in our Stake.
That method requires the 1st click to initiate the resend invite, 2nd click to choose if you want to be copied, 3rd click to acknowledge the invite was successfully sent for each user.
That's 81 clicks.
1 button click to Resend All, and maybe one more click to acknowledge are you sure or cancel, would be far simpler.

[ELHawkes]

Account Verification & Users Login Pie Charts in the Site Dashboard

Could someone share a Scenario of how the data in these two pie charts can be useful?

[swigginton]

Account Verification & Users Login Pie Charts in the Site Dashboard

Could someone share a Scenario of how the data in these two pie charts can be useful?

I don't find those 2 charts to be independently useful. They, along with the the Site Invitation chart tell pretty much the same story about who has initially set up Kindoo on their device. I use "Users login" and "Users command" as the guides to determine who will likely use their access privilege and are my source for seeking out unused user licenses. The raw data from the charts can be helpful when troubleshooting for a specific user. Knowing if they accepted the invite, verified their email address, logged in and issued a command can help identify the source of a problem based on which step(s) they completed. Other than that, I don't find much use in those first couple of charts.

[ELHawkes]

Account Verification & Users Login Pie Charts in the Site Dashboard

Could someone share a Scenario of how the data in these two pie charts can be useful?

I don't find those 2 charts to be independently useful. They, along with the the Site Invitation chart tell pretty much the same story about who has initially set up Kindoo on their device. I use "Users login" and "Users command" as the guides to determine who will likely use their access privilege and are my source for seeking out unused user licenses. The raw data from the charts can be helpful when troubleshooting for a specific user. Knowing if they accepted the invite, verified their email address, logged in and issued a command can help identify the source of a problem based on which step(s) they completed. Other than that, I don't find much use in those first couple of charts.

So basically the data from those two pie charts provide a little deeper dive into the efficient management and use of licences, since over all the push seems to be for less people having access in the name of security.
The manager instructions indicate that users can be deleted even if they were added via LCR auto sync, but I have found that not to be true because it's also been said that the FM has to enable that feature for the manager, and even though I have explain And provided links To my FM Regarding enabling that feature My FM cannot find that feature and just says That I shouldn't be requesting access to Sentry, and others on here say I shouldn't worry about deleting users that have been auto synced, and others indicate that we should keep wards a little hungry for licences by limiting the number of licences or we might as well just leave the buildings unlocked if everybody gets access. Others say that those who are making the decisions at the top to implement this system don't necessarily have an interest in the concerns mentioned in this thread. I have been told in this thread that I have an infinity for her previous Sicunet system.
I find this all to be a strange mix of opinions and politics of the business end of this effort. And then Spiritually we are taught to council together to know the correct path to take.
At any rate, I hope that Stake managers can actually manage more efficiently by getting these features implemented.
Being able to directly manage which callings are synced and not synced.
Able to directly deleted users that were added via sync
Able to resend invites to All, not just one at a time.
Able to list all temporary users.
Improve the Bulk add users by being able to specify which access rule each user gets in the CSV file and not be limited to 50 users per CSV file.

[robmerrill]

For the individual talking with FM and the Kindoo CEO, it would be helpful if this app could enable other users 1x access rights. The use case is building cleaning (if ward members are coming to help earlier or later than the overall group) or building lock up.

The Kindoo app has the ability to add "temporary" users. You add the user and set a date/time when the access expires. Seems like that could cover what you are requesting. We use it for family activities, wedding receptions and other one-time use situations.

+1 for this with a slight edit -- if the expiration date automatically releases the seat/license, great. Though if I could then chain another person to take that *same* user seat later (after the expiration date) then this would greatly simplify access/license management.

example: Its Sunday. A backup person asked to check building for security just this week on wednesday night. gets access that expires that night. I schedule this today, and it uses one floating seat/license. someone else asks to come in and setup for an event Saturday morning, early. I "re-assign" this temporary floating seat/license to person B (the saturday setup person) to be able to get access to a certain set of doors on Saturday morning, expiring that day at 5pm.

only one license gets "used" either time *and* I can proactively setup the usage to swap from person A to person B, all done on Sunday before either of these events has happened, ensuring the members have sufficient time to download and register for the app, so that Wednesday night and Saturday morning, they dont need to call me in a panic because they can't get into the building.

This idea is more of a "parking space" than a fixed user license. I am sure this might be technically difficult depending on how Kindoo's system ties together on the back-end, but if there was a way even for a stake or building to have a few floating licenses like this, that would make the system exponentially more flexible.

(seems like this "guest" access enablement would be a pretty fantastic feature for Kindoo, too, in the long-run. I have to think it's a feature they have on their roadmap anyway!)

[ELHawkes]

+1 for this with a slight edit -- if the expiration date automatically releases the seat/license, great. Though if I could then chain another person to take that *same* user seat later (after the expiration date) then this would greatly simplify access/license management.

example: Its Sunday. A backup person asked to check building for security just this week on wednesday night. gets access that expires that night. I schedule this today, and it uses one floating seat/license. someone else asks to come in and setup for an event Saturday morning, early. I "re-assign" this temporary floating seat/license to person B (the saturday setup person) to be able to get access to a certain set of doors on Saturday morning, expiring that day at 5pm.

only one license gets "used" either time *and* I can proactively setup the usage to swap from person A to person B, all done on Sunday before either of these events has happened, ensuring the members have sufficient time to download and register for the app, so that Wednesday night and Saturday morning, they dont need to call me in a panic because they can't get into the building.

This idea is more of a "parking space" than a fixed user license. I am sure this might be technically difficult depending on how Kindoo's system ties together on the back-end, but if there was a way even for a stake or building to have a few floating licenses like this, that would make the system exponentially more flexible.

(seems like this "guest" access enablement would be a pretty fantastic feature for Kindoo, too, in the long-run. I have to think it's a feature they have on their roadmap anyway!)

That's a great Idea.

[ELHawkes]

Things we would like the Stake Manager to be able to do directly

Able to directly edit the names of access doors (forgot to add this one in the previous thread)
Able to directly manage which callings are synced and not synced.
Able to directly deleted users that were added via sync
Able to resend invites to All, not just one at a time.
Able to list all temporary users.
Improve the Bulk add users by being able to specify which access rule each user gets in the CSV file and not be limited to 50 users per CSV file.
"The floating parking space" Licence, as described here. posting.php?mode=reply&t=41853#pr260994