Bring HaloPSA into your client experience.
Connect Halo tickets, projects, contracts, products, opportunities, and native CSAT to your client experience. Give clients one branded place to follow delivery, complete onboarding, review their IT, and approve the next plan.
- Service requests and client visibility
- Projects, templates, and onboarding
- Contracts, products, and planning
Where your PSA data shows up in MSPortal.
Follow the connection from customers, sites, users, and agents through delivery, commercial records, and client reviews. Each workflow below explains what your team can do and which changes reach Halo.
Start with the right clients, people, and locations.
Bring customers, sites, users, and agents into the portal’s company context. Company mapping connects the records in Halo to the client experience you manage in MSPortal.
- Synchronize customers, sites, users, and agents and match them to the correct portal companies and users.
- Choose which source companies and contacts to import, with automatic import options for future matching records.
- Give each client access to the relevant company information through MSPortal roles and permissions.
- Keep customer and agent scope aligned with the teams and clients the API agent can access.
How it connects
Halo supplies the source records. Importing a contact and inviting that person to the portal are separate actions; your MSP controls invitations and access.
Make the service desk part of your client portal.
Clients can submit requests and follow the conversation in MSPortal while your team works with Halo tickets and the routing you already use.
- Collect requests through configurable service forms or the AI Assistant, with a review step before submission.
- Use synchronized teams, ticket types, statuses, and priorities to configure the portal’s ticket workflow.
- Show ticket activity and replies, let authorized users follow up, and use the configured client-comment status.
- Bring ticket notes and time-entry information into service visibility and reporting, with technician mapping and company access.
How it connects
Ticket reads and supported creation/comment actions use the Halo connection. Your request-template configuration and PSA write permissions determine where new work is created.
Sync Halo projects and share progress with clients.
Connect the delivery plan to the conversation around it: the work your team manages, the progress clients see, and the decisions needed to keep moving.
- Synchronize Halo projects, milestones, child project tickets, notes, and recorded effort into the project workspace.
- Create projects, use reusable MSPortal templates, and create or update supported milestones and project-ticket details.
- Change project lifecycle and project-ticket status, add or complete checklist items, and post supported notes and time entries.
- Plan dates and assignments in the Schedule workspace. Review Smart Schedule proposals, then save task dates and assigned people to Halo.
- Share project updates, deliverables, milestones, decisions, and action items through the portal’s client visibility controls.
How it connects
Halo project and ticket writes depend on both API application and agent permissions. Owner/priority edits on the project-ticket Kanban/details controls are not enabled; assigned people can be saved through the Schedule workspace. Checklist progress-note editing and deletion are not offered.
Connect the client welcome to the delivery work.
Create a guided onboarding experience and link it to an existing Halo project—or create and link a new project from the onboarding portal.
- Guide clients through phases, tasks, forms, file uploads, meetings, training, surveys, signature tasks, and secure credential handoff.
- Create project tickets from selected onboarding tasks, with source-record badges and direct PSA links.
- Log time against linked onboarding work, including the description and billable setting.
- Configure automatic ticket creation, bidirectional linked-ticket status sync, and provider defaults in Onboarding settings.
- Choose Halo team, status, priority, ticket type, category, impact, and urgency defaults from synchronized choices.
How it connects
The onboarding pages, client forms, and submissions live in MSPortal. Project creation, linked work, time entries, and enabled status sync connect to Halo; background synchronization can introduce a delay.
Give clients a clear view of their contracts.
Bring Halo contracts into the client portal so clients and account managers can review service terms, billing context, balances, and the documents you share.
- Find records by name, type, status, and company. Review start/end dates, contract number, billing amount, and cycle where supplied.
- Read current and historical balances, including hours, incidents, or money where the source provides them.
- Upload and manage agreement PDFs in MSPortal and make the appropriate documents available to client readers.
- Keep each record within the mapped company and the reader’s assigned permissions.
How it connects
Terms and balances synchronize from Halo; shared PDFs are managed in MSPortal. This view does not edit, renew, or sign the source contracts, and available balance units vary by record.
Turn your PSA catalog into a client budget.
Use products already synchronized from Halo to build MSPortal’s budget catalog, then use that catalog in the budgets and plans you share with clients.
- Search source products by name, SKU, or category and identify which are already linked to the budget catalog.
- Create budget products from synchronized source details, including price, vendor, category, and recurrence where supplied.
- Link a source product to an existing budget product when you already have the right catalog entry.
- Use the resulting catalog products in planned costs and budgets, reviewing price and billing recurrence before sharing.
- Compare approved or archived budgets with synchronized, tax-exclusive customer invoice spend, including matched line outcomes and unallocated exceptions.
- Trace actual spending to invoice evidence using budget references, linked projects, and product identities; review exceptions or allocate spend manually.
How it connects
This imports or links Halo products into MSPortal. Linking preserves an existing budget product’s fields and price. Distributor ordering and subscription changes use separate Pax8 or Sherweb Storefront integrations. Budget actuals require invoice access, enabled invoice sync, and a mapped company. Posted Halo invoices contribute invoice-line detail where available. Overall actual spend covers eligible company invoices in the budget period and currency; use line outcomes for project-specific allocations.
Connect sales opportunities to the client’s plan.
Bring Halo opportunities into Planner so a sales discussion can become a visible roadmap initiative with context, timing, and an estimate.
- Import synchronized opportunities into Planner with titles, descriptions, due dates, and initial cost estimates.
- Map open, won, and lost opportunity categories to Planner statuses; configure automatic imports and ongoing field refresh.
- Link planned work to supporting devices, projects, tickets, goals, and compliance findings.
- Use the available Create opportunity action to create a new Halo opportunity from planning information, then save its relationship to the Planner item.
How it connects
Opportunity imports read from Halo; creating a new opportunity is an explicit PSA write. Configured source fields can refresh linked Planner items. A client’s roadmap approval does not by itself close or mark the source opportunity won.
Make invoices easier for clients to find and understand.
Show synchronized Halo invoices in the same portal clients use for service and planning, with company-scoped access and filters for the fields your PSA supplies.
- Review invoice dates, due dates, status, totals, and available balances and billing details.
- Open source PDFs where available, download selected PDFs in a ZIP, or export the current invoice page to CSV.
- Add invoices to an upcoming meeting agenda when they need a client conversation.
- Offer a Pay Now link on eligible invoices when a separate BenjiPays payment integration is configured.
How it connects
Halo supplies the outstanding amount; invoice synchronization is opt-in and scoped to mapped companies. Invoice records are read-only in MSPortal. Payments happen through the configured provider, and updated status arrives through source synchronization.
Connect the asset inventory to client planning.
Synchronize Halo assets and connect device information to the companies and planning workflows it supports.
- Bring in-scope assets into the supported device synchronization and import workflow.
- Use company mapping and import controls to associate discovered assets with the correct client.
- Link devices to roadmap initiatives and use lifecycle or warranty information when planning replacement work.
- Enable optional warranty writeback to update matched Halo source records with resolved warranty expiration dates.
How it connects
Inactive Halo assets are excluded from synchronization, and asset status exclusions control scope. Changing filters does not delete existing portal devices. Warranty writeback is separately enabled.
See planned changes alongside scheduled work.
Bring Halo change-calendar records and appointments into MSPortal’s shared calendar so your team can assess change windows with the surrounding work in view.
- View imported change windows, status, risk, company/site context, assigned technicians, and links to the source record.
- Read change and appointment layers alongside other accessible calendar events.
- Use MSPortal change workflows, freeze windows, and conflict indicators when planning portal-owned changes.
- Keep Halo-owned changes visible in the portal while maintaining their lifecycle in Halo.
How it connects
Imported PSA-owned changes are read-only in the portal calendar. Portal scheduling, freeze windows, and lifecycle actions do not write back to this PSA.
Make service delivery visible in your client reviews.
Use Halo information as part of a wider account conversation in MSPortal, from service activity and project progress to planning the next quarter.
- Use synchronized service and project information in dashboards, client reviews, and reporting blocks.
- Turn the delivery context into a review conversation alongside roadmaps, budgets, and recommendations.
- Use AI-assisted summaries and report drafting, then review the result before sharing it with clients.
- Import Halo’s native satisfaction responses into the CSAT Dashboard, CSAT widgets, report blocks, and CSV exports.
- Keep using Halo’s own surveys. Enable satisfaction imports, grant feedback access, and select the matching 1–3, 1–5, or 1–10 rating scale.
How it connects
Halo satisfaction imports are opt-in. Responses need synchronized tickets, company mapping, and reader CSAT permissions; the configured rating scale determines score normalization.
Understand the relationship between revenue and support effort.
Use synchronized Halo commercial and service data in MSP Tools to review client health, ticket trends, and operational account economics.
- Compare available revenue, support effort, seat economics, and complete-month revenue trends.
- Classify recurring and non-recurring revenue using service/SKU, invoice line-item type, Contract Type, Charge Type, and individual contract overrides.
- Configure the reporting model by device, user, or a hybrid of the two, with company seat profiles where needed.
- Use ticket trends and client health evidence to prioritize account conversations and planning work.
How it connects
These are MSP staff views. Results depend on source coverage, company mapping, revenue classification, and the reporting model; they are operational indicators, not accounting net-profit statements.
Choose what to sync and who can see it.
Choose the companies, data, and actions your MSP needs. Portal roles control what staff and clients can see and do; PSA permissions control access to the source records.
Connect your PSA
Create a Halo API application using Client ID and Secret (Services). Enter your Halo URL, Client ID, and Client Secret, and choose an API agent with access to the intended clients and teams.
Check the access you need
Review required and optional capabilities in the Permissions step. Grant source access for the records you want to synchronize and the specific write operations you intend to use.
Select the data and defaults
Select teams, excluded statuses, company and contact filters, and optional data such as projects, opportunities, invoices, products, assets, changes, and satisfaction ratings.
Map companies and import records
Match source companies to portal companies. Review the intended contact and device imports, then configure invitations, staff roles, and client visibility.
Verify the client workflow
Check the completed sync and use a designated test company to verify requests, project actions, onboarding links, and the records a client can see. A successful read-permission check does not verify every write.
Questions about the integration
Does MSPortal replace HaloPSA?
HaloPSA remains the source for your PSA records. MSPortal adds a branded client experience, planning, reporting, onboarding, and collaboration around those records, with supported actions that can write back to the PSA.
Can we create and manage Halo projects from MSPortal?
Halo project and ticket writes depend on both API application and agent permissions. Owner/priority edits on the project-ticket Kanban/details controls are not enabled; assigned people can be saved through the Schedule workspace. Checklist progress-note editing and deletion are not offered. Supported project creation, templates, lifecycle updates, and scheduling are described in the project workflow above.
Can onboarding create work in Halo?
Yes. Link an onboarding portal to an existing Halo project or create and link a project. Create linked tickets or tasks from onboarding tasks, log time, and enable automatic creation or bidirectional status sync using the configured provider defaults.
Can clients change contracts, products, or invoices in the PSA?
The contracts and invoice views expose synchronized information. Product import creates or links the MSPortal budget catalog. These are separate from editing PSA billing records, distributor orders, or a payment integration.
Does connecting the PSA turn on every feature for every client?
You choose data scope and optional syncs. Company mapping determines which client records belong together, and MSPortal roles determine visibility and actions. Extra services such as distributor ordering or invoice payment links need their own integrations.
Is all synchronization bidirectional and live?
No. Source synchronization, portal-owned data, and explicit PSA writes are different workflows. Record updates can arrive through background synchronization. Each section describes the direction and the supported write actions.
Walk through the workflows that matter to your MSP.
Bring your questions about projects, onboarding, commercial data, and client access. We’ll show how the integration fits your process.
See it with your PSA