StakeKindooManagerInstructions - Revision history

Button23r: /* Difference Between Temporary User Dates and Access Rights Dates */

2025-12-17T23:42:47Z

Difference Between Temporary User Dates and Access Rights Dates

← Older revision		Revision as of 23:42, 17 December 2025
Line 246:		Line 246:
	See the general handbook for guidelines on who can be given access to meetinghouses. https://www.churchofjesuschrist.org/study/manual/general-handbook/35?lang=eng&id=title27#title27		See the general handbook for guidelines on who can be given access to meetinghouses. https://www.churchofjesuschrist.org/study/manual/general-handbook/35?lang=eng&id=title27#title27

	==== ~~'''~~Difference Between Temporary User Dates and Access Rights Dates~~'''~~ ====		==== Difference Between Temporary User Dates and Access Rights Dates ====
	'''Temporary User Dates'''		'''Temporary User Dates'''

Button23r: /* Difference Between Temporary User Dates and Access Rights Dates */

2025-12-17T23:42:16Z

Difference Between Temporary User Dates and Access Rights Dates

← Older revision		Revision as of 23:42, 17 December 2025
Line 249:		Line 249:
	'''Temporary User Dates'''		'''Temporary User Dates'''

	A temporary ~~user’s~~ access rights ~~are only active~~ during the defined date range.		A temporary user takes up a user seat or user license as soon as the user is created until that user is removed from the Kindoo system, however, the user only has access rights during the defined date range.

	* Before the temporary user activation date, the user exists on the site (because they were invited), but has no access.		* Before the temporary user activation date, the user exists on the site (because they were invited), but has no access.

Waymana: /* Further Troubleshooting */

2025-12-13T00:26:14Z

Further Troubleshooting

← Older revision		Revision as of 00:26, 13 December 2025
Line 200:		Line 200:
	===== Further Troubleshooting =====		===== Further Troubleshooting =====
	See the [[KindooTroubleshooting\|Kindoo Troubleshooting page]].		See the [[KindooTroubleshooting\|Kindoo Troubleshooting page]].

			If you need further support please contact the Global Services Department or submit a FIR.

	=== Frequently Asked Questions ===		=== Frequently Asked Questions ===

Waymana: /* Who can be given Kindoo access? */

2025-12-12T23:58:41Z

Who can be given Kindoo access?

@@ Line 243: / Line 243: @@
 ==== Who can be given Kindoo access? ====
 See the general handbook for guidelines on who can be given access to meetinghouses. https://www.churchofjesuschrist.org/study/manual/general-handbook/35?lang=eng&id=title27#title27
 === Kindoo Terminology  ===

Waymana at 04:49, 13 November 2025

2025-11-13T04:49:26Z

← Older revision		Revision as of 04:49, 13 November 2025
Line 10:		Line 10:

	=== Stake Kindoo Manager Responsibilities ===		=== Stake Kindoo Manager Responsibilities ===
	The stake Kindoo manager is the stake building representative or another individual that the stake president assigns such as a stake clerk or stake technology specialist. He or she will manage building access for the stake in the Kindoo application. Additional individuals can be assigned as a manager in the Kindoo system. ~~As the licenses are controlled at the stake level, it is recommended that there be no more than one or two managers per stake.~~		The stake Kindoo manager is the stake building representative or another individual that the stake president assigns such as a stake clerk, building scheduler or stake technology specialist. He or she will manage building access for the stake in the Kindoo application. Additional individuals can be assigned as a manager in the Kindoo system.

	~~Because the number of available user seats is only viewable at~~ the stake ~~level~~ in the Kindoo application it is recommended that Kindoo be managed at the stake level. The stake Kindoo manager could have a backup and stake building schedulers could be given the assignment of granting temporary access. Having multiple managers makes it challenging to manage the licenses and across the stake. Each additional manager should know how many user seats they can use to grant temporary access and the individuals they have assigned to those seats. For example, if a stake only had 10 extra user seats and it had five wards, the stake Kindoo manager could inform the other managers that they only have two extra users seats available to use for guests.		As managers can grant or remove anyone in the stake in the Kindoo application it is recommended that Kindoo be managed at the stake level. Other managers should be supervised by the stake Kindoo manager. The stake Kindoo manager could have a backup and stake building schedulers could be given the assignment of granting temporary access. Having multiple managers makes it challenging to manage the licenses and across the stake. Each additional manager should know how many user seats they can use to grant temporary access and the individuals they have assigned to those seats. For example, if a stake only had 10 extra user seats and it had five wards, the stake Kindoo manager could inform the other managers that they only have two extra users seats available to use for guests.

	Instructions on granting user access as well as details about who ~~will be receiving~~ automatic access can be found below.		Instructions on granting user access as well as details about who receives automatic access can be found below.

	==== How does Kindoo access work? ====		==== How does Kindoo access work? ====

