內容簡介
Softtara Resident Management Portal 是一款專為住宅物業設計的外掛，提供居民、技術人員與物業團隊之間的連接，簡化日常管理工作，讓居民能夠輕鬆提交維修請求並追蹤進度。
【主要功能】
• 居民自助註冊與個人儀表板
• 技術人員專屬儀表板與任務管理
• 自動化電子郵件通知系統
• 可自訂的品牌設定與通知選項
• 工作訂單數據匯出至 CSV 或 Excel
• 即時應用內通知功能
外掛標籤
開發者團隊
② 後台搜尋「Softtara Resident Management Portal」→ 直接安裝（推薦）
原文外掛簡介
Resident Portal — Connect Residents, Technicians & Property Teams
Resident Portal gives property teams a self-contained system for running the day-to-day work of a residential property, from a resident’s first login to a technician closing out a maintenance ticket.
Residents register for their own account, land on a personal dashboard, and submit maintenance requests or general inquiries with photos or documents attached. Every request gets an automatic, human-readable ticket number and a visible status timeline, so residents always know where things stand without calling the office.
Technicians sign in to their own dashboard to see what’s assigned to them, update status, and leave notes as work progresses — residents are notified automatically at each step.
Property staff manage everything from the WordPress admin: residents, technicians, and work orders each have a dedicated screen with search, filtering, sorting, and bulk actions, plus a dashboard with an at-a-glance summary and self-hosted SVG charts (no external charting service or CDN). Work order data can be exported to CSV or Excel, or opened in a clean print view, always reflecting whatever filters are currently applied.
Every automated email — registration, verification, new request confirmations, status updates, assignments, replies, and more — renders through one consistent HTML template and can be customized from Settings, including the subject line and body text of each message. Outgoing mail can optionally be routed through a custom SMTP server, with the SMTP password encrypted at rest, or queued in the background for sites with slow mail delivery.
An in-app notification bell keeps residents, technicians, and administrators up to date without relying on email alone — residents see it in their dashboard, and administrators and technicians see it in the WordPress admin bar.
A dedicated Settings screen covers company branding, per-notification on/off toggles, upload restrictions, status badge colors, and appearance — so the portal can be tailored to a property’s branding and workflow without touching any code.
Key Features
Resident Portal
Self-service resident registration with email verification
Login, logout, and forgot/reset password flows
A personal dashboard with request summary, quick actions, and recent activity
Submitting a Maintenance Request or General Inquiry, with priority, category, apartment number, property area, common area, location description, and up to 5 attachments
Paginated request history and a detail view with ticket number, current status, a visual status tracker, structured status history, an activity timeline, and attachments
Replying directly to staff from a request’s detail view
Profile viewing and editing
Work Order Management
Automatic, human-readable ticket numbers (e.g. MR-000123, GI-000045)
A configurable status lifecycle (open, assigned, in progress, completed, closed, cancelled)
Technician assignment, with resident and technician notifications on assignment and status changes
Internal Notes (visible to all staff), Private Notes (visible only to the author), and resident-visible Replies
Soft delete with a Trash view (restore or permanently delete)
An “aging” indicator that flags unresolved requests open longer than 10 days
Technician Dashboard
Overview, My Requests, request detail, and Profile views
Updating the status of assigned requests and adding notes
The same resident-facing notifications used for admin-initiated status changes
Administration
Dedicated screens for Residents, Technicians, Work Orders, and Activity, built on WordPress’s native list table with search, filters, sorting, and pagination
A dashboard with summary statistics and self-hosted SVG charts
Bulk actions on Residents and Work Orders
A read-only, filterable Activity log for auditing
Work order search across ticket number, title, description, apartment number, and resident name/email, plus Status, Priority, Type, Technician, and Date Range filters
Export to CSV, export to a genuine .xlsx Excel file, and a print-ready view — all reflecting the current filtered/sorted results, not just the current page
Email & Notifications
A shared, table-based HTML email template used across every automated message
Editable Subject/Body for every automated email, using placeholder tokens (e.g. {resident_name}, {ticket_number}, {reply_text}), with a Reset to Default option and a live preview
Optional custom SMTP delivery (host, port, encryption, username/password, with the password encrypted at rest), applied through WordPress’s standard phpmailer_init integration, plus a Send Test Email tool
An optional background email queue (WP-Cron based, with retry) for sites with slow mail servers, off by default
An in-app notification bell for residents (dashboard topbar) and administrators/technicians (WordPress admin bar), with live updates, mark-as-read, and mark-all-read
Settings
Company information: name, logo, and contact email/phone
Per-notification on/off toggles for discretionary email and in-app alerts (core account emails always send)
Upload restrictions: allowed file types and maximum upload size
Status badge colors, customizable across both the resident and admin interfaces
Appearance: accent color and logo placement
Privacy
Resident Portal stores the data needed to operate a resident/work-order portal on your own WordPress database:
User information — for residents and technicians: name, email, phone, apartment number (residents), profile photo, and the linked WordPress user account.
Work order information — request type, priority, category, location details, description, status, and assignment history.
Attachments — files uploaded by residents when submitting a request, validated by their actual file content rather than the browser-supplied file type.
Activity data — a log of actions taken on residents, technicians, and work orders, used for the admin Activity screen.
Email-related information — the content of outgoing notification emails, and, if the optional background email queue is enabled, a temporary record of queued messages. If a custom SMTP server is configured, its password is encrypted before being stored.
Resident Portal does not send data to any third-party analytics or tracking service. If a site administrator configures a custom SMTP server under Email Settings, outgoing email is transmitted through that administrator-selected SMTP provider rather than the server’s default mail transport; no other external service is contacted by the plugin.
External Services
Resident Portal does not connect to any external API or third-party service by default.
If a site administrator chooses to configure a custom SMTP server under Resident Portal → Email Settings, outgoing plugin emails (such as verification, work order, and status-update notifications) are transmitted through that administrator-specified SMTP provider instead of the server’s default mail transport. This is entirely optional, off unless configured, and uses whichever SMTP provider the administrator selects — Resident Portal itself does not send data to any specific third party. Sending email through SMTP is subject to that provider’s own terms of service and privacy policy.
The admin dashboard’s charts are rendered as self-hosted SVG markup generated by PHP; no external charting library or CDN is used.
