MadCap Central is a cloud-based platform that lets you plan, track, and manage the processes, content, and teams that are at the heart of your organization.
For more complete information about the benefits of Central, see its online Help:
Although MadCap Central is located in the cloud, it is integrated with MadCap Flare. This integration lets you store copies of your projects in Central, continue to work on them locally in Flare, and keep both sets of copies in sync. You can use Central to quickly publish output (and roll back when necessary) without the need to involve an IT department.
Following are tasks that you can perform from the MadCap Central window pane in Flare:
- Log In and Log Out If you have an account in Central, you are able to log in and out of your account from Flare. When you are logged in, you are able to access project properties, upload (bind) and import projects, and push project changes to the cloud. See Logging In and Out of Central in Flare.
- Uploading (Binding) Projects You do not have to be a Flare user in order to take advantage of the various features in MadCap Central. However, if you would like to add a Flare project to a Central license, you can upload the project from your 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. See Uploading (Binding) Projects.
- Importing Projects 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. See Importing Projects from Central.
- Committing and Synchronizing (Pull, Push) in Single-bound Model If you are working in a single-bound model, you author content in Flare. When you want to transfer your changes to Central, you commit files that you’ve changed to the repository. This gives you the opportunity to organize your files into different groups when you add them to Central, and to add a comment to each commit as well. After this, you synchronize (pull, push) your changes with the cloned project on Central. See Committing and Synchronizing (Pull, Push) in a Single-bound Model.
- Pushing in Dual-bound ModelIf you are working in a dual-bound model, you author content in Flare and use your third-party source control tool to synchronize your files with those from other writers. After this, you use Flare to push those changes to Central. See Pushing in a Dual-bound Model.
- Viewing Project Properties If you have access to a project in Central (i.e., you have been added to the project), you can view its properties in the MadCap Central window pane. This lets you see relevant information about the project, such as when it was added to Central, the number of files in the project, and build information. See Viewing Project Properties.
- Removing Bindings If you no longer need your project to be bound to Central, you can remove its binding. Removing the binding from a project does not remove that project from Central; instead, it simply removes the link between Central and your local project. The project will still be available locally, but you will no longer be able to upload (push) changes from your local project to the cloned project on Central. See Removing Bindings from Projects.
When you upload a Flare project to Central, the files are connected to Central via an integrated source control system. Your interaction with source control can follow one of two models—single-bound or dual-bound. Single-bound projects are not bound to an additional third-party source control provider; they only use Central's source control system. Dual-bound projects, on the other hand, are already bound to another source control provider, and therefore are bound to both the original third-party source control provider and to Central.
Security and privacy are top priorities at MadCap Software, especially when providing customers with a cloud-based system in Central. We are committed to keeping your files, data, and communications secure. Therefore, in choosing Microsoft® Azure as a partner, we focused on selecting a security center that understands the importance of privacy and complies with the highest international and industry-specific compliance standards and uptime guarantees. Microsoft Azure regularly undergoes rigorous third-party audits to ensure and verify the highest level of security controls.
For more information, see the following:
Also see Security and MadCap Central.
Note: At this time, you cannot perform source control tasks from the Central interface. This can be done only from the Flare project.
Note: Certain Flare features are not supported when generating output from Central. This includes limitations on which output formats can be generated and viewed from Central. See Flare Features Not Supported in MadCap Central.
Note: MadCap Central is sold separately from Flare. Please contact MadCap Software Sales for more information.