Administration

Administration screens are reserved for administrators (some are open to planners). They structure the instance: organization, reference data, users, settings, integrations.

Organization

Administration > Organization: sites (code, name, time zone, currency), warehouses per site, teams (discipline, site) and their members. The site code appears in the functional location numbers exported to SAP; choose it short and stable.

Equipment classes and reference codes

• Equipment classes: pumps, compressors, motors, valves, instruments... with their standard preservation tasks and their optional KPI targets.
• Reference codes: disciplines, failure modes, causes, remedies, isolation types, part categories. The drop-down lists of the whole application feed on them; deactivate rather than delete a code already in use.

Users and roles

Administration > Users: creation (e-mail, name, initial password), roles, site and team, preferred language, activation. A deactivated user can no longer sign in but keeps their history. A technician attached to a team sees on mobile the team's work orders not yet assigned by name.

Settings

Administration > Settings groups the settings by category: numbering, criticality thresholds, rule blocking work orders without permit, SAP/Maximo exports, AI assistant (encrypted key, model, length, thinking), AI costs (budget, margin, rate, currency), SCADA, circuits, mobile, instance. Sensitive values are encrypted; a change is taken into account immediately.

User manual

Administration > User manual (editing) lets you modify this manual without republishing the application: each shipped chapter can be adapted (the shipped text remains recoverable with Restore shipped text), new chapters can be created, images inserted, and a chapter unpublished while it is being written. The related screens determine the chapter opened by the "?" button; keywords help the search. Changes are immediately visible in the help, used by the AI assistant, and sent to mobile devices at the next synchronisation (without images, which are consulted online).

Permit templates, circuits, SCADA, KPI targets, mobile devices, AI costs

Each has its own chapter in this manual: Work permits, Approval circuits, Automatic meters, KPIs and reliability, Mobile application, AI assistant.

SOFTIC Intranet

Administration > SOFTIC Intranet links the instance to the SOFTIC intranet: single sign-on from the intranet tile and display of Softic.GMAO in an intranet tab, a “Sign in with SOFTIC Intranet” button on the sign-in page (Button mode, or Automatic: any page opened without a session goes through the intranet first), attached accounts (a user attached to Softic.GMAO in the intranet user form gets an account on first sign-in, in their intranet company and with the role of the form; the intranet can be authoritative for the role on every sign-in). On arrival, the company is the one of the account; site and team stay those of the account. Excluded roles (SOFTIC by default) always sign in with a password. Applied immediately, no restart; “Check the intranet” tells what the intranet supports.

Backups and operations

Operations (updates, backups, SaaS instances) are described in the technical documentation delivered with the application (docs\PROCEDURE-MISE-A-JOUR.md, docs\EXPLOITATION-SAAS.md). Remember the essential: the database and the App_Data folder (encryption keys, attachments) must be backed up together; without the keys, the secrets encrypted in the database can no longer be read.