Waymana: Update to licenses allocation.

2025-11-13T03:33:41Z

Update to licenses allocation.

← Older revision		Revision as of 03:33, 13 November 2025
Line 23:		Line 23:
	Only one person (email address) can be assigned to a user seat at a time. Once the user seat is assigned, it is reserved until it is revoked or expires (for temporary users). For example, if a stake had a total of 100 user seats and 90 were assigned, the Kindoo managers would have 10 user seats available to use to grant temporary guest access. If six user seats are assigned on Monday for use on a Saturday morning. Only 4 user seats would be available until those assigned user seats expire.		Only one person (email address) can be assigned to a user seat at a time. Once the user seat is assigned, it is reserved until it is revoked or expires (for temporary users). For example, if a stake had a total of 100 user seats and 90 were assigned, the Kindoo managers would have 10 user seats available to use to grant temporary guest access. If six user seats are assigned on Monday for use on a Saturday morning. Only 4 user seats would be available until those assigned user seats expire.

	User seats are purchased by the FM group. Each stake starts with an initial allocation of ~~50 user seats for~~ the stake ~~and then 20~~ for ~~each ward or branch. For example, if a stake had six wards they would start with 170 seats~~. All user seats are assigned at the stake level~~. Licenses are restricted to ensure that the buildings are secure and access is tracked~~. Additional user seats ~~should only~~ be requested by the stake president to the FM. As user seats are permanent and cannot be refunded, they should be added only when necessary. Before requesting more ~~seats~~, ~~the stake should use the current number of seats for a few months~~ and ~~then review logs to determine if there are any~~ users that ~~are~~ not ~~using their license~~.		User seats are purchased by the FM group. Each stake starts with an initial allocation based on the number of wards or branches in a stake and the callings the stake president approves for access. All user seats are assigned at the stake level. Additional user seats may be requested by the stake president to the FM. As user seats are permanent and cannot be refunded, they should be added only when necessary. Before requesting more licenses, review dashboards and remove users that do not need access.

	A Kindoo account can only be used on one device at a time. Members should not share their password with others so that they can access church buildings. Access should be requested through the stake Kindoo manager(s). If a member’s account consistently switches between devices, their access may be revoked.		A Kindoo account can only be used on one device at a time. Members should not share their password with others so that they can access church buildings. Access should be requested through the stake Kindoo manager(s). If a member’s account consistently switches between devices, their access may be revoked.
Line 33:		Line 33:
	Kindoo can be synchronized with member calling data based on information in Leader and Clerk Resources (LCR). As callings are updated in LCR, members will gain or lose access to Kindoo automatically for the buildings they are assigned. When a calling is enabled, it applies to all relevant units within the stake. For example, enabling “Technology Specialist” will automatically assign licenses to everyone with that calling in all wards and branches. Members with stake callings receive access to all buildings in the stake. Ward callings receive access to only the buildings they are assigned. Synchronized callings can receive either “Always” (24/7 access usually given to the stake presidency and bishoprics) or “Limited daily” (5AM-11PM access).		Kindoo can be synchronized with member calling data based on information in Leader and Clerk Resources (LCR). As callings are updated in LCR, members will gain or lose access to Kindoo automatically for the buildings they are assigned. When a calling is enabled, it applies to all relevant units within the stake. For example, enabling “Technology Specialist” will automatically assign licenses to everyone with that calling in all wards and branches. Members with stake callings receive access to all buildings in the stake. Ward callings receive access to only the buildings they are assigned. Synchronized callings can receive either “Always” (24/7 access usually given to the stake presidency and bishoprics) or “Limited daily” (5AM-11PM access).

	~~As there is a limit on licenses, the~~ stake president determines which callings should receive [[CallingswithAutomaticKindooAccess\|automatic access]] for their stake. They provide the list to the Facilities Manager who updates the list of callings in a separate Church application. Before the calling synchronization is turned on the FM can provide a report of the members that will receive access. Callings are enabled across all units in the stake and cannot be customized to individual units. If the stake does not want all individuals with a calling to have access, do not enable that calling and grant access manually. The stake can also choose to synchronize access with a calling and then afterwards remove the access for a specific individual.		The stake president determines which callings should receive [[CallingswithAutomaticKindooAccess\|automatic access]] for their stake. They provide the list to the Facilities Manager who updates the list of callings in a separate Church application. Before the calling synchronization is turned on the FM can provide a report of the members that will receive access. Callings are enabled across all units in the stake and cannot be customized to individual units. If the stake does not want all individuals with a calling to have access, do not enable that calling and grant access manually. The stake can also choose to synchronize access with a calling and then afterwards remove the access for a specific individual.

	If the stake does not synchronize callings with LCR, access will need to be managed manually for all members in the Kindoo application.		If the stake does not synchronize callings with LCR, access will need to be managed manually for all members in the Kindoo application.

