TechWiki - User contributions [en]

Glossary

2026-07-20T16:42:40Z

Ericjamee: /* C */

{{A2ZTOC}}
== A ==
;Active : Participating on a regular basis, such as attending meetings, observing the principles of the gospel, and accepting Church callings; Under current Church policy, those who attend meetings at least once a month.

; AD - Active Directory
: Active Directory is an implementation of LDAP directory services by Microsoft for use in Windows environments. AD (also known as EAD) stores information and settings relating to an organization in a central, organized, accessible database.

; AF - Ancestral File
: A database containing family history information contributed by members of the Church and others from 1979 to 1999. The file contains millions of names linked in family groups and pedigrees. Ancestral File data may be accessed on FamilySearch.org.

;Agent Bishop : The Bishop responsible for a meetinghouse when that building has multiple wards.

; AJAX - Asynchronous JavaScript and XML
: AJAX is a Web development technique for creating interactive Web applications. It exchanges small amounts of data with the server behind the scenes, so that the entire Web page does not have to be reloaded each time the user makes a change.

; API - Application Programming Interface
: An application programming interface (API) is a source code interface that a computer library provides to support requests to be made of it by a computer program.
: [http://en.wikipedia.org/wiki/Application_programming_interface Wikipedia Definition]

;Area : A geographical administrative region of many stakes and missions, usually including hundreds of thousands of members. Areas often cover many nations and are presided over by either a General Authority or an Area Authority Seventy.

;Area Presidency : A Presidency of general or regional leaders who preside over an area of the Church.

;Area President : A general or regional leader, a General Authority or Area Authority Seventy, who presides over an area of the Church.

; ASA
: Church-managed Cisco ASA 5505 firewall used for meetinghouse Internet connections.

; ASCII
: American Standard Code for Information Interchange. A standard definition employing characters that can be read without conversion.

; ASE - Application Service Engineer

; ASP - Active Server Pages
: ASP is Microsoft's server-side script engine for dynamically-generated Web pages. Programming ASP Web sites is made easier by various built-in objects.
: [http://en.wikipedia.org/wiki/Active_Server_Pages Wikipedia Definition]

;Auxiliary Organizations : Organizations in a ward that do not include the priesthood quorums. These organizations include the Relief Society, Primary, Young Women, Young Men, and Sunday School.

== B ==
; B2B - Business-to-Business
: Business-to-business (or B2B for short) is a marketing strategy that involves the transaction of goods or services between businesses (as opposed to relations between businesses and other groups, such as consumers or public administration).
: [http://en.wikipedia.org/wiki/B2B Wikipedia Definition]

; B2C - Business-to-Consumer
: B2C (also business-to-customer) describes activities of commercial organization serving the end consumer with products and services.
: [http://en.wikipedia.org/wiki/B2C Wikipedia Definition]

; B2E - Business-to-Employee
: B2E uses an intrabusiness network that allows companies to provide products and services to their employees. Typically, companies use B2E networks to automate employee-related corporate business.
: [http://en.wikipedia.org/wiki/B2E Wikipedia Definition]

;Baptism : The initial saving ordinance performed on those who have joined the Church or who have reached the age of eight, characterized by immersing the person completely in water. Baptisms therefore need to be recorded on Membership records.

; BI - Business Intelligence
: BI is a broad category of applications and technologies for gathering, providing access to, and anlyzing data for the purpose of helping enterprise users make better business decisions.
: [http://en.wikipedia.org/wiki/Business_Intelligence Wikipedia Definition]

;Bishop : A priesthood leader responsible for the spiritual and temporal welfare of a ward. Bishops preside over most ward functions and activities, interview members of their wards for worthiness, call members of their ward to callings within the ward and oversee efforts to provide for ward members unable to provide for themselves.

;Block Schedule : A schedule of Sunday meetings that takes place in a three-hour period. The block schedule contains the sacrament meeting and Melchizedek Priesthood, Aaronic Priesthood, Relief Society, Young Women, Primary, and Sunday school meetings. See ''Handbook 2: Administering the Church'', section [http://lds.org/handbook/handbook-2-administering-the-church/meetings-in-the-church 18] for timing and sequence of meetings.

; Blog - Web Log
: A blog is a Web site where entries are made in journal style and displayed in reverse chronological order.
: [http://en.wikipedia.org/wiki/Blog Wikipedia Definition]

; BO - BusinessObjects
: Enterprise software that is used for business intelligence.

; Born in the Covenant (BIC) : A child who is born in the covenant does not have to be sealed to the parents. A child whose parents were sealed to one another in the temple before the child was born is BIC. A child born after the mother's sealing to her husband is canceled is not BIC. A child born after one of the parents is excommunicated is not BIC.

;Branch : The smallest organized unit of the Church. A congregation not large enough to be made into a ward, or not in an area with enough members to make a stake.

;Branch Clerk : A priesthood leader responsible for the administrative functions of a branch; generally managing the membership and financial records of a branch.

;Branch President : The priesthood holder called and set apart to lead a branch.

;Bulletin : (a k a Ward Bulletin or Sacrament Meeting Program) The printed listing of planned prayers, talks and other sacrament meeting elements passed out at the beginning of each Sacrament Meeting in most LDS congregations.

== C ==
;CAB : Church Administration Building

;Calling : An office or assignment in the Church; An invitation to accept an office or assignment in the Church.

; CCN - Church Communications Network
: The Church's global network.

;[[CDOL]] : Church Directory of Organizations and Leaders

; CES - Church Educational System : The '''Church Educational System (CES)''' serves as the umbrella for all education programs of the Church, including Church-owned universities and colleges, institutes of religion, and seminary programs worldwide.

;CFAR : ''Obsolete''. See CUBS.

;CHI : ''Obsolete''. See Handbook.

;CHQ : Church Headquarters

;Church Handbook of Instructions : ''Obsolete''. See Handbook.

;Clerk : A priesthood holder responsible for tracking financial and membership information and maintaining the associated records.

;Clerk's Office : The room in an LDS meetinghouse or stake center that is used by the Clerks. The room where a unit's financial and membership transactions are made and the associated records are kept.
'''CNM - Church Network Manager'''

Church Network Manager (CNM) is a web-based tool that allows stake technology specialists (STSs) and certain Church leaders to view and manage network devices within their meetinghouses.

;COB : Church Office Building

;Confirmation : An ordinance performed after baptism whereby a person becomes a member of The Church of Jesus Christ of Latter-day Saints. This ordinance is performed under the direction of the bishop. One or more Melchizedek Priesthood holders place their hands on the person’s head and confirm them as a member of The Church of Jesus Christ of Latter-day Saints and use the wording “Receive the Holy Ghost.” May also pronounce a blessing as inspired by the Holy Ghost. Confirmation for eight-year-old [[members of record]] is performed at the baptism. Confirmation for converts is performed at a sacrament meeting on a Sunday following the baptism.

;[[Consolidated Financial Statement]] : Monthly summary for the stake of all units' financial activity.

;Convert
: An individual nine years of age or older who is baptized and confirmed a member of the Church, or an eight-year-old whose parents are not members or are being baptized at the same time. Individuals under the age of eighteen must have the permission of both parents before being baptized.

; COTS - Commercial Off-the-Shelf
: COTS is a term for software or hardware products that are ready-made and available for sale, lease, or license to the general public. They are often used as alternatives to in-house development projects.
: [http://en.wikipedia.org/wiki/Commercial_off-the-shelf Wikipedia Definition]

;Court : ''Obsolete''. See Disciplinary Council

; CRM - Customer Relationship Management
: CRM is a broad term that covers concepts used by companies to manage their relationships with customers, including the capture, storage, and analysis of customer information.
: [http://en.wikipedia.org/wiki/Customer_relationship_management Wikipedia Definition]

;CUBS - Church Unit Banking Services
: Introduced in 2010, a worldwide back office system used by administrative offices for financial record-keeping. Over time, all regions will transition from CFAR or LURBS to CUBS.

;CUFS : [[Church Unit Financial Statement]] (Bank Statement) This has been replaced by the Unit Financial Statement.

== D ==
;Disciplinary Council : A council of local leaders and other priesthood holders held to review the inappropriate behavior of a Church member and to decide on appropriate consequences. Councils may also be reconvened after a period of time to see if a member has repented sufficiently to be restored to full fellowship. See chapter 6 of ''Handbook 1: Stake Presidents and Bishops'' for details.

;District : A district is a smaller version of a stake, organized as the parent unit of branches instead of wards. A district may be organized when there are enough branches in an area to allow easy communication and convenient travel to district meetings. A district president presides over the district and reports to the mission presidency.

;District Clerk : Person responsible for all clerical activities in a district.

;District President : The district president presides over the district and is assisted by two counselors. The district president reports to and receives direction from the mission president.

; DIZ - Development Integration Zone

== E ==
; EAD - Enterprise Active Directory
: Active Directory is an implementation of LDAP directory services by Microsoft for use in Windows environments (also known as AD) stores information and settings relating to an organization in a central, organized, accessible database.
: [http://en.wikipedia.org/wiki/Active_Directory Wikipedia Definition]

; EFD - Exploration Findings Document
: This document is used to identify possible solutions for a specific project.

;Elders Quorum : A quorum in the Church is a combination of a class, a fraternity of brethren, and a service organization. An elders quorum is a group of brethren in a ward consisting of up to 96 elders. After this number is reached, the quorum may be divided under direction of the stake president.

;Elders Quorum President : The elders quorum in a ward is presided over by an elders quorum president and two counselors.

;Endowment : Instruction received in the temple pertaining to the purposes and plans of the Lord in creating and peopling the earth and in exalting his children in the life to come.

;Equalized Contribution : Refers to the support from the General Missionary Fund that results in each missionary serving from a specific country contributing the same amount irrespective of where in the world they serve.

;ERC : Employment Resource Center

; ERS - [http://providentliving.org/content/list/0,11664,1962-1,00.html Employment Resource Services]

; EUP - End-User Productivity

== F ==
;Family History Center : A Family History Center is a branch facility of the Family History Library in Salt Lake City. It contains staff to help patrons identify their ancestors through the use of computer programs and microfilms and microfiche that may be ordered from the Family History Library.

;Fast Offering : Fast offerings are funds freely given monthly by members of the Church to help the needy. As a general guideline members fast for two meals and contribute the cash equivalent of the cost of the two meals to the Church. The use of fast offerings is at the discretion of the bishop under the direction of the stake president.

; FCH - Family and Church History Department

;FHC : Family History Center

; FHL - [http://www.familysearch.org/Eng/Library/FHL/frameset_library.asp Family History Library]

;[[Financial Clerk]] : Person responsible for financial matters in the unit.

; FIR - Facility Issue Reporting : The FIR system provides LDS Church leaders, building representatives, and facilities management groups the ability to report and review facility issues electronically. It uses a web interface to streamline reporting, viewing, and resolving of facility issues.

;FIS : Old DOS-based local unit financial software that is no longer used. See [[MLS]] for current software.

;FM Group : Facilities Management Group

; FWIW - For What It's Worth

== G ==
;General Handbook of Instructions : ''Obsolete''. See Handbook.

;[[Geo code]] : A code used to group members into geographic areas, usually to analyze how a unit might be divided.

;GHI : General Handbook of Instructions. ''Obsolete''. See Handbook.

; GIDS - Global Identity Services
: Project to create LDS Sign-in.

; GIS - Geographic Information System
: A geographic information system (GIS) is a system for capturing, storing, analyzing, and managing data and associated attributes which are spatially referenced to the earth.
: [http://en.wikipedia.org/wiki/Gis Wikipedia Definition]

; GSC - [[Global Service Center]]
: The GSC enables Directors of Temporal Affairs and Managing Directors to focus on their most important work by providing efficient transaction processing. They make gospel teachings, resources, and services directly and globally accessible in a self-service, scalable, affordable way. They help with questions and problems related to things such as IT support, Distribution Services, and clerk and leader issues.

; GSD - Global Service Desk
: Former name for the Global Service Center (GSC).

== H ==
;Handbook : The policy manual for administering the Church, consisting of two volumes: ''Handbook 1: Bishops and Stake Presidents'' and ''[http://lds.org/handbook/handbook-2-administering-the-church Handbook 2: Administering the Church]''.

;High Priests Group : The stake president presides over the stake quorum of high priests, made up of all the high priests in the stake. The quorum is divided at the ward level into individual high priests groups.

;High Priests Group Leader : The high priest group in a ward is presided over by a high priest group leader and two assistants. Under the bishopric’s direction, the high priests group leader coordinates temple and family history work in the ward.

;[[Annual History|Historical Specialist]] : Clerk responsible for preparing the [[Annual_History|annual historical reports]].

;Home Teacher : Home teachers are priesthood brethren who are assigned families at the ward level to visit monthly, to help and to strengthen. They are assigned by priesthood leaders.

;Home Teaching : Home teaching is the responsibility of all Melchizedek Priesthood holders and of those who are teachers and priests in the Aaronic Priesthood. As part of their responsibility to watch over the members of the Church, home teachers visit their assigned families at least once each month to teach and strengthen them.

== I ==
; ICS - Information and Communications Systems Department

; IGI - International Genealogical Index
: A list of names of deceased persons for whom temple ordinances have been performed. The most current version is available on the [http://www.familysearch.org/ FamilySearch] Web site.

; IMOS - Internet Mission Office System

;Inactive : A term not officially used in the Church any more. See '''Less Active'''.

;Inactivity

;[[Individual Ordinance Summary]] : A form that contains most of the information on a [[Membership Records|Membership Record]] that can appropriately be given to a member.

;Investigator

;[[Individual Ordinance Summary|IOS]] : Individual Ordinance Summary

; IP - Internet Protocol
: An Internet protocol is a unique address that devices use to identify and communicate with each other on a computer network utilizing the Internet protocol standard (IP).
: [http://en.wikipedia.org/wiki/IP_address Wikipedia Definition]

; IROP - Internal Record Of Purchase : A document used to record internal Church purchase transactions. The most common IROP transactions for Church units are those made at LDS Distribution Services online through the LDS Store, in person, or by telephone. Unit IROPs are transmitted electronically through MLS.

== J ==
; JSMB - [http://www.lds.org/placestovisit/location/0,10634,1872-1-1-1,00.html Joseph Smith Memorial Building]

== K ==
; KB - KnowledgeBase
: A database of articles that help individuals resolve issues.

== L ==
;Less Active : Participating in Church on an irregular basis, which may vary from coming to a few things a year to never coming at all. Members who attend meetings less than once a month are considered less active.

;[[Priesthood Line of Authority|Line of Authority]] : The chain of ordinations for a priesthood holder showing who ordained him to his current office, who ordained the ordainer, and so on back to Jesus Christ.

;LUAAT : Local Unit Area Auditor Trainer

;[[Budget Allowance|LUBA]] : Local Unit Budget Allowance

;LURBS : Local Unit Receipting, Reporting, and Banking System - A back office system used by administrative offices for financial record-keeping outside of North America. It provides various reports for local units, including a [[Ward/Branch Monthly Financial Report|monthly financial report]].

;[[Administrative office#Local Unit Support|LUS]] : Local Unit Support Group - Located in Salt Lake City, Utah, provides support for priesthood leaders in Canada and the United States.

;[[LUWS]] - Local Unit Web Site
: Also called the "Classic Ward and Stake Website," these sites were retired at the end of 2012 and replaced by various tools on LDS.org.

== M ==
;Member : A member of the Church of Jesus Christ of Latter-day Saints is a person eight years old or older who has been baptized and confirmed a member of the Church.

;Membership : The state of being a member of the Church of Jesus Christ of Latter-day Saints, as evidenced by records kept at Church headquarters and in the local unit's MLS. Records are also created for children of members of the Church who are under eight years old; however, these children are not considered members until eight years old, when they are baptized and confirmed.

;[[Membership Clerk]] : Person responsible for maintaining membership records on the members of a unit.

;[[Membership Records|Membership Record]]

;MIS : Old DOS-based local unit membership software. See [[MLS]] for current software.

;[[MLS]] - Member and Leader Services (membership and financial software)
: MLS software is for use by unit leaders, clerks, auxiliary and quorum leaders, and secretaries at both the ward and stake levels. MLS is designed to make Church record-keeping easier and more efficient.

;MRN : Membership Record Number

;[[Administrative office|MSR]] : Membership and Statistical Records Department - the Church department that is commonly known to clerks as the [[administrative office]].

== N ==
;[[NQI]] : Non-quality item - a financial transaction that is not complete after 2 months.

; NOB - North Office Building
: The building that is directly north of the Church Office Building and was previously called the Data Center.

== O ==
;Office : A position in the priesthood (such as priest, elder, and high priest) that has attached to it certain duties, responsibilities, and rights.

;Ordinance : A ceremony performed by the priesthood for a specific purpose. Examples are baptism/confirmation, ordination to the priesthood, and temple sealings. Some are saving ordinances and must be received by members in order to be saved, such as baptism/confirmation. Others may not necessarily be saving ordinances, such as a child blessing.

;Ordination : The bestowal of the priesthood and/or a priesthood office. For example, when a male member is ordained to the office of elder, he receives the Melchizedek Priesthood and is ordained to the office of elder within the Melchizedek Priesthood. Later in life, if he is ordained to the office of high priest, he does not receive the Melchizedek Priesthood again, but is ordained to the office of high priest within the Melchizedek Priesthood. Both examples are considered ordinations.

== P ==
; PAF - Personal Ancestral File
: A Church-produced computer software program that enables people to compile and organize their genealogy on their personal computers. PAF can help members identify ancestors and prepare their names for temple work.

;Patriarch : Patriarch is an office in the Melchizedek Priesthood, and not a calling. A patriarch is recommended by the stake president, sustained in stake conference or stake priesthood meeting, and ordained by the First Presidency or one of the Twelve Apostles or (with written permission from the Twelve) the stake president. Patriarchs give personal blessings to members of the stake (see Patriarchal Blessing).

;Patriarchal Blessing : A blessing given to a member by the patriarch of his or her stake. After the member obtains a recommendation from the bishop, he or she is given a blessing in which the patriarch may give the member's lineage, list weaknesses and strengths, pronounce advice from the Lord concerning the member's future, and any other direction or guidance.

; PC - Personal Computer

; PDD - Project Definition Document

;PEC : Priesthood Executive Committee

;PEF : Perpetual Education Fund

;Perpetual Education Fund

;Personal Priesthood Interview : ''Obsolete''. See Priesthood Interview

;Physical Facilities Representative : A local priesthood holder responsible for the physical status of a meetinghouse.

;PI : Priesthood Interview

; PIX
: Church-managed Cisco PIX firewall used primarily for FHC Internet connections.

;PLT : Priesthood Leadership Travel

;PPI : Personal Priesthood Interview. ''Obsolete''. See Priesthood Interview

;Presiding Bishop : A General Authority of the Church. The Presiding Bishop and his counselors serve under the direction of the First Presidency to administer the temporal affairs of the Church.

; PRF - Pedigree Resource File
: A file of lineage-linked data submitted by both members and nonmembers through the [http://www.familysearch.org/ FamilySearch] Web site. The master index is available online and the entire file is available on CD. The Pedigree Resource File is the successor to the Ancestral File.

;Priesthood Executive Committee

;Priesthood Interview : A private stewardship meeting between a priesthood leader and a person who reports to him

== Q ==
;[[Quarterly Report]] : A report of member attendance and other key statistics submitted by wards to the stake and the Church each quarter

== R ==
;Recommend

;Record

;Record Keeping

;REFIS

;Relief Society : The women's organization of the Church, organized by Joseph Smith in 1842, dedicated to "the exercise of all benevolent purposes." The Relief Society provides Sunday gospel instruction, other Relief Society meetings, visiting teaching, and welfare and compassionate service opportunities.

;RS : Relief Society

; RSS - Really Simple Syndication
: RSS is a Web-feed format that is used to publish frequently updated digital content to consumers who use RSS aggregators to notify them of updates.
: [http://en.wikipedia.org/wiki/RSS Wikipedia Definition]

== S ==
; SAV - Symantec Anti-Virus : An anti-virus software formerly used on Church-owned computers, such as those used in stakes and wards. All computers should now have the Sophos anti-virus software.

; SA - Single Adult
: A single member above the age of 30. See also YSA.

; SDK - Software Development Kit
: SDK is typically a set of development tools that allows a software engineer to create applications for a certain software package, software framework, hardware platform, computer system, video game console, operating system, and more.
: [http://en.wikipedia.org/wiki/Software_development_kit Wikipedia Definition]

; SEO - Search Engine Optimization

; SERP - Search Engine Results Page

;Set Apart

;SFS : ''Obsolete''. See Consolidated Financial Statement.

; SOAP - Simple Object Access Protocol
: A protocol for exchanging XML-based messages over a computer network, normally using HTTP.
: [http://en.wikipedia.org/wiki/SOAP Wikipedia Definition]

; Sophos Anti-Virus : An anti-virus software currently used on Church-owned computers, such as those used in stakes and wards.

; SORT
: An internal conference hosted by ICS for technical Church employees.

; SRD - Solutions Requirement Document
: The SRD is used to identify the business requirements and business case for a proposed technology project.

; SSH - Secure Shell
: SSH is a communication system that uses public-key cryptography to establish a secure connection between remote computers.
: [http://en.wikipedia.org/wiki/Ssh Wikipedia Definition]

;Stake

;[[Stake Clerk]] : Person responsible for all clerical activities in a stake.

;Stake President : The stake president presides over the stake and is assisted by two counselors. The stake president reports to and receives direction from the presidency of the Seventy or from the Area President.

;[[Stake Technology Specialist]] : Person responsible for the technology assets of the stake and each ward in the stake.

;[[Statistical Clerk]] : Person responsible for collecting and preparing the [[Quarterly Report]].

== T ==

;[[Desktop Management Software|TEM]] - Tivoli Endpoint Manager
: Replaced LANDesk as the official software CHQ uses to centrally manage and secure the global fleet of Church-owned computers. TEM will install and utilize the BES Client service.

;Temple

;Temple Ordinances

;Temple Recommend

;Temporal

;Tithing

;Tithing Settlement

== U ==
;Unit : A congregation or other function in the Church that is responsible for its budget. Wards, Stakes, Branches, Districts, Family History Centers, etc., are all examples of Units.

;Unit Financial Statement : the Unit Financial Statement has replaced the old Church Unit Financial Statement.

== V ==
;Visiting Teacher

;Visiting Teaching

; VoIP - Voice Over Internet Protocol
: The technology that allows voice communication (such as telephone) over a network instead of through traditional phone lines. The Church has deployed VoIP in several locations indlucing BYU, the North Office Building, the Triad Center, and Ghana.
: [http://en.wikipedia.org/wiki/Voip Wikipedia Definition]

; VPN - Virtual Private Network
: VPN is a private communications network often used within a company, or by several companies or organization, to communication confidentially over a publicly accessible network.
: [http://en.wikipedia.org/wiki/Vpn Wikipedia Definition]

== W ==
;Ward

;Ward Budget

;[[Ward Clerk]] : Person responsible for all clerical activities in a ward.

;Ward Council

;Ward Welfare Committee

;Welfare

;Welfare Services

== Y ==
;YM - Young Men
:Single male members between the ages of 12-18.

;YSA - Young Single Adult
:A single member between the ages of 18-30. See also SA.

;YW - Young Women
:Single female members between the ages of 12-18.

[[Category:Help]]

Glossary

2026-07-20T16:40:20Z

Ericjamee: /* C */

{{A2ZTOC}}
== A ==
;Active : Participating on a regular basis, such as attending meetings, observing the principles of the gospel, and accepting Church callings; Under current Church policy, those who attend meetings at least once a month.

; AD - Active Directory
: Active Directory is an implementation of LDAP directory services by Microsoft for use in Windows environments. AD (also known as EAD) stores information and settings relating to an organization in a central, organized, accessible database.

; AF - Ancestral File
: A database containing family history information contributed by members of the Church and others from 1979 to 1999. The file contains millions of names linked in family groups and pedigrees. Ancestral File data may be accessed on FamilySearch.org.

;Agent Bishop : The Bishop responsible for a meetinghouse when that building has multiple wards.

; AJAX - Asynchronous JavaScript and XML
: AJAX is a Web development technique for creating interactive Web applications. It exchanges small amounts of data with the server behind the scenes, so that the entire Web page does not have to be reloaded each time the user makes a change.

; API - Application Programming Interface
: An application programming interface (API) is a source code interface that a computer library provides to support requests to be made of it by a computer program.
: [http://en.wikipedia.org/wiki/Application_programming_interface Wikipedia Definition]

;Area : A geographical administrative region of many stakes and missions, usually including hundreds of thousands of members. Areas often cover many nations and are presided over by either a General Authority or an Area Authority Seventy.

;Area Presidency : A Presidency of general or regional leaders who preside over an area of the Church.

;Area President : A general or regional leader, a General Authority or Area Authority Seventy, who presides over an area of the Church.

; ASA
: Church-managed Cisco ASA 5505 firewall used for meetinghouse Internet connections.

; ASCII
: American Standard Code for Information Interchange. A standard definition employing characters that can be read without conversion.

; ASE - Application Service Engineer

; ASP - Active Server Pages
: ASP is Microsoft's server-side script engine for dynamically-generated Web pages. Programming ASP Web sites is made easier by various built-in objects.
: [http://en.wikipedia.org/wiki/Active_Server_Pages Wikipedia Definition]

;Auxiliary Organizations : Organizations in a ward that do not include the priesthood quorums. These organizations include the Relief Society, Primary, Young Women, Young Men, and Sunday School.

== B ==
; B2B - Business-to-Business
: Business-to-business (or B2B for short) is a marketing strategy that involves the transaction of goods or services between businesses (as opposed to relations between businesses and other groups, such as consumers or public administration).
: [http://en.wikipedia.org/wiki/B2B Wikipedia Definition]

; B2C - Business-to-Consumer
: B2C (also business-to-customer) describes activities of commercial organization serving the end consumer with products and services.
: [http://en.wikipedia.org/wiki/B2C Wikipedia Definition]

; B2E - Business-to-Employee
: B2E uses an intrabusiness network that allows companies to provide products and services to their employees. Typically, companies use B2E networks to automate employee-related corporate business.
: [http://en.wikipedia.org/wiki/B2E Wikipedia Definition]

;Baptism : The initial saving ordinance performed on those who have joined the Church or who have reached the age of eight, characterized by immersing the person completely in water. Baptisms therefore need to be recorded on Membership records.

; BI - Business Intelligence
: BI is a broad category of applications and technologies for gathering, providing access to, and anlyzing data for the purpose of helping enterprise users make better business decisions.
: [http://en.wikipedia.org/wiki/Business_Intelligence Wikipedia Definition]

;Bishop : A priesthood leader responsible for the spiritual and temporal welfare of a ward. Bishops preside over most ward functions and activities, interview members of their wards for worthiness, call members of their ward to callings within the ward and oversee efforts to provide for ward members unable to provide for themselves.

;Block Schedule : A schedule of Sunday meetings that takes place in a three-hour period. The block schedule contains the sacrament meeting and Melchizedek Priesthood, Aaronic Priesthood, Relief Society, Young Women, Primary, and Sunday school meetings. See ''Handbook 2: Administering the Church'', section [http://lds.org/handbook/handbook-2-administering-the-church/meetings-in-the-church 18] for timing and sequence of meetings.

; Blog - Web Log
: A blog is a Web site where entries are made in journal style and displayed in reverse chronological order.
: [http://en.wikipedia.org/wiki/Blog Wikipedia Definition]

; BO - BusinessObjects
: Enterprise software that is used for business intelligence.

; Born in the Covenant (BIC) : A child who is born in the covenant does not have to be sealed to the parents. A child whose parents were sealed to one another in the temple before the child was born is BIC. A child born after the mother's sealing to her husband is canceled is not BIC. A child born after one of the parents is excommunicated is not BIC.

;Branch : The smallest organized unit of the Church. A congregation not large enough to be made into a ward, or not in an area with enough members to make a stake.

;Branch Clerk : A priesthood leader responsible for the administrative functions of a branch; generally managing the membership and financial records of a branch.

;Branch President : The priesthood holder called and set apart to lead a branch.

;Bulletin : (a k a Ward Bulletin or Sacrament Meeting Program) The printed listing of planned prayers, talks and other sacrament meeting elements passed out at the beginning of each Sacrament Meeting in most LDS congregations.

== C ==
;CAB : Church Administration Building

;Calling : An office or assignment in the Church; An invitation to accept an office or assignment in the Church.

; CCN - Church Communications Network
: The Church's global network.

;[[CDOL]] : Church Directory of Organizations and Leaders

; CES - Church Educational System : The '''Church Educational System (CES)''' serves as the umbrella for all education programs of the Church, including Church-owned universities and colleges, institutes of religion, and seminary programs worldwide.

;CFAR : ''Obsolete''. See CUBS.

;CHI : ''Obsolete''. See Handbook.

;CHQ : Church Headquarters

;Church Handbook of Instructions : ''Obsolete''. See Handbook.

;Clerk : A priesthood holder responsible for tracking financial and membership information and maintaining the associated records.

;Clerk's Office : The room in an LDS meetinghouse or stake center that is used by the Clerks. The room where a unit's financial and membership transactions are made and the associated records are kept.
'''CNM - Church Network Manager'''
;COB : Church Office Building

;Confirmation : An ordinance performed after baptism whereby a person becomes a member of The Church of Jesus Christ of Latter-day Saints. This ordinance is performed under the direction of the bishop. One or more Melchizedek Priesthood holders place their hands on the person’s head and confirm them as a member of The Church of Jesus Christ of Latter-day Saints and use the wording “Receive the Holy Ghost.” May also pronounce a blessing as inspired by the Holy Ghost. Confirmation for eight-year-old [[members of record]] is performed at the baptism. Confirmation for converts is performed at a sacrament meeting on a Sunday following the baptism.

;[[Consolidated Financial Statement]] : Monthly summary for the stake of all units' financial activity.

;Convert
: An individual nine years of age or older who is baptized and confirmed a member of the Church, or an eight-year-old whose parents are not members or are being baptized at the same time. Individuals under the age of eighteen must have the permission of both parents before being baptized.

; COTS - Commercial Off-the-Shelf
: COTS is a term for software or hardware products that are ready-made and available for sale, lease, or license to the general public. They are often used as alternatives to in-house development projects.
: [http://en.wikipedia.org/wiki/Commercial_off-the-shelf Wikipedia Definition]

;Court : ''Obsolete''. See Disciplinary Council

; CRM - Customer Relationship Management
: CRM is a broad term that covers concepts used by companies to manage their relationships with customers, including the capture, storage, and analysis of customer information.
: [http://en.wikipedia.org/wiki/Customer_relationship_management Wikipedia Definition]

;CUBS - Church Unit Banking Services
: Introduced in 2010, a worldwide back office system used by administrative offices for financial record-keeping. Over time, all regions will transition from CFAR or LURBS to CUBS.

;CUFS : [[Church Unit Financial Statement]] (Bank Statement) This has been replaced by the Unit Financial Statement.

== D ==
;Disciplinary Council : A council of local leaders and other priesthood holders held to review the inappropriate behavior of a Church member and to decide on appropriate consequences. Councils may also be reconvened after a period of time to see if a member has repented sufficiently to be restored to full fellowship. See chapter 6 of ''Handbook 1: Stake Presidents and Bishops'' for details.

;District : A district is a smaller version of a stake, organized as the parent unit of branches instead of wards. A district may be organized when there are enough branches in an area to allow easy communication and convenient travel to district meetings. A district president presides over the district and reports to the mission presidency.

;District Clerk : Person responsible for all clerical activities in a district.

;District President : The district president presides over the district and is assisted by two counselors. The district president reports to and receives direction from the mission president.

; DIZ - Development Integration Zone

== E ==
; EAD - Enterprise Active Directory
: Active Directory is an implementation of LDAP directory services by Microsoft for use in Windows environments (also known as AD) stores information and settings relating to an organization in a central, organized, accessible database.
: [http://en.wikipedia.org/wiki/Active_Directory Wikipedia Definition]

; EFD - Exploration Findings Document
: This document is used to identify possible solutions for a specific project.

;Elders Quorum : A quorum in the Church is a combination of a class, a fraternity of brethren, and a service organization. An elders quorum is a group of brethren in a ward consisting of up to 96 elders. After this number is reached, the quorum may be divided under direction of the stake president.

;Elders Quorum President : The elders quorum in a ward is presided over by an elders quorum president and two counselors.

;Endowment : Instruction received in the temple pertaining to the purposes and plans of the Lord in creating and peopling the earth and in exalting his children in the life to come.

;Equalized Contribution : Refers to the support from the General Missionary Fund that results in each missionary serving from a specific country contributing the same amount irrespective of where in the world they serve.

;ERC : Employment Resource Center

; ERS - [http://providentliving.org/content/list/0,11664,1962-1,00.html Employment Resource Services]

; EUP - End-User Productivity

== F ==
;Family History Center : A Family History Center is a branch facility of the Family History Library in Salt Lake City. It contains staff to help patrons identify their ancestors through the use of computer programs and microfilms and microfiche that may be ordered from the Family History Library.

;Fast Offering : Fast offerings are funds freely given monthly by members of the Church to help the needy. As a general guideline members fast for two meals and contribute the cash equivalent of the cost of the two meals to the Church. The use of fast offerings is at the discretion of the bishop under the direction of the stake president.

; FCH - Family and Church History Department

;FHC : Family History Center

; FHL - [http://www.familysearch.org/Eng/Library/FHL/frameset_library.asp Family History Library]

;[[Financial Clerk]] : Person responsible for financial matters in the unit.

; FIR - Facility Issue Reporting : The FIR system provides LDS Church leaders, building representatives, and facilities management groups the ability to report and review facility issues electronically. It uses a web interface to streamline reporting, viewing, and resolving of facility issues.

;FIS : Old DOS-based local unit financial software that is no longer used. See [[MLS]] for current software.

;FM Group : Facilities Management Group

; FWIW - For What It's Worth

== G ==
;General Handbook of Instructions : ''Obsolete''. See Handbook.

;[[Geo code]] : A code used to group members into geographic areas, usually to analyze how a unit might be divided.

;GHI : General Handbook of Instructions. ''Obsolete''. See Handbook.

; GIDS - Global Identity Services
: Project to create LDS Sign-in.

; GIS - Geographic Information System
: A geographic information system (GIS) is a system for capturing, storing, analyzing, and managing data and associated attributes which are spatially referenced to the earth.
: [http://en.wikipedia.org/wiki/Gis Wikipedia Definition]

; GSC - [[Global Service Center]]
: The GSC enables Directors of Temporal Affairs and Managing Directors to focus on their most important work by providing efficient transaction processing. They make gospel teachings, resources, and services directly and globally accessible in a self-service, scalable, affordable way. They help with questions and problems related to things such as IT support, Distribution Services, and clerk and leader issues.

; GSD - Global Service Desk
: Former name for the Global Service Center (GSC).

== H ==
;Handbook : The policy manual for administering the Church, consisting of two volumes: ''Handbook 1: Bishops and Stake Presidents'' and ''[http://lds.org/handbook/handbook-2-administering-the-church Handbook 2: Administering the Church]''.

;High Priests Group : The stake president presides over the stake quorum of high priests, made up of all the high priests in the stake. The quorum is divided at the ward level into individual high priests groups.

;High Priests Group Leader : The high priest group in a ward is presided over by a high priest group leader and two assistants. Under the bishopric’s direction, the high priests group leader coordinates temple and family history work in the ward.

;[[Annual History|Historical Specialist]] : Clerk responsible for preparing the [[Annual_History|annual historical reports]].

;Home Teacher : Home teachers are priesthood brethren who are assigned families at the ward level to visit monthly, to help and to strengthen. They are assigned by priesthood leaders.

;Home Teaching : Home teaching is the responsibility of all Melchizedek Priesthood holders and of those who are teachers and priests in the Aaronic Priesthood. As part of their responsibility to watch over the members of the Church, home teachers visit their assigned families at least once each month to teach and strengthen them.

== I ==
; ICS - Information and Communications Systems Department

; IGI - International Genealogical Index
: A list of names of deceased persons for whom temple ordinances have been performed. The most current version is available on the [http://www.familysearch.org/ FamilySearch] Web site.

; IMOS - Internet Mission Office System

;Inactive : A term not officially used in the Church any more. See '''Less Active'''.

;Inactivity

;[[Individual Ordinance Summary]] : A form that contains most of the information on a [[Membership Records|Membership Record]] that can appropriately be given to a member.

;Investigator

;[[Individual Ordinance Summary|IOS]] : Individual Ordinance Summary

; IP - Internet Protocol
: An Internet protocol is a unique address that devices use to identify and communicate with each other on a computer network utilizing the Internet protocol standard (IP).
: [http://en.wikipedia.org/wiki/IP_address Wikipedia Definition]

; IROP - Internal Record Of Purchase : A document used to record internal Church purchase transactions. The most common IROP transactions for Church units are those made at LDS Distribution Services online through the LDS Store, in person, or by telephone. Unit IROPs are transmitted electronically through MLS.

== J ==
; JSMB - [http://www.lds.org/placestovisit/location/0,10634,1872-1-1-1,00.html Joseph Smith Memorial Building]

== K ==
; KB - KnowledgeBase
: A database of articles that help individuals resolve issues.

== L ==
;Less Active : Participating in Church on an irregular basis, which may vary from coming to a few things a year to never coming at all. Members who attend meetings less than once a month are considered less active.

;[[Priesthood Line of Authority|Line of Authority]] : The chain of ordinations for a priesthood holder showing who ordained him to his current office, who ordained the ordainer, and so on back to Jesus Christ.

;LUAAT : Local Unit Area Auditor Trainer

;[[Budget Allowance|LUBA]] : Local Unit Budget Allowance

;LURBS : Local Unit Receipting, Reporting, and Banking System - A back office system used by administrative offices for financial record-keeping outside of North America. It provides various reports for local units, including a [[Ward/Branch Monthly Financial Report|monthly financial report]].

;[[Administrative office#Local Unit Support|LUS]] : Local Unit Support Group - Located in Salt Lake City, Utah, provides support for priesthood leaders in Canada and the United States.

;[[LUWS]] - Local Unit Web Site
: Also called the "Classic Ward and Stake Website," these sites were retired at the end of 2012 and replaced by various tools on LDS.org.

== M ==
;Member : A member of the Church of Jesus Christ of Latter-day Saints is a person eight years old or older who has been baptized and confirmed a member of the Church.

;Membership : The state of being a member of the Church of Jesus Christ of Latter-day Saints, as evidenced by records kept at Church headquarters and in the local unit's MLS. Records are also created for children of members of the Church who are under eight years old; however, these children are not considered members until eight years old, when they are baptized and confirmed.

;[[Membership Clerk]] : Person responsible for maintaining membership records on the members of a unit.

;[[Membership Records|Membership Record]]

;MIS : Old DOS-based local unit membership software. See [[MLS]] for current software.

;[[MLS]] - Member and Leader Services (membership and financial software)
: MLS software is for use by unit leaders, clerks, auxiliary and quorum leaders, and secretaries at both the ward and stake levels. MLS is designed to make Church record-keeping easier and more efficient.

;MRN : Membership Record Number

;[[Administrative office|MSR]] : Membership and Statistical Records Department - the Church department that is commonly known to clerks as the [[administrative office]].

== N ==
;[[NQI]] : Non-quality item - a financial transaction that is not complete after 2 months.

; NOB - North Office Building
: The building that is directly north of the Church Office Building and was previously called the Data Center.

== O ==
;Office : A position in the priesthood (such as priest, elder, and high priest) that has attached to it certain duties, responsibilities, and rights.

;Ordinance : A ceremony performed by the priesthood for a specific purpose. Examples are baptism/confirmation, ordination to the priesthood, and temple sealings. Some are saving ordinances and must be received by members in order to be saved, such as baptism/confirmation. Others may not necessarily be saving ordinances, such as a child blessing.

;Ordination : The bestowal of the priesthood and/or a priesthood office. For example, when a male member is ordained to the office of elder, he receives the Melchizedek Priesthood and is ordained to the office of elder within the Melchizedek Priesthood. Later in life, if he is ordained to the office of high priest, he does not receive the Melchizedek Priesthood again, but is ordained to the office of high priest within the Melchizedek Priesthood. Both examples are considered ordinations.

== P ==
; PAF - Personal Ancestral File
: A Church-produced computer software program that enables people to compile and organize their genealogy on their personal computers. PAF can help members identify ancestors and prepare their names for temple work.

;Patriarch : Patriarch is an office in the Melchizedek Priesthood, and not a calling. A patriarch is recommended by the stake president, sustained in stake conference or stake priesthood meeting, and ordained by the First Presidency or one of the Twelve Apostles or (with written permission from the Twelve) the stake president. Patriarchs give personal blessings to members of the stake (see Patriarchal Blessing).

;Patriarchal Blessing : A blessing given to a member by the patriarch of his or her stake. After the member obtains a recommendation from the bishop, he or she is given a blessing in which the patriarch may give the member's lineage, list weaknesses and strengths, pronounce advice from the Lord concerning the member's future, and any other direction or guidance.

; PC - Personal Computer

; PDD - Project Definition Document

;PEC : Priesthood Executive Committee

;PEF : Perpetual Education Fund

;Perpetual Education Fund

;Personal Priesthood Interview : ''Obsolete''. See Priesthood Interview

;Physical Facilities Representative : A local priesthood holder responsible for the physical status of a meetinghouse.

;PI : Priesthood Interview

; PIX
: Church-managed Cisco PIX firewall used primarily for FHC Internet connections.

;PLT : Priesthood Leadership Travel

;PPI : Personal Priesthood Interview. ''Obsolete''. See Priesthood Interview

;Presiding Bishop : A General Authority of the Church. The Presiding Bishop and his counselors serve under the direction of the First Presidency to administer the temporal affairs of the Church.

; PRF - Pedigree Resource File
: A file of lineage-linked data submitted by both members and nonmembers through the [http://www.familysearch.org/ FamilySearch] Web site. The master index is available online and the entire file is available on CD. The Pedigree Resource File is the successor to the Ancestral File.

;Priesthood Executive Committee

;Priesthood Interview : A private stewardship meeting between a priesthood leader and a person who reports to him

== Q ==
;[[Quarterly Report]] : A report of member attendance and other key statistics submitted by wards to the stake and the Church each quarter

== R ==
;Recommend

;Record

;Record Keeping

;REFIS

;Relief Society : The women's organization of the Church, organized by Joseph Smith in 1842, dedicated to "the exercise of all benevolent purposes." The Relief Society provides Sunday gospel instruction, other Relief Society meetings, visiting teaching, and welfare and compassionate service opportunities.

;RS : Relief Society

; RSS - Really Simple Syndication
: RSS is a Web-feed format that is used to publish frequently updated digital content to consumers who use RSS aggregators to notify them of updates.
: [http://en.wikipedia.org/wiki/RSS Wikipedia Definition]

== S ==
; SAV - Symantec Anti-Virus : An anti-virus software formerly used on Church-owned computers, such as those used in stakes and wards. All computers should now have the Sophos anti-virus software.

; SA - Single Adult
: A single member above the age of 30. See also YSA.

; SDK - Software Development Kit
: SDK is typically a set of development tools that allows a software engineer to create applications for a certain software package, software framework, hardware platform, computer system, video game console, operating system, and more.
: [http://en.wikipedia.org/wiki/Software_development_kit Wikipedia Definition]

; SEO - Search Engine Optimization

; SERP - Search Engine Results Page

;Set Apart

;SFS : ''Obsolete''. See Consolidated Financial Statement.

; SOAP - Simple Object Access Protocol
: A protocol for exchanging XML-based messages over a computer network, normally using HTTP.
: [http://en.wikipedia.org/wiki/SOAP Wikipedia Definition]

; Sophos Anti-Virus : An anti-virus software currently used on Church-owned computers, such as those used in stakes and wards.

; SORT
: An internal conference hosted by ICS for technical Church employees.

; SRD - Solutions Requirement Document
: The SRD is used to identify the business requirements and business case for a proposed technology project.

; SSH - Secure Shell
: SSH is a communication system that uses public-key cryptography to establish a secure connection between remote computers.
: [http://en.wikipedia.org/wiki/Ssh Wikipedia Definition]

;Stake

;[[Stake Clerk]] : Person responsible for all clerical activities in a stake.

;Stake President : The stake president presides over the stake and is assisted by two counselors. The stake president reports to and receives direction from the presidency of the Seventy or from the Area President.

;[[Stake Technology Specialist]] : Person responsible for the technology assets of the stake and each ward in the stake.

;[[Statistical Clerk]] : Person responsible for collecting and preparing the [[Quarterly Report]].

== T ==

;[[Desktop Management Software|TEM]] - Tivoli Endpoint Manager
: Replaced LANDesk as the official software CHQ uses to centrally manage and secure the global fleet of Church-owned computers. TEM will install and utilize the BES Client service.

;Temple

;Temple Ordinances

;Temple Recommend

;Temporal

;Tithing

;Tithing Settlement

== U ==
;Unit : A congregation or other function in the Church that is responsible for its budget. Wards, Stakes, Branches, Districts, Family History Centers, etc., are all examples of Units.

;Unit Financial Statement : the Unit Financial Statement has replaced the old Church Unit Financial Statement.

== V ==
;Visiting Teacher

;Visiting Teaching

; VoIP - Voice Over Internet Protocol
: The technology that allows voice communication (such as telephone) over a network instead of through traditional phone lines. The Church has deployed VoIP in several locations indlucing BYU, the North Office Building, the Triad Center, and Ghana.
: [http://en.wikipedia.org/wiki/Voip Wikipedia Definition]

; VPN - Virtual Private Network
: VPN is a private communications network often used within a company, or by several companies or organization, to communication confidentially over a publicly accessible network.
: [http://en.wikipedia.org/wiki/Vpn Wikipedia Definition]

== W ==
;Ward

;Ward Budget

;[[Ward Clerk]] : Person responsible for all clerical activities in a ward.

;Ward Council

;Ward Welfare Committee

;Welfare

;Welfare Services

== Y ==
;YM - Young Men
:Single male members between the ages of 12-18.

;YSA - Young Single Adult
:A single member between the ages of 18-30. See also SA.

;YW - Young Women
:Single female members between the ages of 12-18.

[[Category:Help]]

Save Local Unit Documents in Church Network Manager

2026-07-17T17:17:22Z

Ericjamee:

= '''Save Local Unit Documents in Church Network Manager''' =
Technology specialists, clerks and bishopric members can upload '''Local Unit Documents''' to the '''Documents''' feature in Church Network Manager. This feature provides a secure, centralized location for storing information that supports the ongoing operation and maintenance of meetinghouse technology. Local Unit Documents remain associated with the property, allowing future technology specialists to access and maintain the documentation as responsibilities change over time.

=== '''Why Use Local Unit Documents?''' ===
As a technology specialist, you are responsible for supporting and maintaining a variety of meetinghouse technology. Whenever possible, issues can be resolved more efficiently if the information you need is available remotely rather than requiring a visit to the meetinghouse.

The '''Documents''' feature in Church Network Manager allows you to store '''Local Unit Documents''' in one secure, centralized location. You can upload the information that is most valuable for supporting your assigned buildings, making it easier for both current and future technology specialists to locate important records.

Examples of useful documents include:

* Network diagrams and rack layouts
* Technology inventories
* Internet service provider information
* Equipment manuals and vendor documentation
* Photographs of equipment installations
* Photos showing serial numbers, model numbers, and part numbers for computers, networking equipment, printers, cameras, displays, and other technology devices

Having this information available remotely can simplify many support tasks. For example, you can reference a device's serial number while working with a vendor's support website, verify model or part numbers before ordering replacement equipment, or provide accurate information when coordinating repairs with the Facilities Manager—all without traveling to the meetinghouse.

Keeping this documentation current also preserves valuable local knowledge, making it easier for future technology specialists to understand the meetinghouse technology environment and continue providing effective support.

For a visual walkthrough of this process, see [https://www.iorad.com/player/2744167/Save-Local-Unit-Documents-in-Church-Network-Manager?#trysteps-1 '''Save Local Unit Documents in Church Network Manager'''].
----

=== '''Upload a Local Unit Document''' ===

===== '''Step 1: Open Church Network Manager''' =====

# Sign in to '''[http://cnm.churchofjesuschrist.org/ Church Network Manager].'''

===== '''Step 2: Select the Property''' =====

# Select the '''Property''' that the document will reference.

===== '''Step 3: In the Documents Section''' =====

# Select '''Manage Documents'''.

===== '''Step 4: Open the Menu''' =====

# Select the '''Menu'''.

===== '''Step 5: Add Document''' =====

# Select '''Add Document'''.

===== '''Step 6: Select the File''' =====

# Browse to the document on your computer.
# Select the file.
# Select '''Open'''.

===== '''Step 7: Enter a Short Name''' =====

# Enter a short, descriptive name for the document.

===== '''Step 8: Complete the Document Information''' =====

# (Optional) Enter a '''Description''' that explains the document's purpose.
# If applicable, select the appropriate document category.

===== '''Step 9: Add a Custom Tag (Optional)''' =====

# Enter a '''Custom Tag''' for the document.
# Select '''Add Tag'''.

===== '''Step 10: Save Document''' =====

# When complete, select '''Save'''.

===== '''Step 11: Verify the Upload''' =====

# Verify that the document appears in the '''Documents''' list.

----

=== '''Recommended Documents''' ===
Consider storing Local Unit Documents such as:

* Network diagrams and rack layouts
* Technology inventories
* Internet service provider information
* Cabling documentation
* Equipment manuals and vendor documentation
* Equipment installation photographs
* Photos showing serial numbers, model numbers, and part numbers for computers, networking equipment, printers, cameras, displays, and other technology devices
* Wireless access point locations
* Audio/video system documentation
* Maintenance notes and equipment replacement history

----

=== '''Protect Personal Information''' ===
Only upload documents that support the operation and maintenance of meetinghouse technology.

Do '''not''' upload documents that contain personal or confidential information, including:

* Member names
* Phone or mobile numbers
* Email addresses
* Messaging account information (such as WhatsApp or Signal)
* Home addresses
* Membership record numbers
* Financial information
* Passwords, passphrases, or security codes
* Personal login credentials
* Any other personally identifiable information (PII)

If a document contains both technology information and personal information, remove or redact the personal information before uploading the document.

When documenting equipment, include information such as model numbers, serial numbers, part numbers, network diagrams, equipment locations, and installation photographs—but avoid including information that identifies individual members or leaders.
----

=== '''Best Practices''' ===

* Use clear, descriptive document titles.
* Include dates on diagrams and inventories so others know when they were last updated.
* Update documentation whenever equipment is installed, replaced, relocated, or removed.
* Replace outdated documents with current versions whenever possible.
* Capture photographs that clearly show equipment placement, cable connections, serial numbers, model numbers, and part numbers.
* Store Local Unit Documents in the '''Documents''' feature of Church Network Manager instead of on personal computers or removable media whenever possible.
* Follow the guidance in '''Protect Personal Information''' before uploading any document.

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

===== '''Who can view Local Unit Documents?''' =====
Only authorized users with access to the property in Church Network Manager can view uploaded documents.

===== '''What kinds of documents should I upload?''' =====
Upload Local Unit Documents that help install, maintain, troubleshoot, or replace meetinghouse technology equipment.

===== '''Should I upload documents containing member information?''' =====
No. Do not upload documents containing confidential member information, financial information, passwords, or other sensitive personal data.

===== '''Can I replace outdated documents?''' =====
Yes. Keep documentation current by replacing outdated versions whenever equipment or configurations change.

===== '''Why should I use Local Unit Documents instead of storing files locally?''' =====
The '''Documents''' feature provides a centralized repository that remains with the property rather than an individual technology specialist. Authorized users can securely access Local Unit Documents from any location, making it easier to troubleshoot issues, identify equipment, coordinate repairs, and preserve important knowledge as technology specialists change callings.

Save Local Unit Documents in Church Network Manager

2026-07-17T17:16:14Z

Ericjamee:

= '''Save Local Unit Documents in Church Network Manager''' =
Technology specialists, clerks and bishopric members can upload '''Local Unit Documents''' to the '''Documents''' feature in Church Network Manager. This feature provides a secure, centralized location for storing information that supports the ongoing operation and maintenance of meetinghouse technology. Local Unit Documents remain associated with the property, allowing future technology specialists to access and maintain the documentation as responsibilities change over time.

=== '''Why Use Local Unit Documents?''' ===
As a technology specialist, you are responsible for supporting and maintaining a variety of meetinghouse technology. Whenever possible, issues can be resolved more efficiently if the information you need is available remotely rather than requiring a visit to the meetinghouse.

The '''Documents''' feature in Church Network Manager allows you to store '''Local Unit Documents''' in one secure, centralized location. You can upload the information that is most valuable for supporting your assigned buildings, making it easier for both current and future technology specialists to locate important records.

Examples of useful documents include:

* Network diagrams and rack layouts
* Technology inventories
* Internet service provider information
* Equipment manuals and vendor documentation
* Photographs of equipment installations
* Photos showing serial numbers, model numbers, and part numbers for computers, networking equipment, printers, cameras, displays, and other technology devices

Having this information available remotely can simplify many support tasks. For example, you can reference a device's serial number while working with a vendor's support website, verify model or part numbers before ordering replacement equipment, or provide accurate information when coordinating repairs with the Facilities Manager—all without traveling to the meetinghouse.

Keeping this documentation current also preserves valuable local knowledge, making it easier for future technology specialists to understand the meetinghouse technology environment and continue providing effective support.

For a visual walkthrough of this process, see [https://www.iorad.com/player/2744167/Save-Local-Unit-Documents-in-Church-Network-Manager?#trysteps-1 Save Local Unit Documents in Church Network Manager].
----

=== '''Upload a Local Unit Document''' ===

===== '''Step 1: Open Church Network Manager''' =====

# Sign in to [http://cnm.churchofjesuschrist.org/ Church Network Manager].

===== '''Step 2: Select the Property''' =====

# Select the '''Property''' that the document will reference.

===== '''Step 3: In the Documents Section''' =====

# Select '''Manage Documents'''.

===== '''Step 4: Open the Menu''' =====

# Select the '''Menu'''.

===== '''Step 5: Add Document''' =====

# Select '''Add Document'''.

===== '''Step 6: Select the File''' =====

# Browse to the document on your computer.
# Select the file.
# Select '''Open'''.

===== '''Step 7: Enter a Short Name''' =====

# Enter a short, descriptive name for the document.

===== '''Step 8: Complete the Document Information''' =====

# (Optional) Enter a '''Description''' that explains the document's purpose.
# If applicable, select the appropriate document category.

===== '''Step 9: Add a Custom Tag (Optional)''' =====

# Enter a '''Custom Tag''' for the document.
# Select '''Add Tag'''.

===== '''Step 10: Save Document''' =====

# When complete, select '''Save'''.

===== '''Step 11: Verify the Upload''' =====

# Verify that the document appears in the '''Documents''' list.

----

=== '''Recommended Documents''' ===
Consider storing Local Unit Documents such as:

* Network diagrams and rack layouts
* Technology inventories
* Internet service provider information
* Cabling documentation
* Equipment manuals and vendor documentation
* Equipment installation photographs
* Photos showing serial numbers, model numbers, and part numbers for computers, networking equipment, printers, cameras, displays, and other technology devices
* Wireless access point locations
* Audio/video system documentation
* Maintenance notes and equipment replacement history

----

=== '''Protect Personal Information''' ===
Only upload documents that support the operation and maintenance of meetinghouse technology.

Do '''not''' upload documents that contain personal or confidential information, including:

* Member names
* Phone or mobile numbers
* Email addresses
* Messaging account information (such as WhatsApp or Signal)
* Home addresses
* Membership record numbers
* Financial information
* Passwords, passphrases, or security codes
* Personal login credentials
* Any other personally identifiable information (PII)

If a document contains both technology information and personal information, remove or redact the personal information before uploading the document.

When documenting equipment, include information such as model numbers, serial numbers, part numbers, network diagrams, equipment locations, and installation photographs—but avoid including information that identifies individual members or leaders.
----

=== '''Best Practices''' ===

* Use clear, descriptive document titles.
* Include dates on diagrams and inventories so others know when they were last updated.
* Update documentation whenever equipment is installed, replaced, relocated, or removed.
* Replace outdated documents with current versions whenever possible.
* Capture photographs that clearly show equipment placement, cable connections, serial numbers, model numbers, and part numbers.
* Store Local Unit Documents in the '''Documents''' feature of Church Network Manager instead of on personal computers or removable media whenever possible.
* Follow the guidance in '''Protect Personal Information''' before uploading any document.

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

===== '''Who can view Local Unit Documents?''' =====
Only authorized users with access to the property in Church Network Manager can view uploaded documents.

===== '''What kinds of documents should I upload?''' =====
Upload Local Unit Documents that help install, maintain, troubleshoot, or replace meetinghouse technology equipment.

===== '''Should I upload documents containing member information?''' =====
No. Do not upload documents containing confidential member information, financial information, passwords, or other sensitive personal data.

===== '''Can I replace outdated documents?''' =====
Yes. Keep documentation current by replacing outdated versions whenever equipment or configurations change.

===== '''Why should I use Local Unit Documents instead of storing files locally?''' =====
The '''Documents''' feature provides a centralized repository that remains with the property rather than an individual technology specialist. Authorized users can securely access Local Unit Documents from any location, making it easier to troubleshoot issues, identify equipment, coordinate repairs, and preserve important knowledge as technology specialists change callings.

CDOL Description

2026-07-15T20:12:09Z

Ericjamee: Rewritten by copilot Help Content Creation

= Church Directory of Organizations and Leaders (CDOL) Overview =
{{Template:CDOL}}

== Quick Summary ==
The Church Directory of Organizations and Leaders (CDOL) is a directory that contains information about Church organizations and leaders worldwide. Authorized users can view organization and leadership information, search for units and leaders, create directories and reports, and access tools that support Church administration.

== Product Purpose ==

=== Why does CDOL exist? ===
CDOL provides a centralized source for organization and leadership information across the Church, helping leaders, employees, and administrators locate contact information, understand organizational relationships, and manage administrative responsibilities.

'''Problem:''' Organization and leadership information is distributed across thousands of Church units worldwide.

'''Solution:''' CDOL centralizes organization, leader, and unit information in a single directory that can be accessed based on assigned permissions.

== Who Is This For? ==
'''Primary Users'''

* General Authorities
* Church Headquarters personnel
* Area administration personnel
* Local priesthood leaders
* Church managers and employees

'''Permissions Required'''

* Access is based on assigned rights and responsibilities.

== Key Features ==
Authorized users may be able to:

* View organization and leader information, including contact details and dates
* Explore organizational relationships between units
* Find Church department contact information
* Create customized directories
* Search for organizations and leaders
* Save searches
* View local time information for units
* Generate reports
* Locate wards and stakes by address
* View unit boundary maps (where available)
* View standard and custom leadership positions within authorized units

== Administrative Functions ==
Users with administrative permissions may also:

* Add, edit, and remove directory information
* Manage organizations, positions, and organizational structures
* Create new organization and position types as authorized

[[Category: CDOL]]

Broadcasting Events/church-meetings-overview

2026-07-15T20:05:59Z

Ericjamee: Updated with copilot Help Content Creation

= Church Meetings Overview =
Technology Specialists help ensure Church meetings run smoothly by preparing and supporting the technology needed by leaders, teachers, and participants. Careful planning, testing, and troubleshooting can reduce distractions and help maintain a positive meeting experience.

As you prepare for meetings, coordinate with leaders and teachers to understand their technology needs and determine which rooms will be used. Because technology capabilities vary by room, advance planning helps ensure the appropriate equipment is available and functioning properly.<blockquote>'''Note:''' Encourage presenters to download media before the meeting. Meetinghouse internet connectivity should not be relied upon for streaming media during meetings.</blockquote>Technology may be used in a variety of meetings, including sacrament meetings, conferences, baptisms, funerals, classes, devotionals, interviews, and other Church events.

== Technology Specialist Tasks ==
Depending on the meeting, you may be asked to:

* Set up video displays for presentations and media playback
* Configure mobile device or computer connections
* Set up and test microphones
* Configure audio and video distribution
* Prepare audio/video backup solutions
* Support presentation playback
* Verify internet connectivity and performance
* Set up live-streaming or virtual meeting solutions

== Additional Considerations for Non-Chapel Meetings ==
When meetings are held outside the chapel, determine the appropriate:

* Display technology
* Audio distribution solution
* Room setup requirements

== Related Resources ==

*Setting up video display for [[Displaying Mobile Devices|mobile devices]]
* [[Using Microphones|Using microphones]]
* [https://www.churchofjesuschrist.org/tools/help/av-distribution-overview?lang=eng Audio/Video (AV) distribution]
* [[Testing and Backup|Audio/Video backup system]]
* [https://www.churchofjesuschrist.org/tools/help/media-playback-overview?lang=eng Playback of a presentation]
* [[Internet Speed Tests|Verifying Church internet speeds/connection]]
* [https://www.churchofjesuschrist.org/tools/help/virtual-meetings-overview?lang=eng Setting up live streams]

Broadcasting Events/stake-conference-overview

2026-07-15T19:56:05Z

Ericjamee: Used copilot "Help Content Creation" to alter the original article. Most of the content was left the same, but format was improved

= Broadcasting Stake Conference Overview =
Stake conference is a meeting of stake members held to strengthen testimonies, receive instruction, and conduct stake business. Most stakes hold two stake conferences each year under the direction of the Quorum of the Twelve Apostles.

As a Technology Specialist, you support stake leadership by planning, setting up, and operating the technology needed for stake conference. Several weeks before the conference, meet with the stake clerk or a member of the stake presidency to understand their goals for the meeting and identify any technology requirements. Your preparation and support can help reduce stress for stake leaders and contribute to a successful experience for members.

Common technologies used during stake conference include audio and video distribution, digital media devices, webcast equipment, video cameras, and accessibility technologies.

== Technology Specialist Tasks ==
Before stake conference, review the following topics:

*[[Using Microphones|Set up microphones]]
* [[Connecting Devices to AV System|Set up a projector]]
* [https://www.churchofjesuschrist.org/tools/help/av-distribution-overview?lang=eng Set up audio and video throughout the meetinghouse]
* [[Using Accessibility Technology|Configure interpretation devices]]
* [[Disabling Wireless Access|Disable wireless access]]
* [[Testing and Backup|Run tests and set up backups]]

== FMG Support ==
Facilities Management Group (FMG) personnel may assist by:

* Providing equipment not already available in the meetinghouse
* Supplying temporary technology resources when needed, such as webcast equipment, additional microphones, enhanced bandwidth, or alternative firewall solutions

Save Local Unit Documents in Church Network Manager

2026-07-15T19:13:59Z

Ericjamee: /* Step 1: Open Church Network Manager */

= '''Save Local Unit Documents in Church Network Manager''' =
Technology specialists, clerks and bishopric members can upload '''Local Unit Documents''' to the '''Documents''' feature in Church Network Manager. This feature provides a secure, centralized location for storing information that supports the ongoing operation and maintenance of meetinghouse technology. Local Unit Documents remain associated with the property, allowing future technology specialists to access and maintain the documentation as responsibilities change over time.

=== '''Why Use Local Unit Documents?''' ===
As a technology specialist, you are responsible for supporting and maintaining a variety of meetinghouse technology. Whenever possible, issues can be resolved more efficiently if the information you need is available remotely rather than requiring a visit to the meetinghouse.

The '''Documents''' feature in Church Network Manager allows you to store '''Local Unit Documents''' in one secure, centralized location. You can upload the information that is most valuable for supporting your assigned buildings, making it easier for both current and future technology specialists to locate important records.

Examples of useful documents include:

* Network diagrams and rack layouts
* Technology inventories
* Internet service provider information
* Equipment manuals and vendor documentation
* Photographs of equipment installations
* Photos showing serial numbers, model numbers, and part numbers for computers, networking equipment, printers, cameras, displays, and other technology devices

Having this information available remotely can simplify many support tasks. For example, you can reference a device's serial number while working with a vendor's support website, verify model or part numbers before ordering replacement equipment, or provide accurate information when coordinating repairs with the Facilities Manager—all without traveling to the meetinghouse.

Keeping this documentation current also preserves valuable local knowledge, making it easier for future technology specialists to understand the meetinghouse technology environment and continue providing effective support.

For a visual walkthrough of this process, see '''[https://www.iorad.com/player/2744167/Save-Local-Unit-Documents-in-Church-Network-Manager?#trysteps-1 Save Local Unit Documents in Church Network Manager]'''.
----

=== '''Upload a Local Unit Document''' ===

===== '''Step 1: Open Church Network Manager''' =====

# Sign in to '''[http://cnm.churchofjesuschrist.org/ Church Network Manager]'''.

===== '''Step 2: Select the Property''' =====

# Select the '''Property''' that the document will reference.

===== '''Step 3: In the Documents Section''' =====

# Select '''Manage Documents'''.

===== '''Step 4: Open the Menu''' =====

# Select the '''Menu'''.

===== '''Step 5: Add Document''' =====

# Select '''Add Document'''.

===== '''Step 6: Select the File''' =====

# Browse to the document on your computer.
# Select the file.
# Select '''Open'''.

===== '''Step 7: Enter a Short Name''' =====

# Enter a short, descriptive name for the document.

===== '''Step 8: Complete the Document Information''' =====

# (Optional) Enter a '''Description''' that explains the document's purpose.
# If applicable, select the appropriate document category.

===== '''Step 9: Add a Custom Tag (Optional)''' =====

# Enter a '''Custom Tag''' for the document.
# Select '''Add Tag'''.

===== '''Step 10: Save Document''' =====

# When complete, select '''Save'''.

===== '''Step 11: Verify the Upload''' =====

# Verify that the document appears in the '''Documents''' list.

----

=== '''Recommended Documents''' ===
Consider storing Local Unit Documents such as:

* Network diagrams and rack layouts
* Technology inventories
* Internet service provider information
* Cabling documentation
* Equipment manuals and vendor documentation
* Equipment installation photographs
* Photos showing serial numbers, model numbers, and part numbers for computers, networking equipment, printers, cameras, displays, and other technology devices
* Wireless access point locations
* Audio/video system documentation
* Maintenance notes and equipment replacement history

----

=== '''Protect Personal Information''' ===
Only upload documents that support the operation and maintenance of meetinghouse technology.

Do '''not''' upload documents that contain personal or confidential information, including:

* Member names
* Phone or mobile numbers
* Email addresses
* Messaging account information (such as WhatsApp or Signal)
* Home addresses
* Membership record numbers
* Financial information
* Passwords, passphrases, or security codes
* Personal login credentials
* Any other personally identifiable information (PII)

If a document contains both technology information and personal information, remove or redact the personal information before uploading the document.

When documenting equipment, include information such as model numbers, serial numbers, part numbers, network diagrams, equipment locations, and installation photographs—but avoid including information that identifies individual members or leaders.
----

=== '''Best Practices''' ===

* Use clear, descriptive document titles.
* Include dates on diagrams and inventories so others know when they were last updated.
* Update documentation whenever equipment is installed, replaced, relocated, or removed.
* Replace outdated documents with current versions whenever possible.
* Capture photographs that clearly show equipment placement, cable connections, serial numbers, model numbers, and part numbers.
* Store Local Unit Documents in the '''Documents''' feature of Church Network Manager instead of on personal computers or removable media whenever possible.
* Follow the guidance in '''Protect Personal Information''' before uploading any document.

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

===== '''Who can view Local Unit Documents?''' =====
Only authorized users with access to the property in Church Network Manager can view uploaded documents.

===== '''What kinds of documents should I upload?''' =====
Upload Local Unit Documents that help install, maintain, troubleshoot, or replace meetinghouse technology equipment.

===== '''Should I upload documents containing member information?''' =====
No. Do not upload documents containing confidential member information, financial information, passwords, or other sensitive personal data.

===== '''Can I replace outdated documents?''' =====
Yes. Keep documentation current by replacing outdated versions whenever equipment or configurations change.

===== '''Why should I use Local Unit Documents instead of storing files locally?''' =====
The '''Documents''' feature provides a centralized repository that remains with the property rather than an individual technology specialist. Authorized users can securely access Local Unit Documents from any location, making it easier to troubleshoot issues, identify equipment, coordinate repairs, and preserve important knowledge as technology specialists change callings.

Save Local Unit Documents in Church Network Manager

2026-07-15T19:12:54Z

Ericjamee: /* Save Local Unit Documents in Church Network Manager */

= '''Save Local Unit Documents in Church Network Manager''' =
Technology specialists, clerks and bishopric members can upload '''Local Unit Documents''' to the '''Documents''' feature in Church Network Manager. This feature provides a secure, centralized location for storing information that supports the ongoing operation and maintenance of meetinghouse technology. Local Unit Documents remain associated with the property, allowing future technology specialists to access and maintain the documentation as responsibilities change over time.

=== '''Why Use Local Unit Documents?''' ===
As a technology specialist, you are responsible for supporting and maintaining a variety of meetinghouse technology. Whenever possible, issues can be resolved more efficiently if the information you need is available remotely rather than requiring a visit to the meetinghouse.

The '''Documents''' feature in Church Network Manager allows you to store '''Local Unit Documents''' in one secure, centralized location. You can upload the information that is most valuable for supporting your assigned buildings, making it easier for both current and future technology specialists to locate important records.

Examples of useful documents include:

* Network diagrams and rack layouts
* Technology inventories
* Internet service provider information
* Equipment manuals and vendor documentation
* Photographs of equipment installations
* Photos showing serial numbers, model numbers, and part numbers for computers, networking equipment, printers, cameras, displays, and other technology devices

Having this information available remotely can simplify many support tasks. For example, you can reference a device's serial number while working with a vendor's support website, verify model or part numbers before ordering replacement equipment, or provide accurate information when coordinating repairs with the Facilities Manager—all without traveling to the meetinghouse.

Keeping this documentation current also preserves valuable local knowledge, making it easier for future technology specialists to understand the meetinghouse technology environment and continue providing effective support.

For a visual walkthrough of this process, see '''[https://www.iorad.com/player/2744167/Save-Local-Unit-Documents-in-Church-Network-Manager?#trysteps-1 Save Local Unit Documents in Church Network Manager]'''.
----

=== '''Upload a Local Unit Document''' ===

===== '''Step 1: Open Church Network Manager''' =====

# Sign in to '''Church Network Manager'''.

===== '''Step 2: Select the Property''' =====

# Select the '''Property''' that the document will reference.

===== '''Step 3: In the Documents Section''' =====

# Select '''Manage Documents'''.

===== '''Step 4: Open the Menu''' =====

# Select the '''Menu'''.

===== '''Step 5: Add Document''' =====

# Select '''Add Document'''.

===== '''Step 6: Select the File''' =====

# Browse to the document on your computer.
# Select the file.
# Select '''Open'''.

===== '''Step 7: Enter a Short Name''' =====

# Enter a short, descriptive name for the document.

===== '''Step 8: Complete the Document Information''' =====

# (Optional) Enter a '''Description''' that explains the document's purpose.
# If applicable, select the appropriate document category.

===== '''Step 9: Add a Custom Tag (Optional)''' =====

# Enter a '''Custom Tag''' for the document.
# Select '''Add Tag'''.

===== '''Step 10: Save Document''' =====

# When complete, select '''Save'''.

===== '''Step 11: Verify the Upload''' =====

# Verify that the document appears in the '''Documents''' list.

----

=== '''Recommended Documents''' ===
Consider storing Local Unit Documents such as:

* Network diagrams and rack layouts
* Technology inventories
* Internet service provider information
* Cabling documentation
* Equipment manuals and vendor documentation
* Equipment installation photographs
* Photos showing serial numbers, model numbers, and part numbers for computers, networking equipment, printers, cameras, displays, and other technology devices
* Wireless access point locations
* Audio/video system documentation
* Maintenance notes and equipment replacement history

----

=== '''Protect Personal Information''' ===
Only upload documents that support the operation and maintenance of meetinghouse technology.

Do '''not''' upload documents that contain personal or confidential information, including:

* Member names
* Phone or mobile numbers
* Email addresses
* Messaging account information (such as WhatsApp or Signal)
* Home addresses
* Membership record numbers
* Financial information
* Passwords, passphrases, or security codes
* Personal login credentials
* Any other personally identifiable information (PII)

If a document contains both technology information and personal information, remove or redact the personal information before uploading the document.

When documenting equipment, include information such as model numbers, serial numbers, part numbers, network diagrams, equipment locations, and installation photographs—but avoid including information that identifies individual members or leaders.
----

=== '''Best Practices''' ===

* Use clear, descriptive document titles.
* Include dates on diagrams and inventories so others know when they were last updated.
* Update documentation whenever equipment is installed, replaced, relocated, or removed.
* Replace outdated documents with current versions whenever possible.
* Capture photographs that clearly show equipment placement, cable connections, serial numbers, model numbers, and part numbers.
* Store Local Unit Documents in the '''Documents''' feature of Church Network Manager instead of on personal computers or removable media whenever possible.
* Follow the guidance in '''Protect Personal Information''' before uploading any document.

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

===== '''Who can view Local Unit Documents?''' =====
Only authorized users with access to the property in Church Network Manager can view uploaded documents.

===== '''What kinds of documents should I upload?''' =====
Upload Local Unit Documents that help install, maintain, troubleshoot, or replace meetinghouse technology equipment.

===== '''Should I upload documents containing member information?''' =====
No. Do not upload documents containing confidential member information, financial information, passwords, or other sensitive personal data.

===== '''Can I replace outdated documents?''' =====
Yes. Keep documentation current by replacing outdated versions whenever equipment or configurations change.

===== '''Why should I use Local Unit Documents instead of storing files locally?''' =====
The '''Documents''' feature provides a centralized repository that remains with the property rather than an individual technology specialist. Authorized users can securely access Local Unit Documents from any location, making it easier to troubleshoot issues, identify equipment, coordinate repairs, and preserve important knowledge as technology specialists change callings.

Save Local Unit Documents in Church Network Manager

2026-07-15T19:12:27Z

Ericjamee:

== '''Save Local Unit Documents in Church Network Manager''' ==
Technology specialists, clerks and bishopric members can upload '''Local Unit Documents''' to the '''Documents''' feature in Church Network Manager. This feature provides a secure, centralized location for storing information that supports the ongoing operation and maintenance of meetinghouse technology. Local Unit Documents remain associated with the property, allowing future technology specialists to access and maintain the documentation as responsibilities change over time.

=== '''Why Use Local Unit Documents?''' ===
As a technology specialist, you are responsible for supporting and maintaining a variety of meetinghouse technology. Whenever possible, issues can be resolved more efficiently if the information you need is available remotely rather than requiring a visit to the meetinghouse.

The '''Documents''' feature in Church Network Manager allows you to store '''Local Unit Documents''' in one secure, centralized location. You can upload the information that is most valuable for supporting your assigned buildings, making it easier for both current and future technology specialists to locate important records.

Examples of useful documents include:

* Network diagrams and rack layouts
* Technology inventories
* Internet service provider information
* Equipment manuals and vendor documentation
* Photographs of equipment installations
* Photos showing serial numbers, model numbers, and part numbers for computers, networking equipment, printers, cameras, displays, and other technology devices

Having this information available remotely can simplify many support tasks. For example, you can reference a device's serial number while working with a vendor's support website, verify model or part numbers before ordering replacement equipment, or provide accurate information when coordinating repairs with the Facilities Manager—all without traveling to the meetinghouse.

Keeping this documentation current also preserves valuable local knowledge, making it easier for future technology specialists to understand the meetinghouse technology environment and continue providing effective support.

For a visual walkthrough of this process, see '''[https://www.iorad.com/player/2744167/Save-Local-Unit-Documents-in-Church-Network-Manager?#trysteps-1 Save Local Unit Documents in Church Network Manager]'''.
----

=== '''Upload a Local Unit Document''' ===

===== '''Step 1: Open Church Network Manager''' =====

# Sign in to '''Church Network Manager'''.

===== '''Step 2: Select the Property''' =====

# Select the '''Property''' that the document will reference.

===== '''Step 3: In the Documents Section''' =====

# Select '''Manage Documents'''.

===== '''Step 4: Open the Menu''' =====

# Select the '''Menu'''.

===== '''Step 5: Add Document''' =====

# Select '''Add Document'''.

===== '''Step 6: Select the File''' =====

# Browse to the document on your computer.
# Select the file.
# Select '''Open'''.

===== '''Step 7: Enter a Short Name''' =====

# Enter a short, descriptive name for the document.

===== '''Step 8: Complete the Document Information''' =====

# (Optional) Enter a '''Description''' that explains the document's purpose.
# If applicable, select the appropriate document category.

===== '''Step 9: Add a Custom Tag (Optional)''' =====

# Enter a '''Custom Tag''' for the document.
# Select '''Add Tag'''.

===== '''Step 10: Save Document''' =====

# When complete, select '''Save'''.

===== '''Step 11: Verify the Upload''' =====

# Verify that the document appears in the '''Documents''' list.

----

=== '''Recommended Documents''' ===
Consider storing Local Unit Documents such as:

* Network diagrams and rack layouts
* Technology inventories
* Internet service provider information
* Cabling documentation
* Equipment manuals and vendor documentation
* Equipment installation photographs
* Photos showing serial numbers, model numbers, and part numbers for computers, networking equipment, printers, cameras, displays, and other technology devices
* Wireless access point locations
* Audio/video system documentation
* Maintenance notes and equipment replacement history

----

=== '''Protect Personal Information''' ===
Only upload documents that support the operation and maintenance of meetinghouse technology.

Do '''not''' upload documents that contain personal or confidential information, including:

* Member names
* Phone or mobile numbers
* Email addresses
* Messaging account information (such as WhatsApp or Signal)
* Home addresses
* Membership record numbers
* Financial information
* Passwords, passphrases, or security codes
* Personal login credentials
* Any other personally identifiable information (PII)

If a document contains both technology information and personal information, remove or redact the personal information before uploading the document.

When documenting equipment, include information such as model numbers, serial numbers, part numbers, network diagrams, equipment locations, and installation photographs—but avoid including information that identifies individual members or leaders.
----

=== '''Best Practices''' ===

* Use clear, descriptive document titles.
* Include dates on diagrams and inventories so others know when they were last updated.
* Update documentation whenever equipment is installed, replaced, relocated, or removed.
* Replace outdated documents with current versions whenever possible.
* Capture photographs that clearly show equipment placement, cable connections, serial numbers, model numbers, and part numbers.
* Store Local Unit Documents in the '''Documents''' feature of Church Network Manager instead of on personal computers or removable media whenever possible.
* Follow the guidance in '''Protect Personal Information''' before uploading any document.

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

===== '''Who can view Local Unit Documents?''' =====
Only authorized users with access to the property in Church Network Manager can view uploaded documents.

===== '''What kinds of documents should I upload?''' =====
Upload Local Unit Documents that help install, maintain, troubleshoot, or replace meetinghouse technology equipment.

===== '''Should I upload documents containing member information?''' =====
No. Do not upload documents containing confidential member information, financial information, passwords, or other sensitive personal data.

===== '''Can I replace outdated documents?''' =====
Yes. Keep documentation current by replacing outdated versions whenever equipment or configurations change.

===== '''Why should I use Local Unit Documents instead of storing files locally?''' =====
The '''Documents''' feature provides a centralized repository that remains with the property rather than an individual technology specialist. Authorized users can securely access Local Unit Documents from any location, making it easier to troubleshoot issues, identify equipment, coordinate repairs, and preserve important knowledge as technology specialists change callings.

Save Local Unit Documents in Church Network Manager

2026-07-15T19:09:27Z

Ericjamee: Created page with "Save Local Unit Documents in Church Network Manager Technology specialists, clerks and bishopric members can upload Local Unit Documents to the Documents feature in Church Network Manager. This feature provides a secure, centralized location for storing information that supports the ongoing operation and maintenance of meetinghouse technology. Local Unit Documents remain associated with the property, allowing future technology specialists to access and maintain the docum..."

Save Local Unit Documents in Church Network Manager
Technology specialists, clerks and bishopric members can upload Local Unit Documents to the Documents feature in Church Network Manager. This feature provides a secure, centralized location for storing information that supports the ongoing operation and maintenance of meetinghouse technology. Local Unit Documents remain associated with the property, allowing future technology specialists to access and maintain the documentation as responsibilities change over time.
Why Use Local Unit Documents?
As a technology specialist, you are responsible for supporting and maintaining a variety of meetinghouse technology. Whenever possible, issues can be resolved more efficiently if the information you need is available remotely rather than requiring a visit to the meetinghouse.
The Documents feature in Church Network Manager allows you to store Local Unit Documents in one secure, centralized location. You can upload the information that is most valuable for supporting your assigned buildings, making it easier for both current and future technology specialists to locate important records.
Examples of useful documents include:
• Network diagrams and rack layouts
• Technology inventories
• Internet service provider information
• Equipment manuals and vendor documentation
• Photographs of equipment installations
• Photos showing serial numbers, model numbers, and part numbers for computers, networking equipment, printers, cameras, displays, and other technology devices
Having this information available remotely can simplify many support tasks. For example, you can reference a device's serial number while working with a vendor's support website, verify model or part numbers before ordering replacement equipment, or provide accurate information when coordinating repairs with the Facilities Manager—all without traveling to the meetinghouse.
Keeping this documentation current also preserves valuable local knowledge, making it easier for future technology specialists to understand the meetinghouse technology environment and continue providing effective support.
For a visual walkthrough of this process, see Save Local Unit Documents in Church Network Manager.

Upload a Local Unit Document
Step 1: Open Church Network Manager
1. Sign in to Church Network Manager.
Step 2: Select the Property
1. Select the Property that the document will reference.
Step 3: In the Documents Section
1. Select Manage Documents.
Step 4: Open the Menu
1. Select the Menu.
Step 5: Add Document
1. Select Add Document.
Step 6: Select the File
1. Browse to the document on your computer.
2. Select the file.
3. Select Open.
Step 7: Enter a Short Name
1. Enter a short, descriptive name for the document.
Step 8: Complete the Document Information
1. (Optional) Enter a Description that explains the document's purpose.
2. If applicable, select the appropriate document category.
Step 9: Add a Custom Tag (Optional)
1. Enter a Custom Tag for the document.
2. Select Add Tag.
Step 10: Save Document
1. When complete, select Save.
Step 11: Verify the Upload
1. Verify that the document appears in the Documents list.

Recommended Documents
Consider storing Local Unit Documents such as:
• Network diagrams and rack layouts
• Technology inventories
• Internet service provider information
• Cabling documentation
• Equipment manuals and vendor documentation
• Equipment installation photographs
• Photos showing serial numbers, model numbers, and part numbers for computers, networking equipment, printers, cameras, displays, and other technology devices
• Wireless access point locations
• Audio/video system documentation
• Maintenance notes and equipment replacement history

Protect Personal Information
Only upload documents that support the operation and maintenance of meetinghouse technology.
Do not upload documents that contain personal or confidential information, including:
• Member names
• Phone or mobile numbers
• Email addresses
• Messaging account information (such as WhatsApp or Signal)
• Home addresses
• Membership record numbers
• Financial information
• Passwords, passphrases, or security codes
• Personal login credentials
• Any other personally identifiable information (PII)
If a document contains both technology information and personal information, remove or redact the personal information before uploading the document.
When documenting equipment, include information such as model numbers, serial numbers, part numbers, network diagrams, equipment locations, and installation photographs—but avoid including information that identifies individual members or leaders.

Best Practices
• Use clear, descriptive document titles.
• Include dates on diagrams and inventories so others know when they were last updated.
• Update documentation whenever equipment is installed, replaced, relocated, or removed.
• Replace outdated documents with current versions whenever possible.
• Capture photographs that clearly show equipment placement, cable connections, serial numbers, model numbers, and part numbers.
• Store Local Unit Documents in the Documents feature of Church Network Manager instead of on personal computers or removable media whenever possible.
• Follow the guidance in Protect Personal Information before uploading any document.

Frequently Asked Questions
Who can view Local Unit Documents?
Only authorized users with access to the property in Church Network Manager can view uploaded documents.
What kinds of documents should I upload?
Upload Local Unit Documents that help install, maintain, troubleshoot, or replace meetinghouse technology equipment.
Should I upload documents containing member information?
No. Do not upload documents containing confidential member information, financial information, passwords, or other sensitive personal data.
Can I replace outdated documents?
Yes. Keep documentation current by replacing outdated versions whenever equipment or configurations change.
Why should I use Local Unit Documents instead of storing files locally?
The Documents feature provides a centralized repository that remains with the property rather than an individual technology specialist. Authorized users can securely access Local Unit Documents from any location, making it easier to troubleshoot issues, identify equipment, coordinate repairs, and preserve important knowledge as technology specialists change callings.

AI Live Interpretation in Sacrament Meetings Pilot

2026-07-02T16:06:54Z

Ericjamee: I added images

{{DISPLAYTITLE:AI Live Interpretation Sacrament Meeting Pilot }}

=== '''<big>Overview</big>''' ===
This article explains how to set up and use the Lara Simultaneous Interpreter for sacrament meetings as part of an approved pilot program. The pilot is intended to help members receive real-time interpretation on their personal devices while allowing the Church to continue evaluating and improving the technology, translation quality, and overall user experience.

''Note: If your unit has not been invited to participate in the pilot, this article will not be applicable.''

'''Important'''

The quality of the interpretation depends primarily on the quality of the audio provided to the system. Clear, consistent audio produces significantly better translation results. For the best experience, follow the audio recommendations provided in this article.

No installation is required. Everything runs in a supported web browser.

== '''<big>How to Use the Lara Simultaneous Interpreter</big>''' ==
The system uses two roles:

* '''Speaker (Host)''': The person who starts and manages the interpretation session.
* '''Listener (Guest):''' The person who receives the interpreted audio and captions.

The Speaker shares a '''Listener link''' or '''QR code''' with participants so they can join the session.

No installation is required. The Speaker and Listener access Lara through a supported web browser.

=== '''<big>Speaker (Host)</big>''' ===

==== '''<big>Preparation</big>''' ====
Before the meeting:
A. Decide how you will share the Listener link (or QR code) and any feedback form with listeners.

B. Test the Speaker link and audio setup before the sacrament meeting.

C. If you are also using Zoom:

* If possible, use '''two devices'''—one for Zoom and one for Lara Simultaneous Interpreter—for the best performance.
* If only one device is available, access both Zoom and Lara through a web browser rather than using the desktop applications.

==== '''<big>Meeting Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Open the Speaker link you received
# Confirm the session shows “'''Ready to broadcast'''”
# When the meeting begins, click '''Start Recording'''
# Use the '''Start''' and '''Stop Recording''' as needed to control what is translated
# When finished, click '''Close Session''' to end the broadcast
[[File:Lara Speaker Graphic 1.png|none|thumb|360x360px]]

===== '''Important''': =====

* The Speaker does not select a language or configure interpretation settings. Simply click '''Start Recording''' and begin speaking.
* Only one Speaker (Host) should manage a session at a time.
* The top-right corner of the Speaker interface displays the current number of listeners connected to the session (This number includes the speaker).
* If your unit has more than one spoken language during a meeting (for example, testimonies in different languages), see '''Multiple Spoken Languages''' later in this article.

=== '''<big>Listener (Guest)</big>''' ===

==== '''<big>Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Scan the QR code or click on the Listener link provided for interpretation
# The Listener page opens with the session name
# Select your desired Target Language
# Click '''Connect'''
# Click the speaker icon to start listening to the real-time translation
## (6a)If the listener does not have headphones, they may choose to only read the captions.
[[File:Lara Listener Graphic.png|none|thumb|481x481px]]

*
== <big>'''APPENDIX'''</big> ==

=== <big>'''Key Reminders and Expectations'''</big> ===

==== '''Speaker (Host)''': ====
* Clear, consistent audio is the most important factor affecting interpretation quality. Review the '''Audio Recommendations''' below before each meeting.
* The Speaker must click '''Start Recording''' before listeners can receive interpretation.
* Speaker and Listener links remain the same each week unless new links are requested. To request new links, contact your Church Headquarters pilot coordinator.
* Do not share the Speaker link. Only the person managing the session should use it.
* Only one Speaker (Host) should manage a session at a time.
* If using Zoom and Lara Simultaneous Interpreter together, use separate devices when possible. If only one device is available, access both through a web browser.

==== '''Listener (Guest):''' ====
* Use a personal device to receive interpretation.
* When using a phone or tablet, headphones are strongly recommended to improve audio quality and help prevent feedback.
* Listeners may join after the Speaker has started the session.
* Each listener may select a different language.
* A delay between the original speech and the interpreted audio is expected.
* On-screen captions typically appear before the interpreted audio because audio processing requires additional time.

==== '''General:''' ====
* Lara Simultaneous Interpreter is currently being used as part of an approved pilot. Interpretation quality, features, and the overall user experience will continue to improve throughout the pilot.
* The quality of the interpretation depends primarily on the quality of the audio provided to the system.
* Everything runs in a supported web browser. No application installation is required.

=== '''<big>Audio Recommendations</big>''' ===
The quality of the interpretation depends primarily on the quality of the audio provided to Lara Simultaneous Interpreter. Clear audio will produce more accurate and natural interpretation, while poor audio may result in reduced accuracy, missed words, or increased delay.

==== '''<big>Speaker (Host)</big>''' ====
'''For the best interpretation quality:'''
* Whenever possible, connect the Speaker device directly to the chapel sound system.
* Minimize background noise near the Speaker device.
* Speak clearly, at a normal conversational pace, and avoid speaking excessively fast.
* Pause briefly between speakers or when changing languages to help the system process the audio.
* Use an external microphone if a direct chapel audio connection is not available.
* Ensure the Speaker device has a reliable internet connection.
* If using Zoom and Lara Simultaneous Interpreter at the same time, use separate devices when possible. If only one device is available, use a web browser for both applications.
To select the audio input, click the '''Settings''' button near the bottom of the Speaker page:[[File:Start Recording Graphic.png|none|thumb|468x468px]]

==== '''<big>Recommended audio setup (best to least preferred)</big>''' ====

===== '''1. Line-level audio from the chapel sound system (Best)''' =====
<blockquote>Connecting directly to the chapel sound system provides the clearest and most consistent audio and is the recommended setup whenever possible. [[File:Pulpit with laptop connected to AV panel (1).jpg|none|thumb]][[File:AV rack with laptop connection.jpg|none|thumb]] </blockquote>

===== '''2. External Microphone''' =====
<blockquote>If a direct chapel audio connection is not available, use a dedicated external microphone (Like a bluetooth microphone) connected to the Speaker device. Position the microphone as close to the person speaking as practical while minimizing background noise.[[File:AI-I laptop with bluetooth mic.jpg|none|thumb]]</blockquote>

===== '''3. Built-in device microphone (least preferred)''' =====
<blockquote>If no external audio equipment is available, use the device’s built-in microphone.
For best results:

* Place the device as close as practical to the speaker.
* Keep the microphone unobstructed.
* Reduce nearby conversations and other background noise.
* Position the device where it has a strong and stable internet connection.</blockquote>If you need help connecting to the chapel audio system, contact your '''Facilities Manager.'''
[[File:AI-I laptop only.jpg|none|thumb]]

=== '''<big>Multiple Spoken Languages</big>''' ===
If more than one language will be spoken during the meeting, you have two options:

==== '''Option 1: Autodetect Language Link''' ====

* Requires a separate Speaker link

* Uses a different Listener link than the primary session

* Automatically detects the language being spoken

'''Note:''' Interpretation quality may be lower when using autodetect.

Contact your pilot coordinator if you would like to use this option

==== '''Option 2: Separate Links for Each Language''' ====

* Request a separate Speaker link for each language

* Each Speaker link has a corresponding Listener link

This option may provide more consistent interpretation quality

== '''<big>Support and Troubleshooting</big>''' ==

=== Unable to connect to the “Liahona” Wi-Fi network ===
If someone cannot connect to the '''Liahona''' Wi-Fi network:

* Verify that the correct password has been entered.
* Confirm that the device is attempting to connect to '''Liahona''' rather than another wireless network.

=== Need additional assistance? ===
During the pilot:

'''Contact the Facilities Manager or submit a ticket using the Church’s Facilities Incident Reporting (FIR) mobile app if:'''

* The issue is related to the meetinghouse internet or Wi-Fi network.
* You need assistance connecting to the chapel audio system.
* There is a problem with the chapel audio system.

'''Contact your Area or Church Headquarters pilot coordinator if:'''

* The issue is related to the Lara by Translated website.
* You have questions about the pilot.
* You would like to request additional Speaker or Listener links.

= '''Frequently Asked Questions''' =

=== Can more than one Speaker (Host) manage a session? ===
No. Only one Speaker (Host) should manage a session at a time. Multiple hosts can create conflicts and may negatively affect session performance.
----

=== What if someone who needs interpretation does not have a personal device? ===
If a personal device is not available, one option is to display the text captions on a TV, projector, or other large display.

Lara Live provides a subtitle link specifically designed for larger displays.

To use this feature, replace '''<code>/listener/</code>''' with '''<code>/subtitle/</code>''' in the Listener URL.

'''Example'''

Change:

<code><nowiki>https://sim.laralive.com/listener/</nowiki>...</code>

To:

<code><nowiki>https://sim.laralive.com/subtitle/</nowiki>...</code>

Another option is to connect a device to a TV or projector in another room of the meetinghouse. The device can join the Listener link to play the interpreted audio while also displaying the captions, allowing participants to both hear the interpretation and read the captions.
[[File:AI-I classroom subtitles.jpg|none|thumb]]
----

=== Why do the captions appear before the interpreted audio? ===
This is expected behavior.

Text captions can usually be displayed more quickly than interpreted audio because additional processing is required to generate natural-sounding speech. As a result, captions will often appear before the audio is heard.
----

=== What provides the best interpretation quality? ===
The quality of the interpretation depends primarily on the quality of the audio received by the system.

For the best results:

* Use the chapel sound system whenever possible.
* Minimize background noise.
* Speak clearly at a normal conversational pace.
* Use an external microphone if a chapel audio connection is not available.
* Ensure a reliable internet connection.
* When using phones or tablets, listeners should use headphones whenever possible.

{{DEFAULTSORT:AI Live Interpretation in Sacrament Meetings Pilot}}

File:AI-I classroom subtitles.jpg

2026-07-02T16:06:35Z

Ericjamee:

AI-I classroom subtitles

File:AI-I laptop only.jpg

2026-07-02T16:04:35Z

Ericjamee:

AI-I laptop only

File:AI-I laptop with bluetooth mic.jpg

2026-07-02T16:03:30Z

Ericjamee:

AI-I laptop with bluetooth mic

File:AV rack with laptop connection.jpg

2026-07-02T16:02:25Z

Ericjamee:

AV rack with laptop connection

File:Pulpit with laptop connected to AV panel (1).jpg

2026-07-02T16:01:26Z

Ericjamee:

Pulpit with laptop connected to AV panel (1)

Using Accessibility Technology

2026-06-26T16:48:48Z

Ericjamee: Ericjamee moved page Using Accessibility Technology to Accessibility Technology

#REDIRECT [[Accessibility Technology]]

Accessibility Technology

2026-06-26T16:48:48Z

Ericjamee: Ericjamee moved page Using Accessibility Technology to Accessibility Technology

>[[Meetinghouse Technology]] > [[Audio Video Distribution]]

[[File:ASL General Conference.png|480x480px]]

Technology enables us to meet the needs of minority language speakers and the hearing impaired. Depending on the age of your AV system,

This article discusses how to use assisted-listening systems (ALSs), show American Sign Language (ASL) in broadcasts, add closed captions to broadcasts and videos, and use interpretation equipment.

==ListenWIFI for Assistive Listening and Interpretation==
ListenWIFI is a Wi-Fi-based assistive listening and interpretation technology being used in the United States and one or two other areas of the world.

For more information, see the [[ListenWIFI]] page.

== TASK: SETTING UP ASSISTED-LISTENING SYSTEMS ==
[[File:Listening Devices.png|484x484px]]

Church members who use a personal hearing aid often find that it does not adequately receive the sound from the sound system. Others with minor hearing impairments sometimes have difficulty understanding speech in large rooms such as chapels. To help these individuals, many meetinghouses have a wireless ALS.

# Locate the ALSs of each building.
#* Each building is equipped with two ALS devices, and more can be requested from your local facilities management group (FMG) if needed.
# Set the channel on the ALS.
#* Ideally, to eliminate difficulties for stake members, the channel will be the same for all meetinghouses.
#* Church ALSs operate at the 70 MHz band.
# Give the ALS to the person in need.
#* Explain to the user how the device works.
#* Refer to the owner’s manual for specific device operation questions.
# Earphones should be permanently given to repeat users; receivers should not.
#* Those who wish to do so can purchase their own devices.

Notes:

* A special neck loop is also available that retransmits the signal to the user’s hearing aid. In order to use the neck loop, the individual’s hearing aid must have a switch for use with a telephone, and the switch must be in the “T” (telephone) position.
* The earphone jack on the receiver is also the power switch, so the earphone and neck loop should be unplugged when they are not in use. For sanitary reasons, earphones should be given to repeat users to keep. The pocket-size receivers should be checked out from the materials center.
* Many countries restrict the power radiated by Church hearing-impaired system transmitters. The transmitter or antenna should not be modified to increase the coverage.
* Generally, ALSs from different brands are still compatible with one another.

== TASK: SETTING UP AMERICAN SIGN LANGUAGE ==
[[File:ASL Setup.png|none|thumb|479x479px]]

ASL is available for Church broadcasts in North American meetinghouses via the internet. Depending on your satellite connections, it may also be available via satellite. Priesthood leaders should coordinate requests for satellite ASL equipment with their facilities manager.

# Review how to broadcast via internet.
# Go to ChurchofJesusChrist.org/broadcasts and select the desired broadcast.
# From the language drop-down menu in the top right corner, choose '''American Sign Language'''.
#* Remember that picture quality is important for reading hand signals.
#** Use a wired connection to provide a clearer and more reliable picture.
# Decide on the best location to show the ASL broadcast.
#* The broadcast may be shown in a separate room or on a separate monitor within the same room.
#* For TV connection instructions, please review how to connect a TV.

== TASK: SETTING UP CLOSED CAPTIONING ==
[[File:Closed Captioning Screen.png|480x480px]]

Closed captioning for the hearing impaired is available in many areas. If it is available in your area, at least one television should be set up during broadcasts for those who need this service. Sample closed-captioning data is broadcast at least one hour before any major broadcast in order to test the setup.

# Set up the TV monitor in the desired viewing area.
#* For more information on using a TV, click here.
#* For more information on how to connect a TV to a satellite broadcast, click here.
# Go to the TV’s menu screen and select the closed-captions menu.
#* For more details, see the TV’s owner’s manual.
# Select the desired language.
#* CC1—English
#* CC3—Spanish
#* CC4—Portuguese

Notes:

* Closed-caption channels selected on the TV affect only the language of the text, not the spoken language heard through the TV.
* TV HDMI inputs are not compatible with closed captioning. If your chapel has HDMI distribution, locate the composite video output (normally on the front of the modesty rail millwork).

== TASK: SETTING UP INTERPRETATION EQUIPMENT ==
[[File:Interpretation Devices.png]]

Congregations with multiple language needs should coordinate with their local FMG. The FMG will obtain the necessary equipment to provide simultaneous interpretation of meetings. Translation assistance is provided through special receivers and headphones. Interpretation systems are portable and can be used anywhere in the meetinghouse.

# Ensure that the meetinghouse has the necessary equipment to provide interpretation of meetings.
#* Contact your local FMG if equipment is needed.
#* Older equipment has proved very durable and is compatible with newer equipment.
# Lend interpretation devices to all who require them.
#* For sanitary reasons, it is recommended that headphones not be transferred from person to person where possible.
# Ensure that the RF channel is the same on the interpreter’s and listeners’ devices.
#* Ideally, the same channel will be used throughout the stake to minimize difficulties in use.
# The interpreter speaks into the microphone to live-translate the meeting.
#* The microphone should be sensitive enough to accurately broadcast a quiet or whispering voice.
#* The transmitter broadcasts the interpreter’s words to people wearing headphones in the congregation.

''Note:'' To allow part of a congregation to hear a different language without having to be in a different room during satellite broadcasts, use a Williams Sound transmitter. Connect the Williams Sound transmitter line-level RCA jack input to a VCR or TV monitor (tuned to the needed language channel) that is connected to the satellite. FMGs can assist you with these connections.

* It is not normally recommended to display closed captioning on the main screen for all to view. The audio and captions are often out of sync, which can distract and frustrate those who do not need captions.
[[Category:Meetinghouse Technology]]

AI Live Interpretation in Sacrament Meetings Pilot

2026-06-25T18:32:55Z

Ericjamee:

{{DISPLAYTITLE:AI Live Interpretation Sacrament Meeting Pilot }}

=== '''<big>Overview</big>''' ===
This article explains how to set up and use the Lara Simultaneous Interpreter for sacrament meetings as part of an approved pilot program. The pilot is intended to help members receive real-time interpretation on their personal devices while allowing the Church to continue evaluating and improving the technology, translation quality, and overall user experience.

''Note: If your unit has not been invited to participate in the pilot, this article will not be applicable.''

'''Important'''

The quality of the interpretation depends primarily on the quality of the audio provided to the system. Clear, consistent audio produces significantly better translation results. For the best experience, follow the audio recommendations provided in this article.

No installation is required. Everything runs in a supported web browser.

== '''<big>How to Use the Lara Simultaneous Interpreter</big>''' ==
The system uses two roles:

* '''Speaker (Host)''': The person who starts and manages the interpretation session.
* '''Listener (Guest):''' The person who receives the interpreted audio and captions.

The Speaker shares a '''Listener link''' or '''QR code''' with participants so they can join the session.

No installation is required. The Speaker and Listener access Lara through a supported web browser.

=== '''<big>Speaker (Host)</big>''' ===

==== '''<big>Preparation</big>''' ====
Before the meeting:
A. Decide how you will share the Listener link (or QR code) and any feedback form with listeners.

B. Test the Speaker link and audio setup before the sacrament meeting.

C. If you are also using Zoom:

* If possible, use '''two devices'''—one for Zoom and one for Lara Simultaneous Interpreter—for the best performance.
* If only one device is available, access both Zoom and Lara through a web browser rather than using the desktop applications.

==== '''<big>Meeting Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Open the Speaker link you received
# Confirm the session shows “'''Ready to broadcast'''”
# When the meeting begins, click '''Start Recording'''
# Use the '''Start''' and '''Stop Recording''' as needed to control what is translated
# When finished, click '''Close Session''' to end the broadcast
[[File:Lara Speaker Graphic 1.png|none|thumb|360x360px]]

===== '''Important''': =====

* The Speaker does not select a language or configure interpretation settings. Simply click '''Start Recording''' and begin speaking.
* Only one Speaker (Host) should manage a session at a time.
* The top-right corner of the Speaker interface displays the current number of listeners connected to the session (This number includes the speaker).
* If your unit has more than one spoken language during a meeting (for example, testimonies in different languages), see '''Multiple Spoken Languages''' later in this article.

=== '''<big>Listener (Guest)</big>''' ===

==== '''<big>Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Scan the QR code or click on the Listener link provided for interpretation
# The Listener page opens with the session name
# Select your desired Target Language
# Click '''Connect'''
# Click the speaker icon to start listening to the real-time translation
## (6a)If the listener does not have headphones, they may choose to only read the captions.
[[File:Lara Listener Graphic.png|none|thumb|481x481px]]

*
== <big>'''APPENDIX'''</big> ==

=== <big>'''Key Reminders and Expectations'''</big> ===

==== '''Speaker (Host)''': ====
* Clear, consistent audio is the most important factor affecting interpretation quality. Review the '''Audio Recommendations''' below before each meeting.
* The Speaker must click '''Start Recording''' before listeners can receive interpretation.
* Speaker and Listener links remain the same each week unless new links are requested. To request new links, contact your Church Headquarters pilot coordinator.
* Do not share the Speaker link. Only the person managing the session should use it.
* Only one Speaker (Host) should manage a session at a time.
* If using Zoom and Lara Simultaneous Interpreter together, use separate devices when possible. If only one device is available, access both through a web browser.

==== '''Listener (Guest):''' ====
* Use a personal device to receive interpretation.
* When using a phone or tablet, headphones are strongly recommended to improve audio quality and help prevent feedback.
* Listeners may join after the Speaker has started the session.
* Each listener may select a different language.
* A delay between the original speech and the interpreted audio is expected.
* On-screen captions typically appear before the interpreted audio because audio processing requires additional time.

==== '''General:''' ====
* Lara Simultaneous Interpreter is currently being used as part of an approved pilot. Interpretation quality, features, and the overall user experience will continue to improve throughout the pilot.
* The quality of the interpretation depends primarily on the quality of the audio provided to the system.
* Everything runs in a supported web browser. No application installation is required.

=== '''<big>Audio Recommendations</big>''' ===
The quality of the interpretation depends primarily on the quality of the audio provided to Lara Simultaneous Interpreter. Clear audio will produce more accurate and natural interpretation, while poor audio may result in reduced accuracy, missed words, or increased delay.

==== '''<big>Speaker (Host)</big>''' ====
'''For the best interpretation quality:'''
* Whenever possible, connect the Speaker device directly to the chapel sound system.
* Minimize background noise near the Speaker device.
* Speak clearly, at a normal conversational pace, and avoid speaking excessively fast.
* Pause briefly between speakers or when changing languages to help the system process the audio.
* Use an external microphone if a direct chapel audio connection is not available.
* Ensure the Speaker device has a reliable internet connection.
* If using Zoom and Lara Simultaneous Interpreter at the same time, use separate devices when possible. If only one device is available, use a web browser for both applications.
To select the audio input, click the '''Settings''' button near the bottom of the Speaker page:[[File:Start Recording Graphic.png|none|thumb|468x468px]]

==== '''<big>Recommended audio setup (best to least preferred)</big>''' ====

===== '''1. Line-level audio from the chapel sound system (Best)''' =====
<blockquote>Connecting directly to the chapel sound system provides the clearest and most consistent audio and is the recommended setup whenever possible. </blockquote>

===== '''2. External Microphone''' =====
<blockquote>If a direct chapel audio connection is not available, use a dedicated external microphone (Like a bluetooth microphone) connected to the Speaker device. Position the microphone as close to the person speaking as practical while minimizing background noise.</blockquote>

===== '''3. Built-in device microphone (least preferred)''' =====
<blockquote>If no external audio equipment is available, use the device’s built-in microphone.
For best results:

* Place the device as close as practical to the speaker.
* Keep the microphone unobstructed.
* Reduce nearby conversations and other background noise.
* Position the device where it has a strong and stable internet connection.</blockquote>If you need help connecting to the chapel audio system, contact your '''Facilities Manager.'''

=== '''<big>Multiple Spoken Languages</big>''' ===
If more than one language will be spoken during the meeting, you have two options:

==== '''Option 1: Autodetect Language Link''' ====

* Requires a separate Speaker link

* Uses a different Listener link than the primary session

* Automatically detects the language being spoken

'''Note:''' Interpretation quality may be lower when using autodetect.

Contact your pilot coordinator if you would like to use this option

==== '''Option 2: Separate Links for Each Language''' ====

* Request a separate Speaker link for each language

* Each Speaker link has a corresponding Listener link

This option may provide more consistent interpretation quality

== '''<big>Support and Troubleshooting</big>''' ==

=== Unable to connect to the “Liahona” Wi-Fi network ===
If someone cannot connect to the '''Liahona''' Wi-Fi network:

* Verify that the correct password has been entered.
* Confirm that the device is attempting to connect to '''Liahona''' rather than another wireless network.

=== Need additional assistance? ===
During the pilot:

'''Contact the Facilities Manager or submit a ticket using the Church’s Facilities Incident Reporting (FIR) mobile app if:'''

* The issue is related to the meetinghouse internet or Wi-Fi network.
* You need assistance connecting to the chapel audio system.
* There is a problem with the chapel audio system.

'''Contact your Area or Church Headquarters pilot coordinator if:'''

* The issue is related to the Lara by Translated website.
* You have questions about the pilot.
* You would like to request additional Speaker or Listener links.

= '''Frequently Asked Questions''' =

=== Can more than one Speaker (Host) manage a session? ===
No. Only one Speaker (Host) should manage a session at a time. Multiple hosts can create conflicts and may negatively affect session performance.
----

=== What if someone who needs interpretation does not have a personal device? ===
If a personal device is not available, one option is to display the text captions on a TV, projector, or other large display.

Lara Live provides a subtitle link specifically designed for larger displays.

To use this feature, replace '''<code>/listener/</code>''' with '''<code>/subtitle/</code>''' in the Listener URL.

'''Example'''

Change:

<code><nowiki>https://sim.laralive.com/listener/</nowiki>...</code>

To:

<code><nowiki>https://sim.laralive.com/subtitle/</nowiki>...</code>

Another option is to connect a device to a TV or projector in another room of the meetinghouse. The device can join the Listener link to play the interpreted audio while also displaying the captions, allowing participants to both hear the interpretation and read the captions.
----

=== Why do the captions appear before the interpreted audio? ===
This is expected behavior.

Text captions can usually be displayed more quickly than interpreted audio because additional processing is required to generate natural-sounding speech. As a result, captions will often appear before the audio is heard.
----

=== What provides the best interpretation quality? ===
The quality of the interpretation depends primarily on the quality of the audio received by the system.

For the best results:

* Use the chapel sound system whenever possible.
* Minimize background noise.
* Speak clearly at a normal conversational pace.
* Use an external microphone if a chapel audio connection is not available.
* Ensure a reliable internet connection.
* When using phones or tablets, listeners should use headphones whenever possible.

{{DEFAULTSORT:AI Live Interpretation in Sacrament Meetings Pilot}}

AI Live Interpretation in Sacrament Meetings Pilot

2026-06-25T16:05:03Z

Ericjamee: Removed AI images

{{DISPLAYTITLE:AI Live Interpretation Sacrament Meeting Pilot }}

=== '''<big>Overview</big>''' ===
This article explains how to set up and use the Lara Simultaneous Interpreter for sacrament meetings as part of an approved pilot program. The pilot is intended to help members receive real-time interpretation on their personal devices while allowing the Church to continue evaluating and improving the technology, translation quality, and overall user experience.

''Note: If your unit has not been invited to participate in the pilot, this article will not be applicable.''

'''Important'''

The quality of the interpretation depends primarily on the quality of the audio provided to the system. Clear, consistent audio produces significantly better translation results. For the best experience, follow the audio recommendations provided in this article.

No installation is required. Everything runs in a supported web browser.

== '''<big>How to Use the Lara Simultaneous Interpreter</big>''' ==
The system uses two roles:

* '''Speaker (Host)''': The person who starts and manages the interpretation session.
* '''Listener (Guest):''' The person who receives the interpreted audio and captions.

The Speaker shares a '''Listener link''' or '''QR code''' with participants so they can join the session.

No installation is required. The Speaker and Listener access Lara through a supported web browser.

=== '''<big>Speaker (Host)</big>''' ===

==== '''<big>Preparation</big>''' ====
Before the meeting:
A. Decide how you will share the Listener link (or QR code) and any feedback form with listeners.

B. Test the Speaker link and audio setup before the sacrament meeting.

C. If you are also using Zoom:

* If possible, use '''two devices'''—one for Zoom and one for Lara Simultaneous Interpreter—for the best performance.
* If only one device is available, access both Zoom and Lara through a web browser rather than using the desktop applications.

==== '''<big>Meeting Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Open the Speaker link you received
# Confirm the session shows “'''Ready to broadcast'''”
# When the meeting begins, click '''Start Recording'''
# Use the '''Start''' and '''Stop Recording''' as needed to control what is translated
# When finished, click '''Close Session''' to end the broadcast
[[File:Lara Speaker Graphic 1.png|none|thumb|360x360px]]

===== '''Important''': =====

* The Speaker does not select a language or configure interpretation settings. Simply click '''Start Recording''' and begin speaking.
* Only one Speaker (Host) should manage a session at a time.
* The top-right corner of the Speaker interface displays the current number of listeners connected to the session (This number includes the speaker).
* If your unit has more than one spoken language during a meeting (for example, testimonies in different languages), see '''Multiple Spoken Languages''' later in this article.

=== '''<big>Listener (Guest)</big>''' ===

==== '''<big>Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Scan the QR code or click on the Listener link provided for interpretation
# The Listener page opens with the session name
# Select your desired Target Language
# Click '''Connect'''
# Click the speaker icon to start listening to the real-time translation
## (6a)If the listener does not have headphones, they may choose to only read the captions.
[[File:Lara Listener Graphic.png|none|thumb|481x481px]]

*
== <big>'''APPENDIX'''</big> ==

=== <big>'''Key Reminders and Expectations'''</big> ===

==== '''Speaker (Host)''': ====
* Clear, consistent audio is the most important factor affecting interpretation quality. Review the '''Audio Recommendations''' below before each meeting.
* The Speaker must click '''Start Recording''' before listeners can receive interpretation.
* Speaker and Listener links remain the same each week unless new links are requested. To request new links, contact your Church Headquarters pilot coordinator.
* Do not share the Speaker link. Only the person managing the session should use it.
* Only one Speaker (Host) should manage a session at a time.
* If using Zoom and Lara Simultaneous Interpreter together, use separate devices when possible. If only one device is available, access both through a web browser.

==== '''Listener (Guest):''' ====
* Use a personal device to receive interpretation.
* When using a phone or tablet, headphones are strongly recommended to improve audio quality and help prevent feedback.
* Listeners may join after the Speaker has started the session.
* Each listener may select a different language.
* A delay between the original speech and the interpreted audio is expected.
* On-screen captions typically appear before the interpreted audio because audio processing requires additional time.

==== '''General:''' ====
* Lara Simultaneous Interpreter is currently being used as part of an approved pilot. Interpretation quality, features, and the overall user experience will continue to improve throughout the pilot.
* The quality of the interpretation depends primarily on the quality of the audio provided to the system.
* Everything runs in a supported web browser. No application installation is required.

=== '''<big>Audio Recommendations</big>''' ===
The quality of the interpretation depends primarily on the quality of the audio provided to Lara Simultaneous Interpreter. Clear audio will produce more accurate and natural interpretation, while poor audio may result in reduced accuracy, missed words, or increased delay.

==== '''<big>Speaker (Host)</big>''' ====
'''For the best interpretation quality:'''
* Whenever possible, connect the Speaker device directly to the chapel sound system.
* Minimize background noise near the Speaker device.
* Speak clearly, at a normal conversational pace, and avoid speaking excessively fast.
* Pause briefly between speakers or when changing languages to help the system process the audio.
* Use an external microphone if a direct chapel audio connection is not available.
* Ensure the Speaker device has a reliable internet connection.
* If using Zoom and Lara Simultaneous Interpreter at the same time, use separate devices when possible. If only one device is available, use a web browser for both applications.
To select the audio input, click the '''Settings''' button near the bottom of the Speaker page:[[File:Start Recording Graphic.png|none|thumb|468x468px]]

==== '''<big>Recommended audio setup (best to least preferred)</big>''' ====

===== '''1. Line-level audio from the chapel sound system (Best)''' =====
<blockquote>Connecting directly to the chapel sound system provides the clearest and most consistent audio and is the recommended setup whenever possible. </blockquote>

===== '''2. External Microphone''' =====
<blockquote>If a direct chapel audio connection is not available, use a dedicated external microphone (Like a bluetooth microphone) connected to the Speaker device. Position the microphone as close to the person speaking as practical while minimizing background noise.</blockquote>

===== '''3. Built-in device microphone (least preferred)''' =====
<blockquote>If no external audio equipment is available, use the device’s built-in microphone.
For best results:

* Place the device as close as practical to the speaker.
* Keep the microphone unobstructed.
* Reduce nearby conversations and other background noise.
* Position the device where it has a strong and stable internet connection.</blockquote>If you need help connecting to the chapel audio system, contact your '''Facilities Manager.'''

=== '''<big>Multiple Spoken Languages</big>''' ===
If more than one language will be spoken during the meeting, you have two options:

==== '''Option 1: Autodetect Language Link''' ====

* Requires a separate Speaker link

* Uses a different Listener link than the primary session

* Automatically detects the language being spoken

'''Note:''' Interpretation quality may be lower when using autodetect.

Contact your pilot coordinator if you would like to use this option

==== '''Option 2: Separate Links for Each Language''' ====

* Request a separate Speaker link for each language

* Each Speaker link has a corresponding Listener link

This option may provide more consistent interpretation quality

== '''<big>Support and Troubleshooting</big>''' ==

=== Unable to connect to the “Liahona” Wi-Fi network ===
If someone cannot connect to the '''Liahona''' Wi-Fi network:

* Verify that the correct password has been entered.
* Confirm that the device is attempting to connect to '''Liahona''' rather than another wireless network.

=== Need additional assistance? ===
During the pilot:

'''Contact the Facilities Manager or submit a ticket using the Church’s Facilities Incident Reporting (FIR) mobile app if:'''

* The issue is related to the meetinghouse internet or Wi-Fi network.
* You need assistance connecting to the chapel audio system.
* There is a problem with the chapel audio system.

'''Contact your Area or Church Headquarters pilot coordinator if:'''

* The issue is related to the Lara by Translated website.
* You have questions about the pilot.
* You would like to request additional Speaker or Listener links.

= '''Frequently Asked Questions''' =

=== Can more than one Speaker (Host) manage a session? ===
No. Only one Speaker (Host) should manage a session at a time. Multiple hosts can create conflicts and may negatively affect session performance.
----

=== What if someone who needs interpretation does not have a personal device? ===
If a personal device is not available, one option is to display the text captions on a TV, projector, or other large display.

Lara Live provides a subtitle link specifically designed for larger displays.

To use this feature, replace '''<code>/listener/</code>''' with '''<code>/subtitle/</code>''' in the Listener URL.

'''Example'''

Change:

<code><nowiki>https://sim.laralive.com/listener/</nowiki>...</code>

To:

<code><nowiki>https://sim.laralive.com/subtitle/</nowiki>...</code>

Another option is to connect a device to a TV or projector in another room of the meetinghouse. The device can join the Listener link to play the interpreted audio while also displaying the captions, allowing participants to both hear the interpretation and read the captions.
----

=== Why do the captions appear before the interpreted audio? ===
This is expected behavior.

Text captions can usually be displayed more quickly than interpreted audio because additional processing is required to generate natural-sounding speech. As a result, captions will often appear before the audio is heard.
----

=== What provides the best interpretation quality? ===
The quality of the interpretation depends primarily on the quality of the audio received by the system.

For the best results:

* Use the chapel sound system whenever possible.
* Minimize background noise.
* Speak clearly at a normal conversational pace.
* Use an external microphone if a chapel audio connection is not available.
* Ensure a reliable internet connection.
* When using phones or tablets, listeners should use headphones whenever possible.

''Images shown above were AI generated.''

{{DEFAULTSORT:AI Live Interpretation in Sacrament Meetings Pilot}}

AI Live Interpretation in Sacrament Meetings Pilot

2026-06-25T16:04:05Z

Ericjamee: Changes based off of feedback

{{DISPLAYTITLE:AI Live Interpretation Sacrament Meeting Pilot }}

=== '''<big>Overview</big>''' ===
This article explains how to set up and use the Lara Simultaneous Interpreter for sacrament meetings as part of an approved pilot program. The pilot is intended to help members receive real-time interpretation on their personal devices while allowing the Church to continue evaluating and improving the technology, translation quality, and overall user experience.

''Note: If your unit has not been invited to participate in the pilot, this article will not be applicable.''

'''Important'''

The quality of the interpretation depends primarily on the quality of the audio provided to the system. Clear, consistent audio produces significantly better translation results. For the best experience, follow the audio recommendations provided in this article.

No installation is required. Everything runs in a supported web browser.

== '''<big>How to Use the Lara Simultaneous Interpreter</big>''' ==
The system uses two roles:

* '''Speaker (Host)''': The person who starts and manages the interpretation session.
* '''Listener (Guest):''' The person who receives the interpreted audio and captions.

The Speaker shares a '''Listener link''' or '''QR code''' with participants so they can join the session.

No installation is required. The Speaker and Listener access Lara through a supported web browser.

=== '''<big>Speaker (Host)</big>''' ===

==== '''<big>Preparation</big>''' ====
Before the meeting:
A. Decide how you will share the Listener link (or QR code) and any feedback form with listeners.

B. Test the Speaker link and audio setup before the sacrament meeting.

C. If you are also using Zoom:

* If possible, use '''two devices'''—one for Zoom and one for Lara Simultaneous Interpreter—for the best performance.
* If only one device is available, access both Zoom and Lara through a web browser rather than using the desktop applications.

==== '''<big>Meeting Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Open the Speaker link you received
# Confirm the session shows “'''Ready to broadcast'''”
# When the meeting begins, click '''Start Recording'''
# Use the '''Start''' and '''Stop Recording''' as needed to control what is translated
# When finished, click '''Close Session''' to end the broadcast
[[File:Lara Speaker Graphic 1.png|none|thumb|360x360px]]

===== '''Important''': =====

* The Speaker does not select a language or configure interpretation settings. Simply click '''Start Recording''' and begin speaking.
* Only one Speaker (Host) should manage a session at a time.
* The top-right corner of the Speaker interface displays the current number of listeners connected to the session (This number includes the speaker).
* If your unit has more than one spoken language during a meeting (for example, testimonies in different languages), see '''Multiple Spoken Languages''' later in this article.

=== '''<big>Listener (Guest)</big>''' ===

==== '''<big>Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Scan the QR code or click on the Listener link provided for interpretation
# The Listener page opens with the session name
# Select your desired Target Language
# Click '''Connect'''
# Click the speaker icon to start listening to the real-time translation
## (6a)If the listener does not have headphones, they may choose to only read the captions.
[[File:Lara Listener Graphic.png|none|thumb|481x481px]]

*
== <big>'''APPENDIX'''</big> ==

=== <big>'''Key Reminders and Expectations'''</big> ===

==== '''Speaker (Host)''': ====
* Clear, consistent audio is the most important factor affecting interpretation quality. Review the '''Audio Recommendations''' below before each meeting.
* The Speaker must click '''Start Recording''' before listeners can receive interpretation.
* Speaker and Listener links remain the same each week unless new links are requested. To request new links, contact your Church Headquarters pilot coordinator.
* Do not share the Speaker link. Only the person managing the session should use it.
* Only one Speaker (Host) should manage a session at a time.
* If using Zoom and Lara Simultaneous Interpreter together, use separate devices when possible. If only one device is available, access both through a web browser.

==== '''Listener (Guest):''' ====
* Use a personal device to receive interpretation.
* When using a phone or tablet, headphones are strongly recommended to improve audio quality and help prevent feedback.
* Listeners may join after the Speaker has started the session.
* Each listener may select a different language.
* A delay between the original speech and the interpreted audio is expected.
* On-screen captions typically appear before the interpreted audio because audio processing requires additional time.

==== '''General:''' ====
* Lara Simultaneous Interpreter is currently being used as part of an approved pilot. Interpretation quality, features, and the overall user experience will continue to improve throughout the pilot.
* The quality of the interpretation depends primarily on the quality of the audio provided to the system.
* Everything runs in a supported web browser. No application installation is required.

=== '''<big>Audio Recommendations</big>''' ===
The quality of the interpretation depends primarily on the quality of the audio provided to Lara Simultaneous Interpreter. Clear audio will produce more accurate and natural interpretation, while poor audio may result in reduced accuracy, missed words, or increased delay.

==== '''<big>Speaker (Host)</big>''' ====
'''For the best interpretation quality:'''
* Whenever possible, connect the Speaker device directly to the chapel sound system.
* Minimize background noise near the Speaker device.
* Speak clearly, at a normal conversational pace, and avoid speaking excessively fast.
* Pause briefly between speakers or when changing languages to help the system process the audio.
* Use an external microphone if a direct chapel audio connection is not available.
* Ensure the Speaker device has a reliable internet connection.
* If using Zoom and Lara Simultaneous Interpreter at the same time, use separate devices when possible. If only one device is available, use a web browser for both applications.
To select the audio input, click the '''Settings''' button near the bottom of the Speaker page:[[File:Start Recording Graphic.png|none|thumb|468x468px]]

==== '''<big>Recommended audio setup (best to least preferred)</big>''' ====

===== '''1. Line-level audio from the chapel sound system (Best)''' =====
<blockquote>Connecting directly to the chapel sound system provides the clearest and most consistent audio and is the recommended setup whenever possible. [[File:Chapel image 1.png|none|thumb|429x429px]]''Example only; computer could be in a different location and may connect into the chapel's audio system differently.''</blockquote>

===== '''2. External Microphone''' =====
<blockquote>If a direct chapel audio connection is not available, use a dedicated external microphone (Like a bluetooth microphone) connected to the Speaker device. Position the microphone as close to the person speaking as practical while minimizing background noise.[[File:Pulpit image 1.png|none|thumb|426x426px]]</blockquote>

===== '''3. Built-in device microphone (least preferred)''' =====
<blockquote>If no external audio equipment is available, use the device’s built-in microphone.
For best results:

* Place the device as close as practical to the speaker.
* Keep the microphone unobstructed.
* Reduce nearby conversations and other background noise.
* Position the device where it has a strong and stable internet connection.

[[File:Pulpit image 2.png|none|thumb|411x411px]]</blockquote>If you need help connecting to the chapel audio system, contact your '''Facilities Manager.'''

=== '''<big>Multiple Spoken Languages</big>''' ===
If more than one language will be spoken during the meeting, you have two options:

==== '''Option 1: Autodetect Language Link''' ====

* Requires a separate Speaker link

* Uses a different Listener link than the primary session

* Automatically detects the language being spoken

'''Note:''' Interpretation quality may be lower when using autodetect.

Contact your pilot coordinator if you would like to use this option

==== '''Option 2: Separate Links for Each Language''' ====

* Request a separate Speaker link for each language

* Each Speaker link has a corresponding Listener link

This option may provide more consistent interpretation quality

== '''<big>Support and Troubleshooting</big>''' ==

=== Unable to connect to the “Liahona” Wi-Fi network ===
If someone cannot connect to the '''Liahona''' Wi-Fi network:

* Verify that the correct password has been entered.
* Confirm that the device is attempting to connect to '''Liahona''' rather than another wireless network.

=== Need additional assistance? ===
During the pilot:

'''Contact the Facilities Manager or submit a ticket using the Church’s Facilities Incident Reporting (FIR) mobile app if:'''

* The issue is related to the meetinghouse internet or Wi-Fi network.
* You need assistance connecting to the chapel audio system.
* There is a problem with the chapel audio system.

'''Contact your Area or Church Headquarters pilot coordinator if:'''

* The issue is related to the Lara by Translated website.
* You have questions about the pilot.
* You would like to request additional Speaker or Listener links.

= '''Frequently Asked Questions''' =

=== Can more than one Speaker (Host) manage a session? ===
No. Only one Speaker (Host) should manage a session at a time. Multiple hosts can create conflicts and may negatively affect session performance.
----

=== What if someone who needs interpretation does not have a personal device? ===
If a personal device is not available, one option is to display the text captions on a TV, projector, or other large display.

Lara Live provides a subtitle link specifically designed for larger displays.

To use this feature, replace '''<code>/listener/</code>''' with '''<code>/subtitle/</code>''' in the Listener URL.

'''Example'''

Change:

<code><nowiki>https://sim.laralive.com/listener/</nowiki>...</code>

To:

<code><nowiki>https://sim.laralive.com/subtitle/</nowiki>...</code>

Another option is to connect a device to a TV or projector in another room of the meetinghouse. The device can join the Listener link to play the interpreted audio while also displaying the captions, allowing participants to both hear the interpretation and read the captions.
[[File:AI-I laptop connected to TV in a classroom Large.jpg|none|thumb|496x496px]]
----

=== Why do the captions appear before the interpreted audio? ===
This is expected behavior.

Text captions can usually be displayed more quickly than interpreted audio because additional processing is required to generate natural-sounding speech. As a result, captions will often appear before the audio is heard.
----

=== What provides the best interpretation quality? ===
The quality of the interpretation depends primarily on the quality of the audio received by the system.

For the best results:

* Use the chapel sound system whenever possible.
* Minimize background noise.
* Speak clearly at a normal conversational pace.
* Use an external microphone if a chapel audio connection is not available.
* Ensure a reliable internet connection.
* When using phones or tablets, listeners should use headphones whenever possible.

''Images shown above were AI generated.''

{{DEFAULTSORT:AI Live Interpretation in Sacrament Meetings Pilot}}

File:AI-I laptop connected to TV in a classroom Large.jpg

2026-06-25T16:03:13Z

Ericjamee:

Photo

File:AI-I laptop connected to TV in a classroom Small.jpg

2026-06-25T16:01:48Z

Ericjamee:

photo

AI Live Interpretation in Sacrament Meetings Pilot

2026-06-16T20:14:34Z

Ericjamee:

{{DISPLAYTITLE:AI Live Interpretation Sacrament Meeting Pilot }}

=== '''<big>Overview</big>''' ===
This article explains how to set up and use the AI Live Interpretation tool for sacrament meetings as part of an approved pilot. This AI tool allows members to hear real-time translation on their personal devices during meetings

''Note: If your unit has not been invited to participate in the pilot, this article will not be applicable.''

== '''<big>How to Use the Lara Simultaneous Interpreter</big>''' ==
The system uses two roles:

* '''Speaker''': the host of the session (the person speaking)
* '''Listener''': the guest (the person listening to the translation)

The connection between the two happens through:

* A Speaker link
* A Listener QR code (to receive the translation)

No installation is required. Everything runs in the browser.

=== '''<big>Speaker (Host)</big>''' ===

==== '''<big>Preparation</big>''' ====
A. Decide how you will share the Listener link (or QR code) and feedback form to the “Listeners”

B. Test the '''Meeting Steps''' shown below before the sacrament meeting

==== '''<big>Meeting Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Open the Speaker link you received
# Confirm the session shows “'''Ready to broadcast'''”
# When the meeting begins, click '''Start Recording'''
# Use the '''Start''' and '''Stop Recording''' as needed to control what is translated
# When finished, click '''Close Session''' to end the broadcast
[[File:Lara Speaker Graphic 1.png|none|thumb|360x360px]]

===== '''Important''': =====
The Speaker does not select any language or configure settings. Simply click '''Start Recording''' and speak.

If your unit has more than one language spoken (for example, if testimonies are given in multiple languages), see the instructions below for using “Multiple Spoken Languages”''.''

=== '''<big>Listener (Guest)</big>''' ===

==== '''<big>Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Scan the QR code or click on the Listener link provided for interpretation
# The Listener page opens with the session name
# Select your desired Target Language
# Click '''Connect'''
# Click the speaker icon to start listening to the real-time translation
## (6a)If the listener does not have headphones, they may choose to only read the captions.
[[File:Lara Listener Graphic.png|none|thumb|481x481px]]

*
== <big>'''APPENDIX'''</big> ==

=== <big>'''Key Reminders and Expectations'''</big> ===

==== '''Speaker (Host)''': ====
* The Speaker (Host) must click '''Start Recording''' for the listeners to hear anything

* Speaker and Listener links remain the same each week unless new links are requested. To request new links, contact your headquarters

* Do not share the “Speaker” link (only those managing the session should us it)

* Clear audio is critical for accurate translation (see Audio Recommendations below)

==== '''Listener (Guest):''' ====
* Use a personal device and headphones (recommended)

* Listeners may join even after the Speaker has already started

* Each listener can select a different language

* Expect a short delay between speech and translation

* Faster speech or fewer pauses may increase the delay

==== '''General:''' ====
* Everything runs in a web browser (no app required)

=== '''<big>Audio Recommendations</big>''' ===
Clear audio is the most important factor for accurate interpretation

==== '''<big>Speaker (Host)</big>''' ====
* Use any device with a web browser and internet connection

* Select the audio input using the Settings button near the bottom of the page:

[[File:Start Recording Graphic.png|none|thumb|468x468px]]

==== '''<big>Recommended audio setup (best to least preferred)</big>''' ====

===== '''1. Line-level audio from the chapel sound system (best)''' =====
<blockquote>Provides the clearest and most consistent audio [[File:Chapel image 1.png|none|thumb|429x429px]]''Example only; computer could be in a different location and may connect into the chapel's audio system differently.''</blockquote>

===== '''2. External Microphone''' =====
<blockquote>Use a dedicated external microphone connected to the Speaker device (Host) (Bluetooth microphone for example)[[File:Pulpit image 1.png|none|thumb|426x426px]]</blockquote>

===== '''3. Built-in device microphone (least preferred)''' =====
<blockquote>Place the device (laptop or tablet) as close as possible to the speaker[[File:Pulpit image 2.png|none|thumb|411x411px]]</blockquote>If you need help connecting to the chapel audio system, contact your '''Facilities Manager.'''

=== '''<big>Multiple Spoken Languages</big>''' ===
If more than one language will be spoken during the meeting, you have two options:

==== '''Option 1: Autodetect Language Link''' ====

* Requires a separate Speaker link

* Uses a different Listener link than the primary session

* Automatically detects the language being spoken

'''Note:''' Interpretation quality may be lower when using autodetect.

Contact your pilot coordinator if you would like to use this option

==== '''Option 2: Separate Links for Each Language''' ====

* Request a separate Speaker link for each language

* Each Speaker link has a corresponding Listener link

This option may provide more consistent interpretation quality

=== '''<big>Support and Troubleshooting</big>''' ===

* If someone cannot connect to the “Liahona” Wi-Fi network:
** Check that the password that they entered for “Liahona” is correct.
** Confirm that their device is trying to connect to "Liahona" and not another Wi-Fi network.
** If others are also unable to connect to “Liahona” additional troubleshooting may be needed [[Troubleshooting Wireless Access Points]]

* During the pilot, if you have a question or issue that you cannot resolve:
** Contact the Facilities Manager or submit a ticket in the Church’s Facilities Incident Reporting (FIR) mobile app, if:
*** It is related to the meetinghouse internet/WI-FI-network
*** You need assistance connecting to the chapel’s audio system.
*** There is a problem with the chapel’s audio system.
** Email the Area or Church Headquarters contact who provided you with the other pilot information, if:
*** It is related to the Lara by Translated website.
*** You have questions about the pilot.
''Images shown above were AI generated.''

{{DEFAULTSORT:AI Live Interpretation in Sacrament Meetings Pilot}}

AI Live Interpretation in Sacrament Meetings Pilot

2026-06-16T20:09:51Z

Ericjamee: Taking out Feedback section

{{DISPLAYTITLE:AI Live Interpretation Sacrament Meeting Pilot }}

=== '''<big>Overview</big>''' ===
This article explains how to set up and use the AI Live Interpretation tool for sacrament meetings as part of an approved pilot. This AI tool allows members to hear real-time translation on their personal devices during meetings

''Note: If your unit has not been invited to participate in the pilot, this article will not be applicable.''

== '''<big>How to Use the Lara Simultaneous Interpreter</big>''' ==
The system uses two roles:

* '''Speaker''': the host of the session (the person speaking)
* '''Listener''': the guest (the person listening to the translation)

The connection between the two happens through:

* A Speaker link
* A Listener QR code (to receive the translation)

No installation is required. Everything runs in the browser.

=== '''<big>Speaker (Host)</big>''' ===

==== '''<big>Preparation</big>''' ====
A. Decide how you will share the Listener link (or QR code) and feedback form to the “Listeners”

B. Test the '''Meeting Steps''' shown below before the sacrament meeting

==== '''<big>Meeting Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Open the Speaker link you received
# Confirm the session shows “'''Ready to broadcast'''”
# When the meeting begins, click '''Start Recording'''
# Use the '''Start''' and '''Stop Recording''' as needed to control what is translated
# When finished, click '''Close Session''' to end the broadcast
[[File:Lara Speaker Graphic 1.png|none|thumb|360x360px]]

===== '''Important''': =====
The Speaker does not select any language or configure settings. Simply click '''Start Recording''' and speak.

If your unit has more than one language spoken (for example, if testimonies are given in multiple languages), see the instructions below for using “Multiple Spoken Languages”''.''

=== '''<big>Listener (Guest)</big>''' ===

==== '''<big>Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Scan the QR code or click on the Listener link provided for interpretation
# The Listener page opens with the session name
# Select your desired Target Language
# Click '''Connect'''
# Click the speaker icon to start listening to the real-time translation
## (6a)If the listener does not have headphones, they may choose to only read the captions.
[[File:Lara Listener Graphic.png|none|thumb|481x481px]]

* 
== <big>'''APPENDIX'''</big> ==

=== <big>'''Key Reminders and Expectations'''</big> ===

==== '''Speaker (Host)''': ====
* The Speaker (Host) must click '''Start Recording''' for the listeners to hear anything

* Speaker and Listener links remain the same each week unless new links are requested. To request new links, contact your headquarters

* Do not share the “Speaker” link (only those managing the session should us it)

* Clear audio is critical for accurate translation (see Audio Recommendations below)

==== '''Listener (Guest):''' ====
* Use a personal device and headphones (recommended)

* Listeners may join even after the Speaker has already started

* Each listener can select a different language

* Expect a short delay between speech and translation

* Faster speech or fewer pauses may increase the delay

==== '''General:''' ====
* Everything runs in a web browser (no app required)

=== '''<big>Audio Recommendations</big>''' ===
Clear audio is the most important factor for accurate interpretation

==== '''<big>Speaker (Host)</big>''' ====
* Use any device with a web browser and internet connection

* Select the audio input using the Settings button near the bottom of the page:

[[File:Start Recording Graphic.png|none|thumb|468x468px]]

==== '''<big>Recommended audio setup (best to least preferred)</big>''' ====

===== '''1. Line-level audio from the chapel sound system (best)''' =====
<blockquote>Provides the clearest and most consistent audio [[File:Chapel image 1.png|none|thumb|429x429px]]''Example only; computer could be in a different location and may connect into the chapel's audio system differently.''</blockquote>

===== '''2. External Microphone''' =====
<blockquote>Use a dedicated external microphone connected to the Speaker device (Host) (Bluetooth microphone for example)[[File:Pulpit image 1.png|none|thumb|426x426px]]</blockquote>

===== '''3. Built-in device microphone (least preferred)''' =====
<blockquote>Place the device (laptop or tablet) as close as possible to the speaker[[File:Pulpit image 2.png|none|thumb|411x411px]]</blockquote>If you need help connecting to the chapel audio system, contact your '''Facilities Manager.'''

=== '''<big>Multiple Spoken Languages</big>''' ===
If more than one language will be spoken during the meeting, you have two options:

==== '''Option 1: Autodetect Language Link''' ====

* Requires a separate Speaker link

* Uses a different Listener link than the primary session

* Automatically detects the language being spoken

'''Note:''' Interpretation quality may be lower when using autodetect.

Contact your pilot coordinator if you would like to use this option

==== '''Option 2: Separate Links for Each Language''' ====

* Request a separate Speaker link for each language

* Each Speaker link has a corresponding Listener link

This option may provide more consistent interpretation quality

=== '''<big>Support and Troubleshooting</big>''' ===

* If someone cannot connect to the “Liahona” Wi-Fi network:
** Check that the password that they entered for “Liahona” is correct.
** Confirm that their device is trying to connect to "Liahona" and not another Wi-Fi network.
** If others are also unable to connect to “Liahona” additional troubleshooting may be needed [[Troubleshooting Wireless Access Points]]

* During the pilot, if you have a question or issue that you cannot resolve:
** Contact the Facilities Manager or submit a ticket in the Church’s Facilities Incident Reporting (FIR) mobile app, if:
*** It is related to the meetinghouse internet/WI-FI-network
*** You need assistance connecting to the chapel’s audio system.
*** There is a problem with the chapel’s audio system.
** Email the Area or Church Headquarters contact who provided you with the other pilot information, if:
*** It is related to the Lara by Translated website.
*** You have questions about the pilot.
''Images shown above were AI generated.''

{{DEFAULTSORT:AI Live Interpretation in Sacrament Meetings Pilot}}

AI Live Interpretation in Sacrament Meetings Pilot

2026-05-06T21:03:08Z

Ericjamee:

{{DISPLAYTITLE:AI Live Interpretation Sacrament Meeting Pilot }}

=== '''<big>Overview</big>''' ===
This article explains how to set up and use the AI Live Interpretation tool for sacrament meetings as part of an approved pilot. This AI tool allows members to hear real-time translation on their personal devices during meetings

''Note: If your unit has not been invited to participate in the pilot, this article will not be applicable.''

== '''<big>How to Use the Lara Simultaneous Interpreter</big>''' ==
The system uses two roles:

* '''Speaker''': the host of the session (the person speaking)
* '''Listener''': the guest (the person listening to the translation)

The connection between the two happens through:

* A Speaker link
* A Listener QR code (to receive the translation)

No installation is required. Everything runs in the browser.

=== '''<big>Speaker (Host)</big>''' ===

==== '''<big>Preparation</big>''' ====
A. Decide how you will share the Listener link (or QR code) and feedback form to the “Listeners”

B. Test the '''Meeting Steps''' shown below before the sacrament meeting

==== '''<big>Meeting Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Open the Speaker link you received
# Confirm the session shows “'''Ready to broadcast'''”
# When the meeting begins, click '''Start Recording'''
# Use the '''Start''' and '''Stop Recording''' as needed to control what is translated
# When finished, click '''Close Session''' to end the broadcast
[[File:Lara Speaker Graphic 1.png|none|thumb|360x360px]]

===== '''Important''': =====
The Speaker does not select any language or configure settings. Simply click '''Start Recording''' and speak.

If your unit has more than one language spoken (for example, if testimonies are given in multiple languages), see the instructions below for using “Multiple Spoken Languages”''.''

=== '''<big>Listener (Guest)</big>''' ===

==== '''<big>Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Scan the QR code or click on the Listener link provided for interpretation
# The Listener page opens with the session name
# Select your desired Target Language
# Click '''Connect'''
# Click the speaker icon to start listening to the real-time translation
## (6a)If the listener does not have headphones, they may choose to only read the captions.
[[File:Lara Listener Graphic.png|none|thumb|481x481px]]

=== '''Feedback Surveys Instructions''' ===
At the end of the meeting, please submit your feedback and request everyone who listened to the interpretation also submit their feedback. This is an important part of the pilot.

* Speaker (Host):  [link]

* Listener (Guest):  [link]

== <big>'''APPENDIX'''</big> ==

=== <big>'''Key Reminders and Expectations'''</big> ===

==== '''Speaker (Host)''': ====
* The Speaker (Host) must click '''Start Recording''' for the listeners to hear anything

* Speaker and Listener links remain the same each week unless new links are requested. To request new links, contact your headquarters

* Do not share the “Speaker” link (only those managing the session should us it)

* Clear audio is critical for accurate translation (see Audio Recommendations below)

==== '''Listener (Guest):''' ====
* Use a personal device and headphones (recommended)

* Listeners may join even after the Speaker has already started

* Each listener can select a different language

* Expect a short delay between speech and translation

* Faster speech or fewer pauses may increase the delay

==== '''General:''' ====
* Everything runs in a web browser (no app required)

=== '''<big>Audio Recommendations</big>''' ===
Clear audio is the most important factor for accurate interpretation

==== '''<big>Speaker (Host)</big>''' ====
* Use any device with a web browser and internet connection

* Select the audio input using the Settings button near the bottom of the page:

[[File:Start Recording Graphic.png|none|thumb|468x468px]]

==== '''<big>Recommended audio setup (best to least preferred)</big>''' ====

===== '''1. Line-level audio from the chapel sound system (best)''' =====
<blockquote>Provides the clearest and most consistent audio [[File:Chapel image 1.png|none|thumb|429x429px]]''Example only; computer could be in a different location and may connect into the chapel's audio system differently.''</blockquote>

===== '''2. External Microphone''' =====
<blockquote>Use a dedicated external microphone connected to the Speaker device (Host) (Bluetooth microphone for example)[[File:Pulpit image 1.png|none|thumb|426x426px]]</blockquote>

===== '''3. Built-in device microphone (least preferred)''' =====
<blockquote>Place the device (laptop or tablet) as close as possible to the speaker[[File:Pulpit image 2.png|none|thumb|411x411px]]</blockquote>If you need help connecting to the chapel audio system, contact your '''Facilities Manager.'''

=== '''<big>Multiple Spoken Languages</big>''' ===
If more than one language will be spoken during the meeting, you have two options:

==== '''Option 1: Autodetect Language Link''' ====

* Requires a separate Speaker link

* Uses a different Listener link than the primary session

* Automatically detects the language being spoken

'''Note:''' Interpretation quality may be lower when using autodetect.

Contact your pilot coordinator if you would like to use this option

==== '''Option 2: Separate Links for Each Language''' ====

* Request a separate Speaker link for each language

* Each Speaker link has a corresponding Listener link

This option may provide more consistent interpretation quality

=== '''<big>Support and Troubleshooting</big>''' ===

* If someone cannot connect to the “Liahona” Wi-Fi network:
** Check that the password that they entered for “Liahona” is correct.
** Confirm that their device is trying to connect to "Liahona" and not another Wi-Fi network.
** If others are also unable to connect to “Liahona” additional troubleshooting may be needed [[Troubleshooting Wireless Access Points]]

* During the pilot, if you have a question or issue that you cannot resolve:
** Contact the Facilities Manager or submit a ticket in the Church’s Facilities Incident Reporting (FIR) mobile app, if:
*** It is related to the meetinghouse internet/WI-FI-network
*** You need assistance connecting to the chapel’s audio system.
*** There is a problem with the chapel’s audio system.
** Email the Area or Church Headquarters contact who provided you with the other pilot information, if:
*** It is related to the Lara by Translated website.
*** You have questions about the pilot.
''Images shown above were AI generated.''

{{DEFAULTSORT:AI Live Interpretation in Sacrament Meetings Pilot}}

File:Pulpit image 2.png

2026-05-06T21:02:51Z

Ericjamee:

pulpit

File:Pulpit image 1.png

2026-05-06T21:01:18Z

Ericjamee:

pulpit

AI Live Interpretation in Sacrament Meetings Pilot

2026-05-06T20:48:03Z

Ericjamee:

{{DISPLAYTITLE:AI Live Interpretation Sacrament Meeting Pilot }}

=== '''<big>Overview</big>''' ===
This article explains how to set up and use the AI Live Interpretation tool for sacrament meetings as part of an approved pilot. This AI tool allows members to hear real-time translation on their personal devices during meetings

''Note: If your unit has not been invited to participate in the pilot, this article will not be applicable.''

== '''<big>How to Use the Lara Simultaneous Interpreter</big>''' ==
The system uses two roles:

* '''Speaker''': the host of the session (the person speaking)
* '''Listener''': the guest (the person listening to the translation)

The connection between the two happens through:

* A Speaker link
* A Listener QR code (to receive the translation)

No installation is required. Everything runs in the browser.

=== '''<big>Speaker (Host)</big>''' ===

==== '''<big>Preparation</big>''' ====
A. Decide how you will share the Listener link (or QR code) and feedback form to the “Listeners”

B. Test the '''Meeting Steps''' shown below before the sacrament meeting

==== '''<big>Meeting Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Open the Speaker link you received
# Confirm the session shows “'''Ready to broadcast'''”
# When the meeting begins, click '''Start Recording'''
# Use the '''Start''' and '''Stop Recording''' as needed to control what is translated
# When finished, click '''Close Session''' to end the broadcast
[[File:Lara Speaker Graphic 1.png|none|thumb|360x360px]]

===== '''Important''': =====
The Speaker does not select any language or configure settings. Simply click '''Start Recording''' and speak.

If your unit has more than one language spoken (for example, if testimonies are given in multiple languages), see the instructions below for using “Multiple Spoken Languages”''.''

=== '''<big>Listener (Guest)</big>''' ===

==== '''<big>Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Scan the QR code or click on the Listener link provided for interpretation
# The Listener page opens with the session name
# Select your desired Target Language
# Click '''Connect'''
# Click the speaker icon to start listening to the real-time translation
## (6a)If the listener does not have headphones, they may choose to only read the captions.
[[File:Lara Listener Graphic.png|none|thumb|481x481px]]

=== '''Feedback Surveys Instructions''' ===
At the end of the meeting, please submit your feedback and request everyone who listened to the interpretation also submit their feedback. This is an important part of the pilot.

* Speaker (Host):  [link]

* Listener (Guest):  [link]

== <big>'''APPENDIX'''</big> ==

=== <big>'''Key Reminders and Expectations'''</big> ===

==== '''Speaker (Host)''': ====
* The Speaker (Host) must click '''Start Recording''' for the listeners to hear anything

* Speaker and Listener links remain the same each week unless new links are requested. To request new links, contact your headquarters

* Do not share the “Speaker” link (only those managing the session should us it)

* Clear audio is critical for accurate translation (see Audio Recommendations below)

==== '''Listener (Guest):''' ====
* Use a personal device and headphones (recommended)

* Listeners may join even after the Speaker has already started

* Each listener can select a different language

* Expect a short delay between speech and translation

* Faster speech or fewer pauses may increase the delay

==== '''General:''' ====
* Everything runs in a web browser (no app required)

=== '''<big>Audio Recommendations</big>''' ===
Clear audio is the most important factor for accurate interpretation

==== '''<big>Speaker (Host)</big>''' ====
* Use any device with a web browser and internet connection

* Select the audio input using the Settings button near the bottom of the page:

[[File:Start Recording Graphic.png|none|thumb|468x468px]]

==== '''<big>Recommended audio setup (best to least preferred)</big>''' ====

===== '''1. Line-level audio from the chapel sound system (best)''' =====
<blockquote>Provides the clearest and most consistent audio [[File:Chapel image 1.png|none|thumb|429x429px]]''Example only; computer could be in a different location and may connect into the chapel's audio system differently.''</blockquote>

===== '''2. External Microphone''' =====
<blockquote>Use a dedicated external microphone connected to the Speaker device (Host) (Bluetooth microphone for example)[[File:Pulpit Image 2.png|none|thumb|422x422px]]</blockquote>

===== '''3. Built-in device microphone (least preferred)''' =====
<blockquote>Place the device (laptop or tablet) as close as possible to the speaker[[File:Pulpit image 3.png|none|thumb|275x275px]]</blockquote>If you need help connecting to the chapel audio system, contact your '''Facilities Manager.'''

=== '''<big>Multiple Spoken Languages</big>''' ===
If more than one language will be spoken during the meeting, you have two options:

==== '''Option 1: Autodetect Language Link''' ====

* Requires a separate Speaker link

* Uses a different Listener link than the primary session

* Automatically detects the language being spoken

'''Note:''' Interpretation quality may be lower when using autodetect.

Contact your pilot coordinator if you would like to use this option

==== '''Option 2: Separate Links for Each Language''' ====

* Request a separate Speaker link for each language

* Each Speaker link has a corresponding Listener link

This option may provide more consistent interpretation quality

=== '''<big>Support and Troubleshooting</big>''' ===

* If someone cannot connect to the “Liahona” Wi-Fi network:
** Check that the password that they entered for “Liahona” is correct.
** Confirm that their device is trying to connect to "Liahona" and not another Wi-Fi network.
** If others are also unable to connect to “Liahona” additional troubleshooting may be needed [[Troubleshooting Wireless Access Points]]

* During the pilot, if you have a question or issue that you cannot resolve:
** Contact the Facilities Manager or submit a ticket in the Church’s Facilities Incident Reporting (FIR) mobile app, if:
*** It is related to the meetinghouse internet/WI-FI-network
*** You need assistance connecting to the chapel’s audio system.
*** There is a problem with the chapel’s audio system.
** Email the Area or Church Headquarters contact who provided you with the other pilot information, if:
*** It is related to the Lara by Translated website.
*** You have questions about the pilot.
''Images shown above were AI generated.''

{{DEFAULTSORT:AI Live Interpretation in Sacrament Meetings Pilot}}

AI Live Interpretation in Sacrament Meetings Pilot

2026-05-06T15:52:35Z

Ericjamee: Title Change

{{DISPLAYTITLE:AI Live Interpretation Sacrament Meeting Pilot }}

=== '''<big>Overview</big>''' ===
This article explains how to set up and use the AI Live Interpretation tool for sacrament meetings as part of an approved pilot. This AI tool allows members to hear real-time translation on their personal devices during meetings

''Note: If your unit has not been invited to participate in the pilot, this article will not be applicable.''

== '''<big>How to Use the Lara Simultaneous Interpreter</big>''' ==
The system uses two roles:

* '''Speaker''': the host of the session (the person speaking)
* '''Listener''': the guest (the person listening to the translation)

The connection between the two happens through:

* A Speaker link
* A Listener QR code (to receive the translation)

No installation is required. Everything runs in the browser.

=== '''<big>Speaker (Host)</big>''' ===

==== '''<big>Preparation</big>''' ====
A. Decide how you will share the Listener link (or QR code) and feedback form to the “Listeners”

B. Test the '''Meeting Steps''' shown below before the sacrament meeting

==== '''<big>Meeting Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Open the Speaker link you received
# Confirm the session shows “'''Ready to broadcast'''”
# When the meeting begins, click '''Start Recording'''
# Use the '''Start''' and '''Stop Recording''' as needed to control what is translated
# When finished, click '''Close Session''' to end the broadcast
[[File:Lara Speaker Graphic 1.png|none|thumb|360x360px]]

===== '''Important''': =====
The Speaker does not select any language or configure settings. Simply click '''Start Recording''' and speak.

If your unit has more than one language spoken (for example, if testimonies are given in multiple languages), see the instructions below for using “Multiple Spoken Languages”''.''

=== '''<big>Listener (Guest)</big>''' ===

==== '''<big>Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Scan the QR code or click on the Listener link provided for interpretation
# The Listener page opens with the session name
# Select your desired Target Language
# Click '''Connect'''
# Click the speaker icon to start listening to the real-time translation
## (6a)If the listener does not have headphones, they may choose to only read the captions.
[[File:Lara Listener Graphic.png|none|thumb|481x481px]]

=== '''Feedback Surveys Instructions''' ===
At the end of the meeting, please submit your feedback and request everyone who listened to the interpretation also submit their feedback. This is an important part of the pilot.

* Speaker (Host):  [link]

* Listener (Guest):  [link]

== <big>'''APPENDIX'''</big> ==

=== <big>'''Key Reminders and Expectations'''</big> ===

==== '''Speaker (Host)''': ====
* The Speaker (Host) must click '''Start Recording''' for the listeners to hear anything

* Speaker and Listener links remain the same each week unless new links are requested. To request new links, contact your headquarters

* Do not share the “Speaker” link (only those managing the session should us it)

* Clear audio is critical for accurate translation (see Audio Recommendations below)

==== '''Listener (Guest):''' ====
* Use a personal device and headphones (recommended)

* Listeners may join even after the Speaker has already started

* Each listener can select a different language

* Expect a short delay between speech and translation

* Faster speech or fewer pauses may increase the delay

==== '''General:''' ====
* Everything runs in a web browser (no app required)

=== '''<big>Audio Recommendations</big>''' ===
Clear audio is the most important factor for accurate interpretation

==== '''<big>Speaker (Host)</big>''' ====
* Use any device with a web browser and internet connection

* Select the audio input using the Settings button near the bottom of the page:

[[File:Start Recording Graphic.png|none|thumb|468x468px]]

==== '''<big>Recommended audio setup (best to least preferred)</big>''' ====

===== '''1. Line-level audio from the chapel sound system (best)''' =====
<blockquote>Provides the clearest and most consistent audio [[File:Chapel image 1.png|none|thumb|429x429px]]''Example only; computer could be in a different location and may connect into the chapel's audio system differently.''</blockquote>

===== '''2. External Microphone''' =====
<blockquote>Use a dedicated external microphone connected to the Speaker device (Host) (Bluetooth microphone for example)[[File:Pulpit Image 2.png|none|thumb|422x422px]]</blockquote>

===== '''3. Built-in device microphone (least preferred)''' =====
<blockquote>Place the device (laptop or tablet) as close as possible to the speaker[[File:Pulpit image 3.png|none|thumb|275x275px]]</blockquote>If you need help connecting to the chapel audio system, contact your '''Facilities Manager.'''

=== '''<big>Multiple Spoken Languages</big>''' ===
If more than one language will be spoken during the meeting, you have two options:

==== '''Option 1: Autodetect Language Link''' ====

* Requires a separate Speaker link

* Uses a different Listener link than the primary session

* Automatically detects the language being spoken

'''Note:''' Interpretation quality may be lower when using autodetect.

Contact your pilot coordinator if you would like to use this option

==== '''Option 2: Separate Links for Each Language''' ====

* Request a separate Speaker link for each language

* Each Speaker link has a corresponding Listener link

This option may provide more consistent interpretation quality

=== '''<big>Support and Troubleshooting</big>''' ===

* If someone cannot connect to the “Liahona” Wi-Fi network:
** Check that the password that they entered for “Liahona” is correct.
** Confirm that their device is trying to connect to "Liahona" and not another Wi-Fi network.
** If others are also unable to connect to “Liahona” additional troubleshooting may be needed [[Troubleshooting Wireless Access Points]]

* During the pilot, if you have a question or issue that you cannot resolve:
** Contact the Facilities Manager or submit a ticket in the Church’s Facilities Incident Reporting (FIR) mobile app, if:
*** It is related to the meetinghouse internet/WI-FI-network
*** You need assistance connecting to the chapel’s audio system.
*** There is a problem with the chapel’s audio system.

* Email the Area or Church Headquarters contact who provided you with the other pilot information, if:
** It is related to the Lara by Translated website.
** You have questions about the pilot.
''Images shown above were AI generated.''

{{DEFAULTSORT:AI Live Interpretation in Sacrament Meetings Pilot}}

AI Live Interpretation Sacrament Meeting Pilot

2026-05-06T15:50:04Z

Ericjamee: Ericjamee moved page AI Live Interpretation Sacrament Meeting Pilot to AI Live Interpretation in Sacrament Meetings Pilot

#REDIRECT [[AI Live Interpretation in Sacrament Meetings Pilot]]

AI Live Interpretation in Sacrament Meetings Pilot

2026-05-06T15:50:04Z

Ericjamee: Ericjamee moved page AI Live Interpretation Sacrament Meeting Pilot to AI Live Interpretation in Sacrament Meetings Pilot

{{DISPLAYTITLE:AI Live Interpretation Sacrament Meeting Pilot }}
{{DISPLAYTITLE:AI Live Interpretation in Sacrament Meetings Pilot}}
{{DISPLAYTITLE:Translated WIKI AI Live Interpretation Page 2026 }}

=== '''<big>Overview</big>''' ===
This article explains how to set up and use the AI Live Interpretation tool for sacrament meetings as part of an approved pilot. This AI tool allows members to hear real-time translation on their personal devices during meetings

''Note: If your unit has not been invited to participate in the pilot, this article will not be applicable.''

== '''<big>How to Use the Lara Simultaneous Interpreter</big>''' ==
The system uses two roles:

* '''Speaker''': the host of the session (the person speaking)
* '''Listener''': the guest (the person listening to the translation)

The connection between the two happens through:

* A Speaker link
* A Listener QR code (to receive the translation)

No installation is required. Everything runs in the browser.

=== '''<big>Speaker (Host)</big>''' ===

==== '''<big>Preparation</big>''' ====
A. Decide how you will share the Listener link (or QR code) and feedback form to the “Listeners”

B. Test the '''Meeting Steps''' shown below before the sacrament meeting

==== '''<big>Meeting Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Open the Speaker link you received
# Confirm the session shows “'''Ready to broadcast'''”
# When the meeting begins, click '''Start Recording'''
# Use the '''Start''' and '''Stop Recording''' as needed to control what is translated
# When finished, click '''Close Session''' to end the broadcast
[[File:Lara Speaker Graphic 1.png|none|thumb|360x360px]]

===== '''Important''': =====
The Speaker does not select any language or configure settings. Simply click '''Start Recording''' and speak.

If your unit has more than one language spoken (for example, if testimonies are given in multiple languages), see the instructions below for using “Multiple Spoken Languages”''.''

=== '''<big>Listener (Guest)</big>''' ===

==== '''<big>Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Scan the QR code or click on the Listener link provided for interpretation
# The Listener page opens with the session name
# Select your desired Target Language
# Click '''Connect'''
# Click the speaker icon to start listening to the real-time translation
## (6a)If the listener does not have headphones, they may choose to only read the captions.
[[File:Lara Listener Graphic.png|none|thumb|481x481px]]

=== '''Feedback Surveys Instructions''' ===
At the end of the meeting, please submit your feedback and request everyone who listened to the interpretation also submit their feedback. This is an important part of the pilot.

* Speaker (Host):  [link]

* Listener (Guest):  [link]

== <big>'''APPENDIX'''</big> ==

=== <big>'''Key Reminders and Expectations'''</big> ===

==== '''Speaker (Host)''': ====
* The Speaker (Host) must click '''Start Recording''' for the listeners to hear anything

* Speaker and Listener links remain the same each week unless new links are requested. To request new links, contact your headquarters

* Do not share the “Speaker” link (only those managing the session should us it)

* Clear audio is critical for accurate translation (see Audio Recommendations below)

==== '''Listener (Guest):''' ====
* Use a personal device and headphones (recommended)

* Listeners may join even after the Speaker has already started

* Each listener can select a different language

* Expect a short delay between speech and translation

* Faster speech or fewer pauses may increase the delay

==== '''General:''' ====
* Everything runs in a web browser (no app required)

=== '''<big>Audio Recommendations</big>''' ===
Clear audio is the most important factor for accurate interpretation

==== '''<big>Speaker (Host)</big>''' ====
* Use any device with a web browser and internet connection

* Select the audio input using the Settings button near the bottom of the page:

[[File:Start Recording Graphic.png|none|thumb|468x468px]]

==== '''<big>Recommended audio setup (best to least preferred)</big>''' ====

===== '''1. Line-level audio from the chapel sound system (best)''' =====
<blockquote>Provides the clearest and most consistent audio [[File:Chapel image 1.png|none|thumb|429x429px]]''Example only; computer could be in a different location and may connect into the chapel's audio system differently.''</blockquote>

===== '''2. External Microphone''' =====
<blockquote>Use a dedicated external microphone connected to the Speaker device (Host) (Bluetooth microphone for example)[[File:Pulpit Image 2.png|none|thumb|422x422px]]</blockquote>

===== '''3. Built-in device microphone (least preferred)''' =====
<blockquote>Place the device (laptop or tablet) as close as possible to the speaker[[File:Pulpit image 3.png|none|thumb|275x275px]]</blockquote>If you need help connecting to the chapel audio system, contact your '''Facilities Manager.'''

=== '''<big>Multiple Spoken Languages</big>''' ===
If more than one language will be spoken during the meeting, you have two options:

==== '''Option 1: Autodetect Language Link''' ====

* Requires a separate Speaker link

* Uses a different Listener link than the primary session

* Automatically detects the language being spoken

'''Note:''' Interpretation quality may be lower when using autodetect.

Contact your pilot coordinator if you would like to use this option

==== '''Option 2: Separate Links for Each Language''' ====

* Request a separate Speaker link for each language

* Each Speaker link has a corresponding Listener link

This option may provide more consistent interpretation quality

=== '''<big>Support and Troubleshooting</big>''' ===

* If someone cannot connect to the “Liahona” Wi-Fi network:
** Check that the password that they entered for “Liahona” is correct.
** Confirm that their device is trying to connect to "Liahona" and not another Wi-Fi network.
** If others are also unable to connect to “Liahona” additional troubleshooting may be needed [[Troubleshooting Wireless Access Points]]

* During the pilot, if you have a question or issue that you cannot resolve:
** Contact the Facilities Manager or submit a ticket in the Church’s Facilities Incident Reporting (FIR) mobile app, if:
*** It is related to the meetinghouse internet/WI-FI-network
*** You need assistance connecting to the chapel’s audio system.
*** There is a problem with the chapel’s audio system.

* Email the Area or Church Headquarters contact who provided you with the other pilot information, if:
** It is related to the Lara by Translated website.
** You have questions about the pilot.
''Images shown above were AI generated.''

{{DEFAULTSORT:AI Live Interpretation in Sacrament Meetings Pilot}}

AI Live Interpretation in Sacrament Meetings Pilot

2026-05-06T15:47:27Z

Ericjamee:

AI Live Interpretation in Sacrament Meetings Pilot

2026-05-06T15:41:24Z

Ericjamee:

{{DISPLAYTITLE:AI Live Interpretation in Sacrament Meetings Pilot}}
{{DISPLAYTITLE:Translated WIKI AI Live Interpretation Page 2026 }}

=== '''<big>Overview</big>''' ===
This article explains how to set up and use the AI Live Interpretation tool for sacrament meetings as part of an approved pilot. This AI tool allows members to hear real-time translation on their personal devices during meetings

''Note: If your unit has not been invited to participate in the pilot, this article will not be applicable.''

== '''<big>How to Use the Lara Simultaneous Interpreter</big>''' ==
The system uses two roles:

* '''Speaker''': the host of the session (the person speaking)
* '''Listener''': the guest (the person listening to the translation)

The connection between the two happens through:

* A Speaker link
* A Listener QR code (to receive the translation)

No installation is required. Everything runs in the browser.

=== '''<big>Speaker (Host)</big>''' ===

==== '''<big>Preparation</big>''' ====
A. Decide how you will share the Listener link (or QR code) and feedback form to the “Listeners”

B. Test the '''Meeting Steps''' shown below before the sacrament meeting

==== '''<big>Meeting Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Open the Speaker link you received
# Confirm the session shows “'''Ready to broadcast'''”
# When the meeting begins, click '''Start Recording'''
# Use the '''Start''' and '''Stop Recording''' as needed to control what is translated
# When finished, click '''Close Session''' to end the broadcast
[[File:Lara Speaker Graphic 1.png|none|thumb|360x360px]]

===== '''Important''': =====
The Speaker does not select any language or configure settings. Simply click '''Start Recording''' and speak.

If your unit has more than one language spoken (for example, if testimonies are given in multiple languages), see the instructions below for using “Multiple Spoken Languages”''.''

=== '''<big>Listener (Guest)</big>''' ===

==== '''<big>Steps</big>''' ====
# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Scan the QR code or click on the Listener link provided for interpretation
# The Listener page opens with the session name
# Select your desired Target Language
# Click '''Connect'''
# Click the speaker icon to start listening to the real-time translation
## (6a)If the listener does not have headphones, they may choose to only read the captions.
[[File:Lara Listener Graphic.png|none|thumb|481x481px]]

=== '''Feedback Surveys Instructions''' ===
At the end of the meeting, please submit your feedback and request everyone who listened to the interpretation also submit their feedback. This is an important part of the pilot.

* Speaker (Host):  [link]

* Listener (Guest):  [link]

== <big>'''APPENDIX'''</big> ==

=== <big>'''Key Reminders and Expectations'''</big> ===

==== '''Speaker (Host)''': ====
* The Speaker (Host) must click '''Start Recording''' for the listeners to hear anything

* Speaker and Listener links remain the same each week unless new links are requested. To request new links, contact your headquarters

* Do not share the “Speaker” link (only those managing the session should us it)

* Clear audio is critical for accurate translation (see Audio Recommendations below)

==== '''Listener (Guest):''' ====
* Use a personal device and headphones (recommended)

* Listeners may join even after the Speaker has already started

* Each listener can select a different language

* Expect a short delay between speech and translation

* Faster speech or fewer pauses may increase the delay

==== '''General:''' ====
* Everything runs in a web browser (no app required)

=== '''<big>Audio Recommendations</big>''' ===
Clear audio is the most important factor for accurate interpretation

==== '''<big>Speaker (Host)</big>''' ====
* Use any device with a web browser and internet connection

* Select the audio input using the Settings button near the bottom of the page:

[[File:Start Recording Graphic.png|none|thumb|468x468px]]

==== '''<big>Recommended audio setup (best to least preferred)</big>''' ====

===== '''1. Line-level audio from the chapel sound system (best)''' =====
<blockquote>Provides the clearest and most consistent audio [[File:Chapel image 1.png|none|thumb|429x429px]]''Example only; computer could be in a different location and may connect into the chapel's audio system differently.''</blockquote>

===== '''2. External Microphone''' =====
<blockquote>Use a dedicated external microphone connected to the Speaker device (Host) (Bluetooth microphone for example)[[File:Pulpit Image 2.png|none|thumb|422x422px]]</blockquote>

===== '''3. Built-in device microphone (least preferred)''' =====
<blockquote>Place the device (laptop or tablet) as close as possible to the speaker[[File:Pulpit image 3.png|none|thumb|275x275px]]</blockquote>If you need help connecting to the chapel audio system, contact your '''Facilities Manager.'''

=== '''<big>Multiple Spoken Languages</big>''' ===
If more than one language will be spoken during the meeting, you have two options:

==== '''Option 1: Autodetect Language Link''' ====

* Requires a separate Speaker link

* Uses a different Listener link than the primary session

* Automatically detects the language being spoken

'''Note:''' Interpretation quality may be lower when using autodetect.

Contact your pilot coordinator if you would like to use this option

==== '''Option 2: Separate Links for Each Language''' ====

* Request a separate Speaker link for each language

* Each Speaker link has a corresponding Listener link

This option may provide more consistent interpretation quality

=== '''<big>Support and Troubleshooting</big>''' ===

* If someone cannot connect to the “Liahona” Wi-Fi network:

** Check that the password that they entered for “Liahona” is correct.
** Confirm that their device is trying to connect to "Liahona" and not another Wi-Fi network.
** If others are also unable to connect to “Liahona” additional troubleshooting may be needed [[Troubleshooting Wireless Access Points]]

* During the pilot, if you have a question or issue that you cannot resolve:

** Contact the Facilities Manager or submit a ticket in the Church’s Facilities Incident Reporting (FIR) mobile app, if:

*** It is related to the meetinghouse internet/WI-FI-network
*** You need assistance connecting to the chapel’s audio system.
*** There is a problem with the chapel’s audio system.

* Email the Area or Church Headquarters contact who provided you with the other pilot information, if:

** It is related to the Lara by Translated website.
** You have questions about the pilot.
''Images shown above were AI generated.''

{{DEFAULTSORT:AI Live Interpretation in Sacrament Meetings Pilot}}

AI Live Interpretation in Sacrament Meetings Pilot

2026-05-06T15:35:34Z

Ericjamee:

{{DISPLAYTITLE:Translated WIKI AI Live Interpretation Page 2026 }}

=== '''<big>Overview</big>''' ===
This article explains how to set up and use the AI Live Interpretation tool for sacrament meetings as part of an approved pilot. This AI tool allows members to hear real-time translation on their personal devices during meetings

''Note: If your unit has not been invited to participate in the pilot, this article will not be applicable.''

== '''<big>How to Use the Lara Simultaneous Interpreter</big>''' ==
The system uses two roles:

* '''Speaker''': the host of the session (the person speaking)
* '''Listener''': the guest (the person listening to the translation)

The connection between the two happens through:

* A Speaker link
* A Listener QR code (to receive the translation)

No installation is required. Everything runs in the browser.

=== '''<big>Speaker (Host)</big>''' ===

=== '''Preparation''' ===
A. Decide how you will share the Listener link (or QR code) and feedback form to the “Listeners”

B. Test the '''Meeting Steps''' shown below before the sacrament meeting

=== '''Meeting Steps''' ===

# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Open the Speaker link you received
# Confirm the session shows “'''Ready to broadcast'''”
# When the meeting begins, click '''Start Recording'''
# Use the '''Start''' and '''Stop Recording''' as needed to control what is translated
# When finished, click '''Close Session''' to end the broadcast
[[File:Lara Speaker Graphic 1.png|none|thumb|360x360px]]

===== '''Important''': =====
The Speaker does not select any language or configure settings. Simply click '''Start Recording''' and speak.

If your unit has more than one language spoken (for example, if testimonies are given in multiple languages), see the instructions below for using “Multiple Spoken Languages”''.''

=== '''<big>Listener (Guest)</big>''' ===

=== '''Steps''' ===

# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Scan the QR code or click on the Listener link provided for interpretation
# The Listener page opens with the session name
# Select your desired Target Language
# Click '''Connect'''
# Click the speaker icon to start listening to the real-time translation
## (6a)If the listener does not have headphones, they may choose to only read the captions.
[[File:Lara Listener Graphic.png|none|thumb|481x481px]]

=== '''Feedback Surveys Instructions''' ===
At the end of the meeting, please submit your feedback and request everyone who listened to the interpretation also submit their feedback. This is an important part of the pilot.

* Speaker (Host):  [link]

* Listener (Guest):  [link]

== <big>'''APPENDIX'''</big> ==

==== <big>'''Key Reminders and Expectations'''</big> ====

==== '''Speaker (Host)''': ====
* The Speaker (Host) must click '''Start Recording''' for the listeners to hear anything

* Speaker and Listener links remain the same each week unless new links are requested. To request new links, contact your headquarters

* Do not share the “Speaker” link (only those managing the session should us it)

* Clear audio is critical for accurate translation (see Audio Recommendations below)

==== '''Listener (Guest):''' ====
* Use a personal device and headphones (recommended)

* Listeners may join even after the Speaker has already started

* Each listener can select a different language

* Expect a short delay between speech and translation

* Faster speech or fewer pauses may increase the delay

==== '''General:''' ====
* Everything runs in a web browser (no app required)

=== '''<big>Audio Recommendations</big>''' ===
Clear audio is the most important factor for accurate interpretation

=== '''Speaker (Host)''' ===

* Use any device with a web browser and internet connection

* Select the audio input using the Settings button near the bottom of the page:

[[File:Start Recording Graphic.png|none|thumb|468x468px]]

=== '''Recommended audio setup (best to least preferred)''' ===

===== '''1. Line-level audio from the chapel sound system (best)''' =====
<blockquote>Provides the clearest and most consistent audio [[File:Chapel image 1.png|none|thumb|429x429px]]''Example only; computer could be in a different location and may connect into the chapel's audio system differently.''</blockquote>

===== '''2. External Microphone''' =====
<blockquote>Use a dedicated external microphone connected to the Speaker device (Host) (Bluetooth microphone for example)[[File:Pulpit Image 2.png|none|thumb|422x422px]]</blockquote>

===== '''3. Built-in device microphone (least preferred)''' =====
<blockquote>Place the device (laptop or tablet) as close as possible to the speaker[[File:Pulpit image 3.png|none|thumb|275x275px]]</blockquote>If you need help connecting to the chapel audio system, contact your '''Facilities Manager.'''

=== '''Multiple Spoken Languages''' ===
If more than one language will be spoken during the meeting, you have two options:

==== '''Option 1: Autodetect Language Link''' ====

* Requires a separate Speaker link

* Uses a different Listener link than the primary session

* Automatically detects the language being spoken

'''Note:''' Interpretation quality may be lower when using autodetect.

Contact your pilot coordinator if you would like to use this option

==== '''Option 2: Separate Links for Each Language''' ====

* Request a separate Speaker link for each language

* Each Speaker link has a corresponding Listener link

This option may provide more consistent interpretation quality

=== '''Support and Troubleshooting''' ===

* If someone cannot connect to the “Liahona” Wi-Fi network:

** Check that the password that they entered for “Liahona” is correct.
** Confirm that their device is trying to connect to "Liahona" and not another Wi-Fi network.
** If others are also unable to connect to “Liahona” additional troubleshooting may be needed [[Troubleshooting Wireless Access Points]]

* During the pilot, if you have a question or issue that you cannot resolve:

** Contact the Facilities Manager or submit a ticket in the Church’s Facilities Incident Reporting (FIR) mobile app, if:

*** It is related to the meetinghouse internet/WI-FI-network
*** You need assistance connecting to the chapel’s audio system.
*** There is a problem with the chapel’s audio system.

* Email the Area or Church Headquarters contact who provided you with the other pilot information, if:

** It is related to the Lara by Translated website.
** You have questions about the pilot.
''Images shown above were AI generated.''

{{DEFAULTSORT:Translated WIKI AI Live Interpretation Page 2026 }}

AI Live Interpretation in Sacrament Meetings Pilot

2026-05-06T15:34:30Z

Ericjamee:

{{DISPLAYTITLE:Translated WIKI AI Live Interpretation Page 2026 }}

== '''<big>Overview</big>''' ==
This article explains how to set up and use the AI Live Interpretation tool for sacrament meetings as part of an approved pilot. This AI tool allows members to hear real-time translation on their personal devices during meetings

''Note: If your unit has not been invited to participate in the pilot, this article will not be applicable.''

=== '''<big>How to Use the Lara Simultaneous Interpreter</big>''' ===
The system uses two roles:

* '''Speaker''': the host of the session (the person speaking)
* '''Listener''': the guest (the person listening to the translation)

The connection between the two happens through:

* A Speaker link
* A Listener QR code (to receive the translation)

No installation is required. Everything runs in the browser.

=== '''<big>Speaker (Host)</big>''' ===

=== '''Preparation''' ===
A. Decide how you will share the Listener link (or QR code) and feedback form to the “Listeners”

B. Test the '''Meeting Steps''' shown below before the sacrament meeting

=== '''Meeting Steps''' ===

# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Open the Speaker link you received
# Confirm the session shows “'''Ready to broadcast'''”
# When the meeting begins, click '''Start Recording'''
# Use the '''Start''' and '''Stop Recording''' as needed to control what is translated
# When finished, click '''Close Session''' to end the broadcast
[[File:Lara Speaker Graphic 1.png|none|thumb|360x360px]]

===== '''Important''': =====
The Speaker does not select any language or configure settings. Simply click '''Start Recording''' and speak.

If your unit has more than one language spoken (for example, if testimonies are given in multiple languages), see the instructions below for using “Multiple Spoken Languages”''.''

=== '''<big>Listener (Guest)</big>''' ===

=== '''Steps''' ===

# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Scan the QR code or click on the Listener link provided for interpretation
# The Listener page opens with the session name
# Select your desired Target Language
# Click '''Connect'''
# Click the speaker icon to start listening to the real-time translation
## (6a)If the listener does not have headphones, they may choose to only read the captions.
[[File:Lara Listener Graphic.png|none|thumb|481x481px]]

=== '''Feedback Surveys Instructions''' ===
At the end of the meeting, please submit your feedback and request everyone who listened to the interpretation also submit their feedback. This is an important part of the pilot.

* Speaker (Host):  [link]

* Listener (Guest):  [link]

== <big>'''APPENDIX'''</big> ==

==== <big>'''Key Reminders and Expectations'''</big> ====

==== '''Speaker (Host)''': ====
* The Speaker (Host) must click '''Start Recording''' for the listeners to hear anything

* Speaker and Listener links remain the same each week unless new links are requested. To request new links, contact your headquarters

* Do not share the “Speaker” link (only those managing the session should us it)

* Clear audio is critical for accurate translation (see Audio Recommendations below)

==== '''Listener (Guest):''' ====
* Use a personal device and headphones (recommended)

* Listeners may join even after the Speaker has already started

* Each listener can select a different language

* Expect a short delay between speech and translation

* Faster speech or fewer pauses may increase the delay

==== '''General:''' ====
* Everything runs in a web browser (no app required)

=== '''<big>Audio Recommendations</big>''' ===
Clear audio is the most important factor for accurate interpretation

=== '''Speaker (Host)''' ===

* Use any device with a web browser and internet connection

* Select the audio input using the Settings button near the bottom of the page:

[[File:Start Recording Graphic.png|none|thumb|468x468px]]

=== '''Recommended audio setup (best to least preferred)''' ===

===== '''1. Line-level audio from the chapel sound system (best)''' =====
<blockquote>Provides the clearest and most consistent audio [[File:Chapel image 1.png|none|thumb|429x429px]]''Example only; computer could be in a different location and may connect into the chapel's audio system differently.''</blockquote>

===== '''2. External Microphone''' =====
<blockquote>Use a dedicated external microphone connected to the Speaker device (Host) (Bluetooth microphone for example)[[File:Pulpit Image 2.png|none|thumb|422x422px]]</blockquote>

===== '''3. Built-in device microphone (least preferred)''' =====
<blockquote>Place the device (laptop or tablet) as close as possible to the speaker[[File:Pulpit image 3.png|none|thumb|275x275px]]</blockquote>If you need help connecting to the chapel audio system, contact your '''Facilities Manager.'''

=== '''Multiple Spoken Languages''' ===
If more than one language will be spoken during the meeting, you have two options:

==== '''Option 1: Autodetect Language Link''' ====

* Requires a separate Speaker link

* Uses a different Listener link than the primary session

* Automatically detects the language being spoken

'''Note:''' Interpretation quality may be lower when using autodetect.

Contact your pilot coordinator if you would like to use this option

==== '''Option 2: Separate Links for Each Language''' ====

* Request a separate Speaker link for each language

* Each Speaker link has a corresponding Listener link

This option may provide more consistent interpretation quality

=== '''Support and Troubleshooting''' ===

* If someone cannot connect to the “Liahona” Wi-Fi network:

** Check that the password that they entered for “Liahona” is correct.
** Confirm that their device is trying to connect to "Liahona" and not another Wi-Fi network.
** If others are also unable to connect to “Liahona” additional troubleshooting may be needed [[Troubleshooting Wireless Access Points]]

* During the pilot, if you have a question or issue that you cannot resolve:

** Contact the Facilities Manager or submit a ticket in the Church’s Facilities Incident Reporting (FIR) mobile app, if:

*** It is related to the meetinghouse internet/WI-FI-network
*** You need assistance connecting to the chapel’s audio system.
*** There is a problem with the chapel’s audio system.

* Email the Area or Church Headquarters contact who provided you with the other pilot information, if:

** It is related to the Lara by Translated website.
** You have questions about the pilot.
''Images shown above were AI generated.''

{{DEFAULTSORT:Translated WIKI AI Live Interpretation Page 2026 }}

AI Live Interpretation in Sacrament Meetings Pilot

2026-05-06T15:33:10Z

Ericjamee: /* Key Reminders and Expectations */

{{DISPLAYTITLE:Translated WIKI AI Live Interpretation Page 2026 }}

== '''<big>Overview</big>''' ==
This article explains how to set up and use the AI Live Interpretation tool for sacrament meetings as part of an approved pilot. This AI tool allows members to hear real-time translation on their personal devices during meetings

''Note: If your unit has not been invited to participate in the pilot, this article will not be applicable.''

=== '''<big>How to Use the Lara Simultaneous Interpreter</big>''' ===
The system uses two roles:

* '''Speaker''': the host of the session (the person speaking)
* '''Listener''': the guest (the person listening to the translation)

The connection between the two happens through:

* A Speaker link
* A Listener QR code (to receive the translation)

No installation is required. Everything runs in the browser.

=== '''<big>Speaker (Host)</big>''' ===

=== '''Preparation''' ===
A. Decide how you will share the Listener link (or QR code) and feedback form to the “Listeners”

B. Test the '''Meeting Steps''' shown below before the sacrament meeting

=== '''Meeting Steps''' ===

# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Open the Speaker link you received
# Confirm the session shows “'''Ready to broadcast'''”
# When the meeting begins, click '''Start Recording'''
# Use the '''Start''' and '''Stop Recording''' as needed to control what is translated
# When finished, click '''Close Session''' to end the broadcast
[[File:Lara Speaker Graphic 1.png|none|thumb|360x360px]]

===== '''Important''': =====
The Speaker does not select any language or configure settings. Simply click '''Start Recording''' and speak.

If your unit has more than one language spoken (for example, if testimonies are given in multiple languages), see the instructions below for using “Multiple Spoken Languages”''.''

=== '''<big>Listener (Guest)</big>''' ===

=== '''Steps''' ===

# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Scan the QR code or click on the Listener link provided for interpretation
# The Listener page opens with the session name
# Select your desired Target Language
# Click '''Connect'''
# Click the speaker icon to start listening to the real-time translation
## (6a)If the listener does not have headphones, they may choose to only read the captions.
[[File:Lara Listener Graphic.png|none|thumb|481x481px]]

=== '''Feedback Surveys Instructions''' ===
At the end of the meeting, please submit your feedback and request everyone who listened to the interpretation also submit their feedback. This is an important part of the pilot.

* Speaker (Host):  [link]

* Listener (Guest):  [link]

=== <big>'''APPENDIX'''</big> ===

==== <big>'''Key Reminders and Expectations'''</big> ====

==== '''Speaker (Host)''': ====
* The Speaker (Host) must click '''Start Recording''' for the listeners to hear anything

* Speaker and Listener links remain the same each week unless new links are requested. To request new links, contact your headquarters

* Do not share the “Speaker” link (only those managing the session should us it)

* Clear audio is critical for accurate translation (see Audio Recommendations below)

==== '''Listener (Guest):''' ====
* Use a personal device and headphones (recommended)

* Listeners may join even after the Speaker has already started

* Each listener can select a different language

* Expect a short delay between speech and translation

* Faster speech or fewer pauses may increase the delay

==== '''General:''' ====
* Everything runs in a web browser (no app required)

=== '''<big>Audio Recommendations</big>''' ===
Clear audio is the most important factor for accurate interpretation

=== '''Speaker (Host)''' ===

* Use any device with a web browser and internet connection

* Select the audio input using the Settings button near the bottom of the page:

[[File:Start Recording Graphic.png|none|thumb|468x468px]]

=== '''Recommended audio setup (best to least preferred)''' ===

===== '''1. Line-level audio from the chapel sound system (best)''' =====
<blockquote>Provides the clearest and most consistent audio [[File:Chapel image 1.png|none|thumb|429x429px]]''Example only; computer could be in a different location and may connect into the chapel's audio system differently.''</blockquote>

===== '''2. External Microphone''' =====
<blockquote>Use a dedicated external microphone connected to the Speaker device (Host) (Bluetooth microphone for example)[[File:Pulpit Image 2.png|none|thumb|422x422px]]</blockquote>

===== '''3. Built-in device microphone (least preferred)''' =====
<blockquote>Place the device (laptop or tablet) as close as possible to the speaker[[File:Pulpit image 3.png|none|thumb|275x275px]]</blockquote>If you need help connecting to the chapel audio system, contact your '''Facilities Manager.'''

=== '''Multiple Spoken Languages''' ===
If more than one language will be spoken during the meeting, you have two options:

==== '''Option 1: Autodetect Language Link''' ====

* Requires a separate Speaker link

* Uses a different Listener link than the primary session

* Automatically detects the language being spoken

'''Note:''' Interpretation quality may be lower when using autodetect.

Contact your pilot coordinator if you would like to use this option

==== '''Option 2: Separate Links for Each Language''' ====

* Request a separate Speaker link for each language

* Each Speaker link has a corresponding Listener link

This option may provide more consistent interpretation quality

=== '''Support and Troubleshooting''' ===

* If someone cannot connect to the “Liahona” Wi-Fi network:

** Check that the password that they entered for “Liahona” is correct.
** Confirm that their device is trying to connect to "Liahona" and not another Wi-Fi network.
** If others are also unable to connect to “Liahona” additional troubleshooting may be needed [[Troubleshooting Wireless Access Points]]

* During the pilot, if you have a question or issue that you cannot resolve:

** Contact the Facilities Manager or submit a ticket in the Church’s Facilities Incident Reporting (FIR) mobile app, if:

*** It is related to the meetinghouse internet/WI-FI-network
*** You need assistance connecting to the chapel’s audio system.
*** There is a problem with the chapel’s audio system.

* Email the Area or Church Headquarters contact who provided you with the other pilot information, if:

** It is related to the Lara by Translated website.
** You have questions about the pilot.
''Images shown above were AI generated.''

{{DEFAULTSORT:Translated WIKI AI Live Interpretation Page 2026 }}

AI Live Interpretation in Sacrament Meetings Pilot

2026-05-06T15:31:08Z

Ericjamee: Formatting

{{DISPLAYTITLE:Translated WIKI AI Live Interpretation Page 2026 }}

== '''<big>Overview</big>''' ==
This article explains how to set up and use the AI Live Interpretation tool for sacrament meetings as part of an approved pilot. This AI tool allows members to hear real-time translation on their personal devices during meetings

''Note: If your unit has not been invited to participate in the pilot, this article will not be applicable.''

=== '''<big>How to Use the Lara Simultaneous Interpreter</big>''' ===
The system uses two roles:

* '''Speaker''': the host of the session (the person speaking)
* '''Listener''': the guest (the person listening to the translation)

The connection between the two happens through:

* A Speaker link
* A Listener QR code (to receive the translation)

No installation is required. Everything runs in the browser.

=== '''<big>Speaker (Host)</big>''' ===

=== '''Preparation''' ===
A. Decide how you will share the Listener link (or QR code) and feedback form to the “Listeners”

B. Test the '''Meeting Steps''' shown below before the sacrament meeting

=== '''Meeting Steps''' ===

# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Open the Speaker link you received
# Confirm the session shows “'''Ready to broadcast'''”
# When the meeting begins, click '''Start Recording'''
# Use the '''Start''' and '''Stop Recording''' as needed to control what is translated
# When finished, click '''Close Session''' to end the broadcast
[[File:Lara Speaker Graphic 1.png|none|thumb|360x360px]]

===== '''Important''': =====
The Speaker does not select any language or configure settings. Simply click '''Start Recording''' and speak.

If your unit has more than one language spoken (for example, if testimonies are given in multiple languages), see the instructions below for using “Multiple Spoken Languages”''.''

=== '''<big>Listener (Guest)</big>''' ===

=== '''Steps''' ===

# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Scan the QR code or click on the Listener link provided for interpretation
# The Listener page opens with the session name
# Select your desired Target Language
# Click '''Connect'''
# Click the speaker icon to start listening to the real-time translation
## (6a)If the listener does not have headphones, they may choose to only read the captions.
[[File:Lara Listener Graphic.png|none|thumb|481x481px]]

=== '''Feedback Surveys Instructions''' ===
At the end of the meeting, please submit your feedback and request everyone who listened to the interpretation also submit their feedback. This is an important part of the pilot.

* Speaker (Host):  [link]

* Listener (Guest):  [link]

=== '''<big>APPENDIX</big>''' ===

==== <big>Key Reminders and Expectations</big> ====

==== '''Speaker (Host)''': ====
* The Speaker (Host) must click '''Start Recording''' for the listeners to hear anything

* Speaker and Listener links remain the same each week unless new links are requested. To request new links, contact your headquarters

* Do not share the “Speaker” link (only those managing the session should us it)

* Clear audio is critical for accurate translation (see Audio Recommendations below)

==== '''Listener (Guest):''' ====
* Use a personal device and headphones (recommended)

* Listeners may join even after the Speaker has already started

* Each listener can select a different language

* Expect a short delay between speech and translation

* Faster speech or fewer pauses may increase the delay

==== '''General:''' ====
* Everything runs in a web browser (no app required)

=== '''<big>Audio Recommendations</big>''' ===
Clear audio is the most important factor for accurate interpretation

=== '''Speaker (Host)''' ===

* Use any device with a web browser and internet connection

* Select the audio input using the Settings button near the bottom of the page:

[[File:Start Recording Graphic.png|none|thumb|468x468px]]

=== '''Recommended audio setup (best to least preferred)''' ===

===== '''1. Line-level audio from the chapel sound system (best)''' =====
<blockquote>Provides the clearest and most consistent audio [[File:Chapel image 1.png|none|thumb|429x429px]]''Example only; computer could be in a different location and may connect into the chapel's audio system differently.''</blockquote>

===== '''2. External Microphone''' =====
<blockquote>Use a dedicated external microphone connected to the Speaker device (Host) (Bluetooth microphone for example)[[File:Pulpit Image 2.png|none|thumb|422x422px]]</blockquote>

===== '''3. Built-in device microphone (least preferred)''' =====
<blockquote>Place the device (laptop or tablet) as close as possible to the speaker[[File:Pulpit image 3.png|none|thumb|275x275px]]</blockquote>If you need help connecting to the chapel audio system, contact your '''Facilities Manager.'''

=== '''Multiple Spoken Languages''' ===
If more than one language will be spoken during the meeting, you have two options:

==== '''Option 1: Autodetect Language Link''' ====

* Requires a separate Speaker link

* Uses a different Listener link than the primary session

* Automatically detects the language being spoken

'''Note:''' Interpretation quality may be lower when using autodetect.

Contact your pilot coordinator if you would like to use this option

==== '''Option 2: Separate Links for Each Language''' ====

* Request a separate Speaker link for each language

* Each Speaker link has a corresponding Listener link

This option may provide more consistent interpretation quality

=== '''Support and Troubleshooting''' ===

* If someone cannot connect to the “Liahona” Wi-Fi network:

** Check that the password that they entered for “Liahona” is correct.
** Confirm that their device is trying to connect to "Liahona" and not another Wi-Fi network.
** If others are also unable to connect to “Liahona” additional troubleshooting may be needed [[Troubleshooting Wireless Access Points]]

* During the pilot, if you have a question or issue that you cannot resolve:

** Contact the Facilities Manager or submit a ticket in the Church’s Facilities Incident Reporting (FIR) mobile app, if:

*** It is related to the meetinghouse internet/WI-FI-network
*** You need assistance connecting to the chapel’s audio system.
*** There is a problem with the chapel’s audio system.

* Email the Area or Church Headquarters contact who provided you with the other pilot information, if:

** It is related to the Lara by Translated website.
** You have questions about the pilot.
''Images shown above were AI generated.''

{{DEFAULTSORT:Translated WIKI AI Live Interpretation Page 2026 }}

AI Live Interpretation in Sacrament Meetings Pilot

2026-05-05T22:58:43Z

Ericjamee: Internal link change

{{DISPLAYTITLE:Translated WIKI AI Live Interpretation Page 2026 }}

== '''<big>Overview</big>''' ==
This article explains how to set up and use the AI Live Interpretation tool for sacrament meetings as part of an approved pilot. This AI tool allows members to hear real-time translation on their personal devices during meetings

''Note: If your unit has not been invited to participate in the pilot, this article will not be applicable.''

=== '''<big>How to Use the Lara Simultaneous Interpreter</big>''' ===
The system uses two roles:

* '''Speaker''': the host of the session (the person speaking)
* '''Listener''': the guest (the person listening to the translation)

The connection between the two happens through:

* A Speaker link

# A Listener QR code (to receive the translation)

No installation is required. Everything runs in the browser.

=== '''<big>Speaker (Host)</big>''' ===

=== '''Preparation''' ===

# Decide how you will share the Listener link (or QR code) and feedback form to the “Listeners”

# Test the '''Meeting Steps''' shown below before the sacrament meeting

=== '''Meeting Steps''' ===

# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Open the Speaker link you received
# Confirm the session shows “'''Ready to broadcast'''”
# When the meeting begins, click '''Start Recording'''
# Use the '''Start''' and '''Stop Recording''' as needed to control what is translated
# When finished, click '''Close Session''' to end the broadcast

[[File:Lara Speaker Graphic 1.png|none|thumb|360x360px]]

===== '''Important''': =====
The Speaker does not select any language or configure settings. Simply click '''Start Recording''' and speak.

If your unit has more than one language spoken (for example, if testimonies are given in multiple languages), see the instructions below for using “Multiple Spoken Languages”''.''

=== '''<big>Listener (Guest)</big>''' ===

=== '''Steps''' ===

# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Scan the QR code or click on the Listener link provided for interpretation
# The Listener page opens with the session name
# Select your desired Target Language
# Click '''Connect'''
# Click the speaker icon to start listening to the real-time translation
## (6a)If the listener does not have headphones, they may choose to only read the captions.

[[File:Lara Listener Graphic.png|none|thumb|481x481px]]

=== '''Feedback Surveys Instructions''' ===
At the end of the meeting, please submit your feedback and request everyone who listened to the interpretation also submit their feedback. This is an important part of the pilot.

* Speaker (Host):  [link]

* Listener (Guest):  [link]

== '''<big>APPENDIX</big>''' ==

=== '''<big>Key Reminders and Expectations</big>''' ===

=== '''Speaker (Host)''': ===

* The Speaker (Host) must click '''Start Recording''' for the listeners to hear anything

* Speaker and Listener links remain the same each week unless new links are requested. To request new links, contact your headquarters

* Do not share the “Speaker” link (only those managing the session should us it)

* Clear audio is critical for accurate translation (see Audio Recommendations below)

=== '''Listener (Guest):''' ===

* Use a personal device and headphones (recommended)

* Listeners may join even after the Speaker has already started

* Each listener can select a different language

* Expect a short delay between speech and translation

* Faster speech or fewer pauses may increase the delay

=== '''General:''' ===

* Everything runs in a web browser (no app required)

=== '''<big>Audio Recommendations</big>''' ===
Clear audio is the most important factor for accurate interpretation

=== '''Speaker (Host)''' ===

* Use any device with a web browser and internet connection

* Select the audio input using the Settings button near the bottom of the page:

[[File:Start Recording Graphic.png|none|thumb|468x468px]]

=== '''Recommended audio setup (best to least preferred)''' ===

===== '''Line-level audio from the chapel sound system (best)''' =====
<blockquote>Provides the clearest and most consistent audio [[File:Chapel image 1.png|none|thumb|429x429px]]''Example only; computer could be in a different location and may connect into the chapel's audio system differently.''</blockquote>

===== '''External Microphone''' =====
<blockquote>Use a dedicated external microphone connected to the Speaker device (Host) (Bluetooth microphone for example)[[File:Pulpit Image 2.png|none|thumb|422x422px]]</blockquote>

===== '''Built-in device microphone (least preferred)''' =====
<blockquote>Place the device (laptop or tablet) as close as possible to the speaker[[File:Pulpit image 3.png|none|thumb|275x275px]]</blockquote>If you need help connecting to the chapel audio system, contact your '''Facilities Manager.'''

=== '''Multiple Spoken Languages''' ===
If more than one language will be spoken during the meeting, you have two options:

==== '''Option 1: Autodetect Language Link''' ====

* Requires a separate Speaker link

* Uses a different Listener link than the primary session

* Automatically detects the language being spoken

'''Note:''' Interpretation quality may be lower when using autodetect.

Contact your pilot coordinator if you would like to use this option

==== '''Option 2: Separate Links for Each Language''' ====

* Request a separate Speaker link for each language

* Each Speaker link has a corresponding Listener link

This option may provide more consistent interpretation quality

=== '''Support and Troubleshooting''' ===

* If someone cannot connect to the “Liahona” Wi-Fi network:

* Check that the password that they entered for “Liahona” is correct.

* Confirm that their device is trying to connect to "Liahona" and not another Wi-Fi network.

* If others are also unable to connect to “Liahona” additional troubleshooting may be needed [[Troubleshooting Wireless Access Points]]

* During the pilot, if you have a question or issue that you cannot resolve:

* Contact the Facilities Manager or submit a ticket in the Church’s Facilities Incident Reporting (FIR) mobile app, if:

* It is related to the meetinghouse internet/WI-FI-network

* You need assistance connecting to the chapel’s audio system.

* There is a problem with the chapel’s audio system.

* Email the Area or Church Headquarters contact who provided you with the other pilot information, if:

* It is related to the Lara by Translated website.

* You have questions about the pilot.

''Images shown above were AI generated.''

{{DEFAULTSORT:Translated WIKI AI Live Interpretation Page 2026 }}

AI Live Interpretation in Sacrament Meetings Pilot

2026-05-05T22:57:41Z

Ericjamee: Title of Article

{{DISPLAYTITLE:Translated WIKI AI Live Interpretation Page 2026 }}

== '''<big>Overview</big>''' ==
This article explains how to set up and use the AI Live Interpretation tool for sacrament meetings as part of an approved pilot. This AI tool allows members to hear real-time translation on their personal devices during meetings

''Note: If your unit has not been invited to participate in the pilot, this article will not be applicable.''

=== '''<big>How to Use the Lara Simultaneous Interpreter</big>''' ===
The system uses two roles:

* '''Speaker''': the host of the session (the person speaking)
* '''Listener''': the guest (the person listening to the translation)

The connection between the two happens through:

* A Speaker link

# A Listener QR code (to receive the translation)

No installation is required. Everything runs in the browser.

=== '''<big>Speaker (Host)</big>''' ===

=== '''Preparation''' ===

# Decide how you will share the Listener link (or QR code) and feedback form to the “Listeners”

# Test the '''Meeting Steps''' shown below before the sacrament meeting

=== '''Meeting Steps''' ===

# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Open the Speaker link you received
# Confirm the session shows “'''Ready to broadcast'''”
# When the meeting begins, click '''Start Recording'''
# Use the '''Start''' and '''Stop Recording''' as needed to control what is translated
# When finished, click '''Close Session''' to end the broadcast

[[File:Lara Speaker Graphic 1.png|none|thumb|360x360px]]

===== '''Important''': =====
The Speaker does not select any language or configure settings. Simply click '''Start Recording''' and speak.

If your unit has more than one language spoken (for example, if testimonies are given in multiple languages), see the instructions below for using “Multiple Spoken Languages”''.''

=== '''<big>Listener (Guest)</big>''' ===

=== '''Steps''' ===

# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Scan the QR code or click on the Listener link provided for interpretation
# The Listener page opens with the session name
# Select your desired Target Language
# Click '''Connect'''
# Click the speaker icon to start listening to the real-time translation
## (6a)If the listener does not have headphones, they may choose to only read the captions.

[[File:Lara Listener Graphic.png|none|thumb|481x481px]]

=== '''Feedback Surveys Instructions''' ===
At the end of the meeting, please submit your feedback and request everyone who listened to the interpretation also submit their feedback. This is an important part of the pilot.

* Speaker (Host):  [link]

* Listener (Guest):  [link]

== '''<big>APPENDIX</big>''' ==

=== '''<big>Key Reminders and Expectations</big>''' ===

=== '''Speaker (Host)''': ===

* The Speaker (Host) must click '''Start Recording''' for the listeners to hear anything

* Speaker and Listener links remain the same each week unless new links are requested. To request new links, contact your headquarters

* Do not share the “Speaker” link (only those managing the session should us it)

* Clear audio is critical for accurate translation (see Audio Recommendations below)

=== '''Listener (Guest):''' ===

* Use a personal device and headphones (recommended)

* Listeners may join even after the Speaker has already started

* Each listener can select a different language

* Expect a short delay between speech and translation

* Faster speech or fewer pauses may increase the delay

=== '''General:''' ===

* Everything runs in a web browser (no app required)

=== '''<big>Audio Recommendations</big>''' ===
Clear audio is the most important factor for accurate interpretation

=== '''Speaker (Host)''' ===

* Use any device with a web browser and internet connection

* Select the audio input using the Settings button near the bottom of the page:

[[File:Start Recording Graphic.png|none|thumb|468x468px]]

=== '''Recommended audio setup (best to least preferred)''' ===

===== '''Line-level audio from the chapel sound system (best)''' =====
<blockquote>Provides the clearest and most consistent audio [[File:Chapel image 1.png|none|thumb|429x429px]]''Example only; computer could be in a different location and may connect into the chapel's audio system differently.''</blockquote>

===== '''External Microphone''' =====
<blockquote>Use a dedicated external microphone connected to the Speaker device (Host) (Bluetooth microphone for example)[[File:Pulpit Image 2.png|none|thumb|422x422px]]</blockquote>

===== '''Built-in device microphone (least preferred)''' =====
<blockquote>Place the device (laptop or tablet) as close as possible to the speaker[[File:Pulpit image 3.png|none|thumb|275x275px]]</blockquote>If you need help connecting to the chapel audio system, contact your '''Facilities Manager.'''

=== '''Multiple Spoken Languages''' ===
If more than one language will be spoken during the meeting, you have two options:

==== '''Option 1: Autodetect Language Link''' ====

* Requires a separate Speaker link

* Uses a different Listener link than the primary session

* Automatically detects the language being spoken

'''Note:''' Interpretation quality may be lower when using autodetect.

Contact your pilot coordinator if you would like to use this option

==== '''Option 2: Separate Links for Each Language''' ====

* Request a separate Speaker link for each language

* Each Speaker link has a corresponding Listener link

This option may provide more consistent interpretation quality

=== '''Support and Troubleshooting''' ===

* If someone cannot connect to the “Liahona” Wi-Fi network:

* Check that the password that they entered for “Liahona” is correct.

* Confirm that their device is trying to connect to "Liahona" and not another Wi-Fi network.

* If others are also unable to connect to “Liahona” additional troubleshooting may be needed - [[Troubleshooting Wireless Access Points|Troubleshooting Wireless Access Points - TechWiki]].

* During the pilot, if you have a question or issue that you cannot resolve:

* Contact the Facilities Manager or submit a ticket in the Church’s Facilities Incident Reporting (FIR) mobile app, if:

* It is related to the meetinghouse internet/WI-FI-network

* You need assistance connecting to the chapel’s audio system.

* There is a problem with the chapel’s audio system.

* Email the Area or Church Headquarters contact who provided you with the other pilot information, if:

* It is related to the Lara by Translated website.

* You have questions about the pilot.

''Images shown above were AI generated.''

{{DEFAULTSORT:Translated WIKI AI Live Interpretation Page 2026 }}

AI Live Interpretation in Sacrament Meetings Pilot

2026-05-05T22:25:41Z

Ericjamee: Created page with " = Translated WIKI AI Live Interpretation Page 2026 = === '''<big>Overview</big>''' === This article explains how to set up and use the AI Live Interpretation tool for sacrament meetings as part of an approved pilot. This AI tool allows members to hear real-time translation on their personal devices during meetings ''Note: If your unit has not been invited to participate in the pilot, this article will not be applicable.'' === '''<big>How to Use the Lara Simultane..."

= Translated WIKI AI Live Interpretation Page 2026 =

=== '''<big>Overview</big>''' ===
This article explains how to set up and use the AI Live Interpretation tool for sacrament meetings as part of an approved pilot. This AI tool allows members to hear real-time translation on their personal devices during meetings

''Note: If your unit has not been invited to participate in the pilot, this article will not be applicable.''

=== '''<big>How to Use the Lara Simultaneous Interpreter</big>''' ===
The system uses two roles:

* '''Speaker''': the host of the session (the person speaking)
* '''Listener''': the guest (the person listening to the translation)

The connection between the two happens through:

* A Speaker link

# A Listener QR code (to receive the translation)

No installation is required. Everything runs in the browser.

=== '''<big>Speaker (Host)</big>''' ===

=== '''Preparation''' ===

# Decide how you will share the Listener link (or QR code) and feedback form to the “Listeners”

# Test the '''Meeting Steps''' shown below before the sacrament meeting

=== '''Meeting Steps''' ===

# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Open the Speaker link you received
# Confirm the session shows “'''Ready to broadcast'''”
# When the meeting begins, click '''Start Recording'''
# Use the '''Start''' and '''Stop Recording''' as needed to control what is translated
# When finished, click '''Close Session''' to end the broadcast

[[File:Lara Speaker Graphic 1.png|none|thumb|360x360px]]

===== '''Important''': =====
The Speaker does not select any language or configure settings. Simply click '''Start Recording''' and speak.

If your unit has more than one language spoken (for example, if testimonies are given in multiple languages), see the instructions below for using “Multiple Spoken Languages”''.''

=== '''<big>Listener (Guest)</big>''' ===

=== '''Steps''' ===

# Connect to the meetinghouse “'''Liahona'''” Wi-Fi network
# Scan the QR code or click on the Listener link provided for interpretation
# The Listener page opens with the session name
# Select your desired Target Language
# Click '''Connect'''
# Click the speaker icon to start listening to the real-time translation
## (6a)If the listener does not have headphones, they may choose to only read the captions.

[[File:Lara Listener Graphic.png|none|thumb|481x481px]]

=== '''Feedback Surveys Instructions''' ===
At the end of the meeting, please submit your feedback and request everyone who listened to the interpretation also submit their feedback. This is an important part of the pilot.

* Speaker (Host):  [link]

* Listener (Guest):  [link]

== '''<big>APPENDIX</big>''' ==

=== '''<big>Key Reminders and Expectations</big>''' ===

=== '''Speaker (Host)''': ===

* The Speaker (Host) must click '''Start Recording''' for the listeners to hear anything

* Speaker and Listener links remain the same each week unless new links are requested. To request new links, contact your headquarters

* Do not share the “Speaker” link (only those managing the session should us it)

* Clear audio is critical for accurate translation (see Audio Recommendations below)

=== '''Listener (Guest):''' ===

* Use a personal device and headphones (recommended)

* Listeners may join even after the Speaker has already started

* Each listener can select a different language

* Expect a short delay between speech and translation

* Faster speech or fewer pauses may increase the delay

=== '''General:''' ===

* Everything runs in a web browser (no app required)

=== '''<big>Audio Recommendations</big>''' ===
Clear audio is the most important factor for accurate interpretation

=== '''Speaker (Host)''' ===

* Use any device with a web browser and internet connection

* Select the audio input using the Settings button near the bottom of the page:

[[File:Start Recording Graphic.png|none|thumb|468x468px]]

=== '''Recommended audio setup (best to least preferred)''' ===

===== '''Line-level audio from the chapel sound system (best)''' =====
<blockquote>Provides the clearest and most consistent audio [[File:Chapel image 1.png|none|thumb|429x429px]]''Example only; computer could be in a different location and may connect into the chapel's audio system differently.''</blockquote>

===== '''External Microphone''' =====
<blockquote>Use a dedicated external microphone connected to the Speaker device (Host) (Bluetooth microphone for example)[[File:Pulpit Image 2.png|none|thumb|422x422px]]</blockquote>

===== '''Built-in device microphone (least preferred)''' =====
<blockquote>Place the device (laptop or tablet) as close as possible to the speaker[[File:Pulpit image 3.png|none|thumb|275x275px]]</blockquote>If you need help connecting to the chapel audio system, contact your '''Facilities Manager.'''

=== '''Multiple Spoken Languages''' ===
If more than one language will be spoken during the meeting, you have two options:

==== '''Option 1: Autodetect Language Link''' ====

* Requires a separate Speaker link

* Uses a different Listener link than the primary session

* Automatically detects the language being spoken

'''Note:''' Interpretation quality may be lower when using autodetect.

Contact your pilot coordinator if you would like to use this option

==== '''Option 2: Separate Links for Each Language''' ====

* Request a separate Speaker link for each language

* Each Speaker link has a corresponding Listener link

This option may provide more consistent interpretation quality

=== '''Support and Troubleshooting''' ===

* If someone cannot connect to the “Liahona” Wi-Fi network:

* Check that the password that they entered for “Liahona” is correct.

* Confirm that their device is trying to connect to "Liahona" and not another Wi-Fi network.

* If others are also unable to connect to “Liahona” additional troubleshooting may be needed - [[Troubleshooting Wireless Access Points|Troubleshooting Wireless Access Points - TechWiki]].

* During the pilot, if you have a question or issue that you cannot resolve:

* Contact the Facilities Manager or submit a ticket in the Church’s Facilities Incident Reporting (FIR) mobile app, if:

* It is related to the meetinghouse internet/WI-FI-network

* You need assistance connecting to the chapel’s audio system.

* There is a problem with the chapel’s audio system.

* Email the Area or Church Headquarters contact who provided you with the other pilot information, if:

* It is related to the Lara by Translated website.

* You have questions about the pilot.

''Images shown above were AI generated.''

File:Pulpit image 3.png

2026-05-05T20:29:00Z

Ericjamee:

pulpit

File:Pulpit Image 2.png

2026-05-05T20:28:13Z

Ericjamee:

pulpit image 2

File:Chapel image 1.png

2026-05-05T20:25:20Z

Ericjamee:

chapel image 1

File:Start Recording Graphic.png

2026-05-05T20:10:25Z

Ericjamee:

Start Recording Graphic

File:Lara Listener Graphic.png

2026-05-05T20:06:40Z

Ericjamee:

Lara Listener Graphic

File:Lara Listener Graphic 1.png

2026-05-05T20:04:19Z

Ericjamee:

Lara Listener Graphic 1

File:Lara Speaker Graphic 1.png

2026-05-05T20:00:37Z

Ericjamee:

Lara Speaker Graphic 1