Course contents

Module 1: FortiManager FundamentalsLesson 1.2 (2 of 2 in this module)2 of 17 in the FortiManager Administration course

The FortiManager GUI and the management workflow

The main GUI areas, the ADOM selector, and the loop of edit, install and verify that every task follows.

Intermediate · 15 min read

Written for FortiManager 7.6 · FortiManager 7.4: not yet reviewed

Exam domain: NSE 6 FortiManager (7.6) · Administration

Before this: What FortiManager is and how it manages FortiGates

You'll learn to name the main GUI areas, say which ADOM you are working in, and follow the edit, preview, install and verify loop.

Technical definition

Install is the step that sends configuration from FortiManager to a FortiGate. Editing in FortiManager changes FortiManager's own copy; nothing reaches the device until it is installed.

The same screens, every day

The FortiManager GUI has a handful of areas you will use constantly. Learn where they are and most tasks become a matter of choosing the right one.

The same screens, every day
The same screens, every dayArea; What you do there. Device Manager: Add devices, see their status, edit device settings, install and view revisions Policy & Objects: Policy packages, addresses, services, profiles, dynamic mapping FortiGuard: Updates, firmware images and licence information for managed devices System Settings: ADOMs, administrators, HA, network and logs of FortiManager itselfAreaWhat you do thereDevice ManagerAdd devices, see their status, edit device settings, install and viewrevisionsPolicy & ObjectsPolicy packages, addresses, services, profiles, dynamic mappingFortiGuardUpdates, firmware images and licence information for managed devicesSystem SettingsADOMs, administrators, HA, network and logs of FortiManager itself

On small screens, swipe sideways or focus the diagram and use the arrow keys.

Each item on the left, with what it means on the right.

Menu names move a little between releases, so follow the area rather than the exact path. If a menu you expect is missing, check that you are in the right ADOM and that your administrator profile allows it.

The edit, preview, install, verify loop

The loop behind every FortiManager task
The loop behind every FortiManager taskFour steps: edit, preview, install and verify. After verify, the next change begins at edit.1 EditChange a package,object or template2 PreviewSee the exact CLIbefore it is sent3 InstallPush to theFortiGate4 VerifyCheck status andthe install log

On small screens, swipe sideways or focus the diagram and use the arrow keys.

Editing in FortiManager changes FortiManager's copy only. Nothing reaches the FortiGate until the install step.
  1. Edit. Change a package, object or template. The change exists only in FortiManager.
  2. Preview. Use the install preview to see the configuration difference before it is sent.
  3. Install. Push the change to the target FortiGates.
  4. Verify. Check the device status and install log, and test a real flow if the change affects traffic.

Every later lesson is a variation on this loop. When something goes wrong, ask which step it failed at: the edit that was wrong, a preview that was skipped, an install that errored, or a check that was never done.

Check your understanding

Predict · scenario 1

You changed a policy in a package and saved it. The FortiGate still has the old behaviour. Why?

Predict · scenario 2

Which step shows the exact difference before it is sent?

Predict · scenario 3

A menu is missing. What should you check first?

Further reading in Fortinet's documentation

Links open the named page in Fortinet's documentation (checked 19 October 2026). RouteLearn is an independent educational resource, not affiliated with or endorsed by Fortinet. Fortinet, FortiGate, FortiOS, FortiManager and FortiGuard are trademarks of Fortinet, Inc. Example output on this page is illustrative.

FAQ

Where do I see which ADOM I am in?
The ADOM selector at the top of the GUI shows the current ADOM when ADOMs are enabled. Policy and device views always belong to the ADOM selected there.
Why does the install preview matter?
It shows the exact configuration difference FortiManager will send. It is where you notice a change you did not intend, such as removal of something configured on the FortiGate itself.