Waymana at 02:36, 4 November 2025

2025-11-04T02:36:03Z

← Older revision		Revision as of 02:36, 4 November 2025
Line 240:		Line 240:
	==== How do I setup sports groups that only need access certain days of the week? ====		==== How do I setup sports groups that only need access certain days of the week? ====
	If an individual is assigned a user seat they will take up a user seat even if they only use the building part of the week. They could be assigned a standard access rule such as limited daily access or they could be assigned a custom access rule.		If an individual is assigned a user seat they will take up a user seat even if they only use the building part of the week. They could be assigned a standard access rule such as limited daily access or they could be assigned a custom access rule.

			==== Who can be given Kindoo access? ====
			See the general handbook for guidelines on who can be given access to meetinghouses. https://www.churchofjesuschrist.org/study/manual/general-handbook/35?lang=eng&id=title27#title27

	=== Kindoo Terminology  ===		=== Kindoo Terminology  ===

Waymana at 02:31, 4 November 2025

2025-11-04T02:31:48Z

← Older revision		Revision as of 02:31, 4 November 2025
Line 33:		Line 33:
	Kindoo can be synchronized with member calling data based on information in Leader and Clerk Resources (LCR). As callings are updated in LCR, members will gain or lose access to Kindoo automatically for the buildings they are assigned. When a calling is enabled, it applies to all relevant units within the stake. For example, enabling “Technology Specialist” will automatically assign licenses to everyone with that calling in all wards and branches. Members with stake callings receive access to all buildings in the stake. Ward callings receive access to only the buildings they are assigned. Synchronized callings can receive either “Always” (24/7 access usually given to the stake presidency and bishoprics) or “Limited daily” (5AM-11PM access).		Kindoo can be synchronized with member calling data based on information in Leader and Clerk Resources (LCR). As callings are updated in LCR, members will gain or lose access to Kindoo automatically for the buildings they are assigned. When a calling is enabled, it applies to all relevant units within the stake. For example, enabling “Technology Specialist” will automatically assign licenses to everyone with that calling in all wards and branches. Members with stake callings receive access to all buildings in the stake. Ward callings receive access to only the buildings they are assigned. Synchronized callings can receive either “Always” (24/7 access usually given to the stake presidency and bishoprics) or “Limited daily” (5AM-11PM access).

	As there is a limit on licenses, the stake president determines which callings should receive [[CallingswithAutomaticKindooAccess\|automatic access]] for their stake. They provide the list to the Facilities Manager who updates the list of callings in a separate Church application. Before the calling synchronization is turned on the FM can provide a report of the members that will receive access.		As there is a limit on licenses, the stake president determines which callings should receive [[CallingswithAutomaticKindooAccess\|automatic access]] for their stake. They provide the list to the Facilities Manager who updates the list of callings in a separate Church application. Before the calling synchronization is turned on the FM can provide a report of the members that will receive access. Callings are enabled across all units in the stake and cannot be customized to individual units. If the stake does not want all individuals with a calling to have access, do not enable that calling and grant access manually. The stake can also choose to synchronize access with a calling and then afterwards remove the access for a specific individual.

	If the stake does not synchronize callings with LCR, access will need to be managed manually for all members in the Kindoo application.		If the stake does not synchronize callings with LCR, access will need to be managed manually for all members in the Kindoo application.

	===== Manually Granted Callings =====		===== Manually Granted Callings =====
	After the callings are synchronized the stake Kindoo managers will need to manually add members to Kindoo who are not on the synchronized callings list. Callings are enabled across all units in the stake and cannot be customized to individual units. If the stake does not want all individuals with a calling to have access, do not enable that calling and grant access manually. The stake can also choose to synchronize access with a calling and then afterwards remove the access for a specific individual. Some callings where this may apply include:		After the callings are synchronized the stake Kindoo managers will need to manually add members to Kindoo who are not on the synchronized callings list. Some callings where this may apply include:
	*Primary activity day leaders		*Primary activity day leaders

