Home› Welcome to the FamilySearch Community!› FamilySearch Help› Temple

Temple work for an individual without any family members alive

K Stansel
K Stansel ✭
August 30, 2021 edited August 30, 2021 in Temple

My husband and I desire to complete the work for this individual:

Nicholas Mark McBrearty

KWDX-F23

This gentleman was a member of our ward, and we knew him for about 20 years. My husband was his bishop when he passed away. Brother Mac was an orphan and grew up in an orphanage. Then he joined the Navy, and the Navy became his family. He never married and had no children. After he joined the church, he researched his parents, who had both passed way, and did their temple work. He did not find any siblings. He sealed his parents to each other, but somehow he did not seal himself to them. This is a service that we would like to provide to this wonderful man. He has no living family, and we would very much like to seal him to his parents. May we have permission to perform this work?

Kim & David Stansel

IMG_3540.jpg
IMG_3541.jpg


0

Answers

  • Sanra
    Sanra ✭✭✭✭
    August 30, 2021

    @ K Stansel

    Thank you for your question to the Community about doing the ordinances for Nicholas Mark McBrearty .

    If your deceased friend has no close living relatives that can provide written permission, then a request cannot be granted.  This statement was taken from the article listed below.

    https://www.familysearch.org/help/helpcenter/article/can-i-request-proxy-temple-ordinances-for-a-friend

    We are sorry we cannot help you with this issue. Hopefully one of his extended family members may do the ordinance for him.

    0
Clear
No Groups Found

Categories

  • 24.8K All Categories
  • 593 1950 US Census
  • 47.6K FamilySearch Help
  • 100 Get Involved
  • 2.4K General Questions
  • 366 Family History Centers
  • 365 FamilySearch Account
  • 3.5K Family Tree
  • 2.7K Search
  • 3.8K Indexing
  • 474 Memories
  • 4.9K Temple
  • 270 Other Languages
  • 30 Community News
  • 5.6K Suggest an Idea
  • Groups