Gfacility
Contact us

Overview

Overview

Overview of the configuration layer, everything you'll set up in Gfacility, and what each part covers. A short tour so you know what's coming before we dive deeper step by step.

Updated Jul 25, 2026

Configuration · overview

After the business phase comes the real work: setup. Gfacility splits that configuration into seven areas, from general shared logic to module-specific settings. This chapter gives you a tour so you know up front what’s coming and in what order.

The seven configuration areas

Building Blocks

The shared logic that runs above every module: classifications, workflows, custom fields, filters, groups, notifications and workgroups. Get it right once = never per module again.

Module configuration

Module-specific settings per area: Asset, Configuration items, Finance, Knowledge base, Products, Rooms, SLA, Tasks, Tickets and Visitors. Only build what you actually use.

Devices

Physical devices in your building: dashboards (analytics screens), visitor kiosks (self check-in) and room signages (meeting-room displays). Enterprise-tied.

Miscellaneous

Other settings that don't fit a single module: communication templates, GDPR cleanup, holiday calendar and QR code generator. Small in scope, big in impact.

Appearance

Look & feel of the portal: homepage templates for different roles and the visual theme (colors, logo, typography). Important for adoption and brand consistency.

AI

The smart layer: AI Agents (autonomous actions), AI Use Cases (predefined scenarios), System Contexts (knowledge injection) and Consumption Control (cost monitoring).

Automation

What runs in the background without anyone doing anything: Office 365 sync (resources, mailboxes), user sync from Entra ID or Google Workspace, and the Automations engine: one rule builder for every module, with triggers, conditions, actions, webhooks and a full run history. The old notification rules, task rules and CI task rules are legacy and get rebuilt here.

There’s no sacred order, but there is a logical one. Most dependencies flow one way: Building Blocks are used by modules, modules are fed by masterdata, AI leans on everything below it.

Global build-up

  1. 1Load masterdata: organizations, locations, users (mostly sits in 'To (re)map' until we work out the structure).
  2. 2Build Building Blocks: taxonomy, process flows and shared templates before a single module is switched on.
  3. 3Activate modules: start with the modules from phase 1 of your MoSCoW. Not everything at once.
  4. 4Devices & Appearance: physical screens and visual identity, once the digital flows are right.
  5. 5Automation & AI: only when the base is running stably. Otherwise you're automating a process you still have to adjust.
  6. 6Miscellaneous: wrap up communication templates, holidays, GDPR settings just before go-live.