IF, you are referring to IMPORTING a GEDCOM File in "Family Tree" of 'FamilySearch'; THEN, ...
You can; but ...
Please DO NOT upload a GEDCOM File in "Family Tree" of "FamilySearch".
Upload GEDCOM File in the "Genealogies" Part of "FamilySearch", that is fine; but, please NOT into "Family Tree" of "FamilySearch".
Some of the reasons that Users/Patrons (like myself) DO NOT want the ability to upload a GEDCOM File into "Family Tree" of "FamilySearch" are:
(1) It is most likely that individuals/persons in a GEDCOM File are ALREADY in "Family Tree" of "FamilySearch"; and, most Users/Patrons DO NOT even take the time to look to see if any one in their GEDCOM File is already in "Family Tree", in some instances, negating the need to even upload the GEDCOM File.
(2) There has been (many) cases where Users/Patrons, using the "Compare" process (of the upload) have "Dismissed" a "Possible" Match with an individual/person already in "Family Tree"; so that, their "Record", from their GEDCOM File, is loaded into "Family Tree", regardless; just so that, their "Record" appears in "Family Tree" (and, in some instances, for Members of the Church, so they can do the "Temple" Work, despite the fact that the "Temple" Work is ALREADY done with the "Possible" Match with the individual/person already in "Family Tree").
(3) Even with the "Compare" process (of the upload), there has been (many) cases where Users/Patrons have uploaded THEIR version of an individual/person in their GEDCOM File, on top of (ie. Over) an individual/person ALREADY in "Family Tree" of "FamilySearch" that has been there for MANY years and is well documented and "Sources" - in many instances obliterating all of the documentation and "Sources".
(4) If an individual/person is ALREADY in "Family Tree" of "FamilySearch", there is NO need to up uploaded one's version of an individual/person from one's own GEDCOM File - just take note of the the 'FamilySearch Person Idenmtifier' (PID) of the individual/person that is ALREADY in "Family Tree"; and, one can go back later to ensure what information/detail is recorded and attached for that individual/person. Just DO NOT uploaded one's version of an individual/person in their GEDCOM File, on top of (ie. Over) an individual/person ALREADY in "Family Tree" - obliterating all of the documentation and "Sources" ALREADY in place/on record.
(5) The "Hours" (sometimes "Days") of work, by other Users/Patrons, that can be needed to CORRECT the DAMAGE done by the upload of a GEDCOM File can be disheartening.
I am sorry ... 'off my soap box' ...
Enter (ie. 'Create) the individuals/persons in "Family Tree" of "FamilySearch" one at a time - on a one by one basis.
Many of the individuals/persons most probably ALREADY exist in "Family Tree" of "FamilySearch".
Only one or two generations of the "Living" individuals/persons may be required to be entered/input in "Family Tree" of "FamilySearch"; before, some of the "Deceased" individuals/persons from Ancestral lines ALREADY existing in "Family Tree" of "FamilySearch", are discovered.
Use the "Find" facility/function/feature to Search "Family Tree" of "FamilySearch", you may be surprised to find some (if not, many) of them already there.
Many well established and documented (eg. "Sourced") individuals/person in "Family Tree" of "FamilySearch" have been RUINED by the upload a GEDCOM File into "Family Tree" of "FamilySearch".
I hope this puts things into perspective.
OK I did that, now how do I see that tree in Genealogies and use that to update my tree under family search
IF, you ONLY "Uploaded" you GEDCOM File into the "Genealogies" Part of 'FamilySearch'; THEN, that 'standalone' "Pedigree" (ie. 'Tree') can be found here:
Submit your Tree ...
My Uploaded Trees
[ towards the 'Bottom' of the page/screen ]
As an aside ...
Those 'standalone' "Pedigrees" (ie. 'Trees') CANNOT be Changed/Edited, they are "As Is" (ie. as loaded).
The ONLY option is to "Delete"/"Remove" them; and, upload an "Up-Dated" version.
I hope this helps.
Once you've imported the GEDCOM file under the "Search->Genealogies->Submit your Tree" function, that file will show up in your "My Uploaded Trees" list:
In the first column of the GEDCOM File controls area, you will get an "In Progress" indicator while the file is uploading and being converted into a searchable format in the genealogies data base.
When it is complete, that "In Progress" indicator will turn into a "Compare" button. When you click on that button, the GEDCOM Compare tool will walk through your GEDCOM file records, and for each one it will search the FamilySearch FamilyTree for records that match it. The results will be stored with the GEDCOM file. The "Compare" button will turn into a "View" button.
(Note that once you have uploaded a GEDCOM file, you can only perform this compare function ONCE. If you come back a year later and want to perform another compare to pick up any new changes in the FamilySearch FamilyTree, you will have to upload the file again in order to initiate another compare on it. If you don't have a copy, you can download the GEDCOM file from your "My Uploaded Trees" list and then upload it again in order to initiate a new compare)
Once the compare is completed, you can view the results by clicking on the new "View" button:
This will give you access to each of the records that were in your GEDCOM File with the results of the Compare function. As you can see the compare function groups the GEDCOM records into 4 groups based on the comparison that was performed earlier. the "Already in Family Tree" group are records that the Compare tool is fairly certain about (this is mainly from their position in trees and associated relationships). You can walk through the group and look at each record and compare it with the match in the FSFT. If there is a vital or relationship in the FSFT that is different you can replace it with the value in your GEDCOM file by hitting the "Replace" button on it. The replacement is not performed until you hit the "Save button".
The "Already in Family Tree" group is occasionally wrong though and performing any replacements will blow away potentially correct data in the wrong record.
The "Add to Family Tree" group are items that the Compare tool thinks don't exist there. The tool also makes mistakes on this and misses matches. If you add that record to the FSFT, it will be a duplicate that someone will have to clean up (duplicates in the tree can really foul things up and create a mess of work for others)
The "Potential Matches" group is where the Compare tool thinks there MIGHT be a match but it isn't sure so you can go through and put them into the "Already in the Family Tree" or the "Add to Family Tree" groups. The tool is severely lacking here as well. Other than some vitals, all of the necessary information to make an intelligent decision here is totally missing and inaccessible. You can't see either the tree structure in your GEDCOM records or the tree structure in the FSFT.
This blindness that the Compare tool forces upon you can screw up a lot of things. For example, if you go to replace a vital value in the FSFT with one from your GEDCOM, in addition to not being able to see the notes for that record that are actually in the GEDCOM file, you cannot see any of the Reason statements, Notes, Sources, discussions, or change history for that vital in the FSFT. There is frequently years of evidence that has been provided by many different persons proving that the value already in the FSFT is completely correct. But since the tool PREVENTS you from seeing any of it, frequently the vitals in the FSFT are blown away by people assuming that their GEDCOM file is more correct for some reason.
Furthermore, when you make the change in the FSFT, although the Compare Tool prompts you to provide a reason for the change, it never records it in the change reason, recent changes lists, and change history logs in the FSFT. As a result, your change in the FSFT has NO justification documented making it look like a "drive-by alteration" (which makes a LOT of people angry).
The GEDCOM Compare tool can be moderately useful, but it creates a tremendous amount of grief for others who's well documented conclusions are being blown away for no visibly justifiable reason. This tool is severely lacking in many critical ways. If you are going to use it, you need to open another window so that you can view all aspects of the record in the FSFT at the same time. Unfortunately, although notes and such do actually exist in the GEDCOM file, you cannot easily bring up any kind of window that will show them so that you can compare with your other window.
Anyway, this is just a smattering of the problems that you can cause using this tool. It used to be much WORST up to a few months ago when it was upgraded using the new merge function type screens (the merge functions have some issue too, but not quite as severe). So be very careful and make sure that you've read all the supporting information for any given vitals before replacing them via the Compare tool. The Compare Tool does NOT provide any way for you to see any of that critical information so you need to find work-arounds to it.
@FamilySearch Family Tree