LGU San Francisco logo
LGU San Francisco
LGU San Francisco Information System
Platform Landing

LGU San Francisco Information System

A shared digital platform for LGU office systems, internal workflows, and operational records. This public page gives visitors a clear entry point into the active information systems already running under the LGU platform.

Internal workflow actions, approvals, and records creation remain limited to authenticated and authorized users.

Platform Modules

Active and planned system areas

The platform is designed to host multiple office systems under one LGU-wide foundation. Public visitors can use these module entries as public reference pages, while internal work remains behind authenticated access.

GSO Live
General Services Office

Legacy GSO workflows being integrated into the LGU platform.

DTS Future
Document Tracking System

Planned office workflow module for routing, receiving, forwarding, and monitoring official document movement.

Planned module
PROCUREMENT Future
Procurement Management

Planned procurement workspace for BAC-aligned tracking, supplier coordination, and purchasing workflows.

Planned module
Platform Coverage

Shared capabilities across the system

Office modules do not stand alone. They run on top of shared platform capabilities so the LGU can keep identity, access, logging, notifications, and reusable workflow infrastructure aligned.

Identity and access

Users, roles, module access, and permission assignments are managed through a shared platform access model.

Audit and notifications

Important actions and workflow changes can be traced and surfaced through shared audit and notification capabilities.

Tasks and approvals

Modules can surface work inside their own shell while still reusing the shared task engine and review standards.

Public Reminders

Before using internal platform features

A few practical reminders for visitors and office users accessing the platform.

Public pages are informational

Public landing pages help visitors understand the office systems available, but record creation and approvals remain internal.

Office workflows stay module-owned

Each module keeps its own processes, records, and business rules even while using the same platform foundation.

Login is for authorized users

Only users with assigned accounts and module access should proceed into internal dashboards and transaction screens.