3. Context and scope

Business context

flowchart TB
  Visitor[Visitor] -->|views availability| MRBS[MRBS 1.12.2]
  User[Authenticated user] -->|manages own bookings| MRBS
  Admin[Administrator] -->|configures and governs| MRBS
  MRBS -->|notifications| Recipient[Mail recipient]
  Calendar[Calendar client] <-->|iCalendar import/export| MRBS
  MRBS <-->|identity and attributes| IdP[Identity provider]

Partner	Information exchanged
Visitor	Public calendar pages and permitted booking details
Authenticated user	Credentials or session identity, booking commands, search and report criteria
Administrator	Configuration, user and resource administration, approvals and upgrades
Identity provider	Login result, username, display name, email, groups or roles
Mail recipient	Booking notification and optional iCalendar attachment
Calendar client	RFC 5545-compatible calendar data

Technical context

flowchart LR
  Browser -->|HTTP/HTTPS| Pages[PHP page controllers]
  Pages --> Core[MRBS application]
  Core -->|PDO| SQL[(MySQL/MariaDB or PostgreSQL)]
  Core -->|LDAP/CAS/SAML/CMS/API| Identity[External identity system]
  Core -->|SMTP/sendmail/mail| Mail[Mail transport]
  Core -->|HTTP(S)| Remote[Remote import or integration endpoint]

Inbound interfaces

• Browser requests to PHP pages under web/
• Form submissions for booking and administration commands
• AJAX requests used by interactive pages
• Import uploads or permitted remote import sources
• Command-line entry points when explicitly enabled

Outbound interfaces

• PDO connections to the MRBS or external user database
• LDAP, CAS, SAML, CMS, mail-server, and Wix integration calls
• SMTP, Sendmail, qmail, or PHP mail()
• iCalendar, CSV, spreadsheet, and PDF-style export responses
• HTTP requests for selected imports and integrations

Data ownership

MRBS owns booking, room, area, local-user, participant, variable, zone, and optional session data in its configured tables. External identity and mail systems retain ownership of their accounts and delivery state.

Local filesystem configuration remains operator-owned and is intentionally not stored in the MRBS database.