Waymana: Changed the Stake Kindoo Manager Responsibilities section and Synchronized Calling section.

2025-11-04T02:24:27Z

Changed the Stake Kindoo Manager Responsibilities section and Synchronized Calling section.

← Older revision		Revision as of 02:24, 4 November 2025
Line 11:		Line 11:
	=== Stake Kindoo Manager Responsibilities ===		=== Stake Kindoo Manager Responsibilities ===
	The stake Kindoo manager is the stake building representative or another individual that the stake president assigns such as a stake clerk or stake technology specialist. He or she will manage building access for the stake in the Kindoo application. Additional individuals can be assigned as a manager in the Kindoo system. As the licenses are controlled at the stake level, it is recommended that there be no more than one or two managers per stake.		The stake Kindoo manager is the stake building representative or another individual that the stake president assigns such as a stake clerk or stake technology specialist. He or she will manage building access for the stake in the Kindoo application. Additional individuals can be assigned as a manager in the Kindoo system. As the licenses are controlled at the stake level, it is recommended that there be no more than one or two managers per stake.

			Because the number of available user seats is only viewable at the stake level in the Kindoo application it is recommended that Kindoo be managed at the stake level. The stake Kindoo manager could have a backup and stake building schedulers could be given the assignment of granting temporary access. Having multiple managers makes it challenging to manage the licenses and across the stake. Each additional manager should know how many user seats they can use to grant temporary access and the individuals they have assigned to those seats. For example, if a stake only had 10 extra user seats and it had five wards, the stake Kindoo manager could inform the other managers that they only have two extra users seats available to use for guests.

	Instructions on granting user access as well as details about who will be receiving automatic access can be found below.		Instructions on granting user access as well as details about who will be receiving automatic access can be found below.
Line 21:		Line 23:
	Only one person (email address) can be assigned to a user seat at a time. Once the user seat is assigned, it is reserved until it is revoked or expires (for temporary users). For example, if a stake had a total of 100 user seats and 90 were assigned, the Kindoo managers would have 10 user seats available to use to grant temporary guest access. If six user seats are assigned on Monday for use on a Saturday morning. Only 4 user seats would be available until those assigned user seats expire.		Only one person (email address) can be assigned to a user seat at a time. Once the user seat is assigned, it is reserved until it is revoked or expires (for temporary users). For example, if a stake had a total of 100 user seats and 90 were assigned, the Kindoo managers would have 10 user seats available to use to grant temporary guest access. If six user seats are assigned on Monday for use on a Saturday morning. Only 4 user seats would be available until those assigned user seats expire.

	User seats are purchased by the FM group. Each stake starts with 30 user seats for stake ~~callings,~~ 20 for each ward~~, and 20 for additional users~~. For example, if a stake had six wards they would start with 170 seats. All user seats are assigned at the stake level. Licenses are restricted to ensure that the buildings are secure and access is tracked. Additional user seats should only be requested by the stake president to the FM. As user seats are permanent and cannot be refunded, they should be added only when necessary. Before requesting more seats, the stake should use the current number of seats for a few months and then review logs to determine if there are any users that are not using their license.		User seats are purchased by the FM group. Each stake starts with an initial allocation of 50 user seats for the stake and then 20 for each ward or branch. For example, if a stake had six wards they would start with 170 seats. All user seats are assigned at the stake level. Licenses are restricted to ensure that the buildings are secure and access is tracked. Additional user seats should only be requested by the stake president to the FM. As user seats are permanent and cannot be refunded, they should be added only when necessary. Before requesting more seats, the stake should use the current number of seats for a few months and then review logs to determine if there are any users that are not using their license.

	A Kindoo account can only be used on one device at a time. Members should not share their password with others so that they can access church buildings. Access should be requested through the stake Kindoo manager(s). If a member’s account consistently switches between devices, their access may be revoked.		A Kindoo account can only be used on one device at a time. Members should not share their password with others so that they can access church buildings. Access should be requested through the stake Kindoo manager(s). If a member’s account consistently switches between devices, their access may be revoked.
