Uploading (Binding) Projects

You can upload a project to Central from the desktop Flare application. A copy of the project will therefore reside in the cloud via Central, and you will be able to keep the local and cloud versions of the project synchronized using integrated source control. You will also be able to generate and publish Flare targets using Central.

Permission Required?

For this activity, you must have the following permission setting:

For more information about permissions, see Setting User Permissions.

How to Upload (Bind) a Project to Central

  1. Open the project in MadCap Flare.
  2. Select View > MadCap Central. The MadCap Central window pane opens.
  3. If you are not yet logged in, enter the same user name (i.e., email) and password that you use for logging into Central, and click Log In.
  4. Click .

    Tip If this button is disabled, try clicking in the window pane first.

  5. In the Bind Project dialog, you can complete any of the fields, then click OK.

    • Select License If you are a member of more than one MadCap Central license, you can use this field to choose the license where the project will be added.
    • Enter project name This shows the name of the project. You can change the name if you want, but in most cases you will probably want to keep the same name.
    • Enter project description You can enter a short description, which can then be seen when anyone views the project profile in Central.
  6. In the success message, click OK. The MadCap Central window pane adjusts, showing properties for the current project.

  7. (Optional) In the local toolbar, click to open Central.
  8. (Optional) In Central, you can click Projects on the left side to open the Projects page. The uploaded project should be shown in the grid. If it isn’t, click to refresh the page.

    Note Binding your project to Central adds an ID to the Flare project file. If your project is dual-bound (see Dual-Bound Projects), be sure you check in the project to your third-party source control provider after you bind to Central. This will ensure that other users who import the project from source control have the most recent version of the project file (i.e., the one with the Central ID). The Central ID is necessary for Central to recognize that each user's local copy of the project is linked to the copy in Central.

    Note When you bind a project to Central, a .gitignore text file is created in your local project folder. Advanced users can edit the .gitignore file with a text editor to control which files or folders can be pushed to your Git repository. You can also specify which files and folders are ignored by Git, and are not pushed to the repository.

    Note If you intend to build a target that links to an outside Flare project (e.g., for the purpose of importing files via Global Project Linking, project merging, or multilingual output), make sure that the other project is also uploaded to Central. Otherwise, the automated imports or merging will not work. See Setting Up Project Linking.

What’s Next?

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 in a Single-Bound Model and Pushing in a Dual-Bound Model.