Database

Shared Database Architecture

The Portal, API v1, and API v2 all connect to the same MySQL database. This means:

The database connection is configured in config/database.php using standard Laravel MySQL settings:


DB_CONNECTION=mysql
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=housr
DB_USERNAME=forge
DB_PASSWORD=

The strict mode is set to false to maintain compatibility with the existing schema.

Table	Model	Notes
`users`	`User`	All platform users (students, agents, moderators, admins, B2B). Role in `role` column.
`internal_users`	`InternalUser`	Housr staff accounts for admin panel access
`internal_roles`	`Role`	Staff role definitions
`internal_permissions`	`Permission`	Granular permission definitions
`internal_role_user`	—	Pivot: internal users to roles
`internal_permission_role`	—	Pivot: roles to permissions
`password_reset_links`	`Password_reset_link`	Password reset tokens
`user_sessions`	`UserSession`	Login session tracking
`bypass_codes`	`BypassCode`	Auth bypass codes

Table	Model	Notes
`houses`	`House`	Property listings (soft deletes)
`property_operators`	`Property_operator`	Companies managing properties (soft deletes, parent-child hierarchy)
`property_operator_verifications`	`PropertyOperatorVerification`	Operator verification status
`house_image_rooms`	`House_image_room`	Room images for houses
`future_house_availabilities`	`Future_house_availability`	Future availability dates
`featured_houses`	`Featured_house`	Featured/promoted houses
`house_changes`	`House_change`	Audit trail for house edits
`house_viewed`	`House_viewed`	View tracking
`building_details`	`BuildingDetail`	Additional building information

Table	Model	Notes
`viewing_requests`	`Viewing_request`	Student viewing requests
`viewing_request_status_changes`	`Viewing_request_status_change`	Status audit trail
`booking_slots`	`Booking_slot`	Available viewing times
`booked_slots`	`Booked_slot`	Confirmed viewing bookings
`enquiries`	`Enquiry`	Deprecated — legacy enquiry records
`enquiry_status_changes`	`Enquiry_status_change`	Legacy enquiry status trail
`website_enquiries`	`Website_enquiry`	Enquiries from the website
`concierge_direct_transfers`	`Concierge_direct_transfer`	Direct concierge transfers

Table	Model	Notes
`chat_rooms`	`Chat_room`	Chat conversations
`chat_room_members`	`Chat_room_member`	Chat participants
`chat_room_moderations`	`Chat_room_moderation`	Moderator assignments
`messages`	`Message`	Chat messages (synced with Firebase)

Table	Model	Notes
`contracts`	`Contract`	Tenancy agreements
`contract_members`	`Contract_member`	Tenants on a contract
`huddle_contracts`	`Huddle_contract`	Huddle integration contracts
`documents`	`Document`	Contract and other documents

Table	Model	Notes
`events`	`Event`	Events with status, access_type, schedule
`event_tickets`	`EventTicket`	Issued tickets
`event_rsvps`	`EventRSVP`	RSVP responses
`event_user_applications`	`EventUserApplication`	Application-based access requests
`event_exclusive_users`	`EventExclusiveUser`	Users with exclusive access

Table	Model	Notes
`notifications`	`Notification`	Push notification definitions
`notification_logs`	`Notification_log`	Send logs
`notification_opens`	`Notification_open` / `NotificationOpen`	Open/engagement tracking
`drops`	`Drop`	Notification drops
`drop_opens`	`Drop_open`	Drop engagement
`portal_notifications`	`Portal_notification`	In-portal notifications

The Portal does not own the database schema — migrations exist but the canonical schema is shared with the API repos.
Many models use $guarded = [] (mass assignment unprotected) for flexibility.
Some models explicitly set public $timestamps = false when the table lacks created_at/updated_at columns.
Soft deletes are used on House and Property_operator models.
The CompanyScope trait on User allows scoping queries by company_name for multi-tenant operator views.