Line 28:		Line 30:
	Access is granted through the Kindoo mobile app or desktop version (https://web.kindoo.tech/).		Access is granted through the Kindoo mobile app or desktop version (https://web.kindoo.tech/).

	Kindoo can be synchronized with member calling data based on information in Leader and Clerk Resources (LCR). When a ~~member~~ is ~~assigned a~~ calling in ~~LCR that is approved for Kindoo access they receive an invitation~~ and ~~when they are released they are removed from Kindoo~~. ~~The~~ stake ~~president determines which~~ callings ~~should~~ receive ~~automatic~~ access ~~for their~~ stake. ~~After~~ the callings ~~are synchronized~~ the stake ~~Kindoo managers will only need to manually add members to Kindoo who are not on the synchronized callings list~~.		===== Synchronized Callings =====
			Kindoo can be synchronized with member calling data based on information in Leader and Clerk Resources (LCR). As callings are updated in LCR, members will gain or lose access to Kindoo automatically for the buildings they are assigned. When a calling is enabled, it applies to all relevant units within the stake. For example, enabling “Technology Specialist” will automatically assign licenses to everyone with that calling in all wards and branches. Members with stake callings receive access to all buildings in the stake. Ward callings receive access to only the buildings they are assigned. Synchronized callings can receive either “Always” (24/7 access usually given to the stake presidency and bishoprics) or “Limited daily” (5AM-11PM access).

	~~If your~~ stake ~~does not have~~ automatic ~~calling~~ access ~~set up, access will need~~ to ~~be managed manually for all members~~ in the ~~Kindoo application~~.		As there is a limit on licenses, the stake president determines which callings should receive [[CallingswithAutomaticKindooAccess\|automatic access]] for their stake. They provide the list to the Facilities Manager who updates the list of callings in a separate Church application. Before the calling synchronization is turned on the FM can provide a report of the members that will receive access.

	~~==== Temporary and Other Calling Access ====~~		If the stake does not synchronize callings with LCR, access will need to be managed manually for all members in the Kindoo application.
	~~Some members may require short-term or temporary access that are~~ not ~~on the list of those who are automatically granted~~ access~~. Below are some examples of individuals that may need building access. These individuals~~ will need to be ~~granted access~~ manually by the ~~stake~~ Kindoo ~~manager. These types of users are defined as temporary or guest users~~.

	* Members needing repeat access ~~due~~ to a calling ~~not included on~~ the ~~default list~~		===== Manually Granted Callings =====
			After the callings are synchronized the stake Kindoo managers will need to manually add members to Kindoo who are not on the synchronized callings list. Callings are enabled across all units in the stake and cannot be customized to individual units. If the stake does not want all individuals with a calling to have access, do not enable that calling and grant access manually. The stake can also choose to synchronize access with a calling and then afterwards remove the access for a specific individual. Some callings where this may apply include:
			*Primary activity day leaders

	* ~~Primary activity day leaders~~		* Athletic directors
			* Technology specialists
			* Accompanists
			* Advisors
			* Full-time missionary companionships are granted access manually using the teaching area email. (see the section “Granting Local Full-time Missionaries Access)
			* If a member needs access to buildings in more than one stake, they need to have a license to each stake.

	* Stake YW athletic directors		===== Guest Access =====
			Some members may require short-term or temporary access that are not on the list of those who are automatically granted access. Below are some examples of individuals that may need building access. These individuals will need to be granted access manually by the stake Kindoo manager. These types of users are defined as temporary or guest users. Temporary users fill a user seat from the time that they are granted access until their access expires or is revoked. A best practice is to assign these the week that they need access to avoid running out of licenses.

	* Members or guests needing access for a series of events		* Members or guests needing access for a series of events

	* Self-reliance courses		* Self-reliance courses
Line 56:		Line 66:

	* Blood drives		* Blood drives

	~~Full-time missionary companionships are granted access manually using the teaching area email. (see the section “Granting Local Full-time Missionaries Access)~~

	~~If a member needs access to buildings in more than one stake, they need to have a license to each stake.~~

	Because the number of available user seats is only viewable at the stake level in the Kindoo application it is recommended that Kindoo be managed at the stake level. The stake Kindoo manager could have a backup and stake building schedulers could be given the assignment of granting temporary access. Having multiple managers makes it challenging to manage the licenses and across the stake. Each additional manager should know how many user seats they can use to grant temporary access and the individuals they have assigned to those seats. For example, if a stake only had 10 extra user seats and it had five wards, the stake Kindoo manager could inform the other managers that they only have two extra users seats available to use for guests.

	==== Granting Access in Kindoo ====		==== Granting Access in Kindoo ====

Button23r at 16:46, 25 August 2025

2025-08-25T16:46:01Z

← Older revision		Revision as of 16:46, 25 August 2025
Line 71:		Line 71:
	# Click the stake you want to give the individual access to.		# Click the stake you want to give the individual access to.
	# Select '''Users'''. The app will display a list of authorized users for the stake.		# Select '''Users'''. The app will display a list of authorized users for the stake.
	# At the top of the screen, click on '''Add Users'''. [[File:1 Add Users.png\|~~center~~\|~~thumb~~]]		# At the top of the screen, click on '''Add Users'''. [[File:1 Add Users.png\|thumb\|none\|100x100px]]
	# Select '''Add a Single User'''.		# Select '''Add a Single User'''.
	# Check that there are user seats available. (See the identifying available user seats section for more information.)		# Check that there are user seats available. (See the identifying available user seats section for more information.)
Line 78:		Line 78:
	# Toggle the field "''Temporary user''" if the person's access should expire after a certain date. Complete the section specifying when their rights should be activated and expire. Note that the individual will still use a user seat until their access expires and they are removed from the system.		# Toggle the field "''Temporary user''" if the person's access should expire after a certain date. Complete the section specifying when their rights should be activated and expire. Note that the individual will still use a user seat until their access expires and they are removed from the system.
	# Put in a description of who the user is. We recommend this naming convention: [Unit Name] - [Calling Name]. Example: Redmond 1st Ward – Bishop.		# Put in a description of who the user is. We recommend this naming convention: [Unit Name] - [Calling Name]. Example: Redmond 1st Ward – Bishop.
	# Click '''Save'''. The email invitation will be sent to the user. [[File:2 Image Next.png\|~~center~~\|~~thumb~~]]		# Click '''Save'''. The email invitation will be sent to the user. [[File:2 Image Next.png\|thumb\|none]]
	# If the user you are inviting does not have a Kindoo account, Kindoo will confirm that you want to invite them to Kindoo. Click '''OK'''.		# If the user you are inviting does not have a Kindoo account, Kindoo will confirm that you want to invite them to Kindoo. Click '''OK'''.
	# When asked if you would like to define the access rights for the user. Click '''Yes'''.		# When asked if you would like to define the access rights for the user. Click '''Yes'''.
	# To assign an existing access rule to the user, select '''Access Rule''' and click '''Next'''. Select the access rule(s) that will allow this user to access the correct building(s) and door(s). Access to specific entry points and times can also be entered manually or additional access rules can be created. Usually guests can just use the standard Limited Daily access for a building rather than setting up a custom access rule. [[File:3 Access.png\|~~center~~\|~~thumb~~]]		# To assign an existing access rule to the user, select '''Access Rule''' and click '''Next'''. Select the access rule(s) that will allow this user to access the correct building(s) and door(s). Access to specific entry points and times can also be entered manually or additional access rules can be created. Usually guests can just use the standard Limited Daily access for a building rather than setting up a custom access rule. [[File:3 Access.png\|thumb\|none]]
	# Click '''Save''' and select the back arrow in the upper-left corner to leave the screen once you have confirmed everything looks accurate for this user. The system will send the user an invite from Kindoo.		# Click '''Save''' and select the back arrow in the upper-left corner to leave the screen once you have confirmed everything looks accurate for this user. The system will send the user an invite from Kindoo.

Line 87:		Line 87:
	When adding users, keep in mind that there are a limited number of user seats for each stake. Only give access when needed. As soon as a user is created (even if the date they have access is in the future), that user occupies a user seat. Until that access expires (which can be set when creating the user), that user seat can't be used for another user.		When adding users, keep in mind that there are a limited number of user seats for each stake. Only give access when needed. As soon as a user is created (even if the date they have access is in the future), that user occupies a user seat. Until that access expires (which can be set when creating the user), that user seat can't be used for another user.

	When adding users, you can see how many user seats are assigned and how many are available. [[File:1 Eagle Mountain Stake.png\|thumb\|Example showing the number of user seats a stake is occupying.\|~~center~~]]Example showing the number of user seats in a stake.		When adding users, you can see how many user seats are assigned and how many are available. [[File:1 Eagle Mountain Stake.png\|thumb\|Example showing the number of user seats a stake is occupying.\|none]]Example showing the number of user seats in a stake.

	An error will display if there are no seats available. If the stake starts running out of user seats, first review the Kindoo usage reports and see if any users can be removed. Stakes with multiple Kindoo managers will need to coordinate so the stake does not run out of user seats.		An error will display if there are no seats available. If the stake starts running out of user seats, first review the Kindoo usage reports and see if any users can be removed. Stakes with multiple Kindoo managers will need to coordinate so the stake does not run out of user seats.

	Check to see if there are any users that have not accepted the Kindoo invitation that could potentially be removed. In the Users menu, look for users that have the “Resend Email” link. These users have not accepted the Kindoo invitation and could be removed.		Check to see if there are any users that have not accepted the Kindoo invitation that could potentially be removed. In the Users menu, look for users that have the “Resend Email” link. These users have not accepted the Kindoo invitation and could be removed.
	[[File:5 Resend Email.png\|~~center~~\|~~thumb~~]]		[[File:5 Resend Email.png\|thumb\|none\|150x150px]]
	To see all users and when they were invited in a spreadsheet, click “Export to CSV”.		To see all users and when they were invited in a spreadsheet, click “Export to CSV”.

Line 123:		Line 123:
	Most individuals should be able to use the Always or Limited Daily default access rules that are setup for those with synchronized callings. If additional access rules are needed they should only be created by the stake Kindoo manager. Too many access rules can be confusing and unnecessary. Avoid creating more access rules than are needed.		Most individuals should be able to use the Always or Limited Daily default access rules that are setup for those with synchronized callings. If additional access rules are needed they should only be created by the stake Kindoo manager. Too many access rules can be confusing and unnecessary. Avoid creating more access rules than are needed.

	Access rules does not affect the number of user seats available. If an individual is assigned an access rule for only certain times of the day they continue to use that user seat until their access expires or is revoked. [[File:Access Rules Examples.png~~\|center~~\|thumb\|478x478px]]		Access rules does not affect the number of user seats available. If an individual is assigned an access rule for only certain times of the day they continue to use that user seat until their access expires or is revoked. [[File:Access Rules Examples.png\|thumb\|478x478px\|none]]

	===== Create an Access Rule =====		===== Create an Access Rule =====
Line 150:		Line 150:
	*  '''From the access rules screen:''' Click on the ''Users'' tab and toggle the switch on a previously created user’s record to add them to this access rule.		*  '''From the access rules screen:''' Click on the ''Users'' tab and toggle the switch on a previously created user’s record to add them to this access rule.

	*  '''From the user’s profile''': Click ''Add Access Right'' at the top of the page. Select the access rule you want that user to have. [[File:6 Add Access Right.png\|~~center~~\|~~thumb~~\|~~200x200px~~]]		*  '''From the user’s profile''': Click ''Add Access Right'' at the top of the page. Select the access rule you want that user to have. [[File:6 Add Access Right.png\|thumb\|150x150px\|none]]

	9. Click ''Save''.		9. Click ''Save''.
Line 218:		Line 218:

	See the image below for an example of questions you could put on a form.		See the image below for an example of questions you could put on a form.
	[[File:Building Access Request Form Questions.jpg\|~~center~~\|~~thumb~~]]		[[File:Building Access Request Form Questions.jpg\|thumb\|none]]

	==== How do stakes that share a building manage access? ====		==== How do stakes that share a building manage access? ====