If another user uploads a Flare project to your MadCap Central license and you do not yet have that project on your computer, you can import it.
In order to import a project, you must be associated with that project in Central. For more information, see the Central online Help.
For this activity, you must have the following permission setting
For more information about permissions, see the Central online Help.
- Open MadCap Flare.
- Select View > MadCap Central. The MadCap Central window pane opens.
- If you are not yet logged in, enter the same username (i.e., email) and password that you use for logging into Central, and click Log In.
Tip: If this button is disabled, try clicking in the window pane first.
The Import Project dialog opens.
- If you are a member of more than one MadCap Central license, click in the My Licenses field and choose the license where the project is located.
- From the My Projects field, select the project you want to import.
- Next to the Destination folder field, click and choose the folder where you want the imported project to be stored on your computer.
- Click OK.
- When the import is finished, you can click Open to launch the project in Flare. Otherwise, you can click Cancel.
Important: If you are using a Git/Central dual-binding
Note: If your project is already bound to a third-party source control provider other than Git (i.e., you are working in a dual-bound model as opposed to a single-bound model
If you already have the project on your machine, you do not need to re-import the project from source control. Instead, you can get the latest version from source control by using the Flare Source Control ribbon.
Be sure that you have the latest version of the project because when the project is initially uploaded to Central, a Central ID is added to the project file. You must have the Central ID in your local copy of the project file in order for Central to recognize that your copy of the project is linked to the copy in Central.
As you make changes to the imported Flare project, you will need to synchronize those changes with Central periodically to make sure the local and cloud files are in sync. See Committing and Synchronizing (Pull, Push) in a Single-bound Model and Pushing in a Dual-bound Model.