MSPortal, question by question.

MSPortal costs a flat $99 USD per month for up to five client organizations. From six organizations, each organization is billed at a volume rate that falls from $20 to $15 per month as you add clients, and above 400 organizations pricing is custom. Every plan includes all modules, unlimited technicians, unlimited client users and unlimited AI usage.

MSPortal integrates with four PSA platforms: ConnectWise Manage (ConnectWise PSA), HaloPSA, Autotask and Syncro. With each one, the portal can create tickets, add notes and change ticket status, and those changes are written to the PSA. Beyond tickets, ConnectWise, HaloPSA and Autotask also sync projects, invoices, agreements or contracts, products and opportunities. Syncro covers tickets, contacts and devices.

Yes, MSPortal has both. Its remote MCP server lets AI clients such as Claude, Cursor, Codex and Gemini CLI read and change portal data under the signed-in user's permissions, with browser sign-in and a confirmation step before most changes. Its REST Public API (v1) uses API keys and is documented with an OpenAPI specification. Both are included in every plan.

In MSPortal, AI does specific drafting and lookup jobs. It turns a client's description into a completed ticket form, summarizes ticket histories for technicians, drafts QBRs and reports with cited sources, drafts compliance checks and client-ready notes, and proposes Planner, project and template changes. Most results arrive as drafts or proposals a person reviews first. One exception: a compliance note draft saves straight into client-visible notes, so edit it right away.

Supported PSA integrations include ConnectWise Manage, HaloPSA, Autotask and Syncro. Entities, routing fields and write actions vary by provider; check the integration guide and configured permissions for your workflow.

Yes. MSPortal syncs Microsoft Secure Score data and recommendations, and you can use the Planner workflow to prepare follow-up work. Available metrics and history depend on the Microsoft permissions you grant and the sync schedule.

Connections use the provider's supported OAuth or API credentials. Configure only the permissions needed for your workflows; supported write actions require write access. Contact us for current security and credential-handling details.

Contact our team directly to request a new integration. We prioritize new integrations based on customer demand and technical feasibility.

Yes. You can connect a PSA, device platforms and Microsoft 365 together. Company mapping, synchronization and permissions determine which records appear in each module; a connection alone does not populate every dashboard.

The catalog includes Datto RMM, Syncro, ConnectWise Asio, NinjaOne, N-able N-central, Addigy, Cisco Meraki, UniFi and Domotz. Device coverage varies by connector. Check the catalog status; planned integrations are not available features.

ConnectWise PSA 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.

Project, phase, ticket, checklist, and time operations use the API member’s corresponding ConnectWise permissions. Project-team assignments are read in MSPortal and maintained in ConnectWise. Client collaboration content and scheduling rules stay in MSPortal. Supported project creation, templates, lifecycle updates, and scheduling are described in the project workflow above.

Yes. Link an onboarding portal to an existing ConnectWise 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.

The agreements 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.

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.

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.

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.

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.

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.

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.

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.

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.

Autotask PSA 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.

Autotask project tasks use Projects/Tasks permissions, separately from Service Desk tickets. Task notes in this workflow use time-entry notes; standalone task-note creation and editable checklists are not supported. Scheduling rules and client collaboration content stay in MSPortal. Supported project creation, templates, lifecycle updates, and scheduling are described in the project workflow above.

Yes. Link an onboarding portal to an existing Autotask 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.

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.

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.

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.

Assessing clients against your standards, turning gaps into roadmap items and budgets, preparing QBRs and reports, and sharing the results in each client's branded portal. Client Health and Financial Reporting help your team decide which clients need attention.

Clients see what you share with their role: compliance scores and checks, risks you approve for them, roadmap items you don't hide, budgets, dashboards and published reports. Client Health, the standards matrix and Financial Reporting stay internal to your team.

No. MSPortal syncs tickets, invoices, devices and other records from ConnectWise PSA, Autotask, HaloPSA or Syncro, and your team keeps working in the PSA. Reports, scores and grades use the latest sync, so a number can trail the PSA by one sync cycle.

A scheduled report, including one AI writes, publishes or sends on its own unless you turn on approval for that schedule. Changes the assistant suggests, such as new checks or Planner items, wait until someone on your team applies them. The AI Draft button on a compliance check saves straight into the check's client-visible notes, so review the check before you share it.

MSPortal covers the assessment, roadmap, budget and QBR work that dedicated vCIO tools handle, and puts the results in a client portal. Compare the workflows, integrations and client permissions you rely on before you switch. Our comparisons with myITprocess, ScalePad Lifecycle Manager and CloudRadial list the differences we could verify.

You can import CIS Benchmarks by product with Level 1 and Level 2 profiles, NIS2, CAN/DGSI 104, and best-practice playbooks. Use of CIS Benchmark content is subject to your CIS licensing. For HIPAA, SOC 2 or an internal standard, build your own checks or have AI draft them from a description. MSPortal tracks checks and evidence. It does not certify compliance.

Describe what you want to check. AI proposes a plan, and after you approve it, drafts up to 40 checks. You choose which ones to save. AI can also rewrite a single check, translate checks into 15 languages, and draft a client-facing note with a summary, business impact and remediation steps. Review AI text before you rely on it, because a drafted check does not show that a requirement is met.

Yes. Clients see their score and grade, pass and fail counts, overdue checks, public notes, shared files and any risks you approve for them. You can hide individual checks, and private notes are never sent to client users. If you give a client role write access, those users can update check status and upload evidence.

Each check is weighted by scope (company, location or device), criticality and priority. Statuses can give partial credit, and statuses such as N/A can be left out. Scores map to A to F grades. The weights and grade thresholds apply to your whole portal, and each client gets its own score from its open compliance runs.

Yes. The report builder has compliance blocks for score overview, breakdown by group, progress over time and non-compliance items, plus risk blocks for the register, matrix and exposure trend. You can schedule these reports and require approval before each one sends.

ConnectWise, HaloPSA, Autotask and Syncro. With all four, the portal can create tickets, add notes and change status. Attachments work with every one except Syncro. ConnectWise updates arrive by webhook, and Autotask and HaloPSA can use webhooks once you set them up. Otherwise a scheduled sync brings changes in within 5 to 15 minutes, depending on the PSA.

On the New Ticket form, and in the portal's AI assistant, AI picks the request template from the client's description and fills in its fields. The client reviews the form and submits it. The template then sets the board, type and priority, so routing follows your rules rather than an AI guess. Technicians can also generate AI summaries of a ticket's history, which only your team sees.

Clients see the tickets you allow, whether that is their own, their location's or their whole company's. They see status, the assigned technician and public notes, and can reply and add attachments if their role allows it. Internal notes and worked hours stay hidden unless you choose to show hours. Users with parent access can switch between locations or see them all together.

Yes. The portal adapts to phone, tablet and desktop browsers. There is no separate mobile app. Clients can also open tickets from the Chrome extension, with screenshot capture, or from a Tickets tab in your branded Microsoft Teams app.

Yes. Templates support over 30 field types, required and conditional fields, instructional text, and embedded templates that create their own linked tickets. You can vary a template by client company, limit it to certain roles or industries, and import or export templates as JSON or CSV. AI can also draft a new template for you to edit and save.

Yes. Turn off PSA project sync and new projects live only in MSPortal, with phases, tasks, time entries and collaboration records. The setting applies to your whole portal rather than to each project, so while sync is on, new projects are created in your PSA.

Yes. Clients see the projects you allow in card, list, Kanban or schedule views. They read client-visible updates, milestones and deliverables, and respond to approvals, questions and decisions assigned to them. They cannot comment on updates. You control access by company, role, project type and per-item visibility.

Project AI reads the project's tickets, milestones, updates and decisions to answer questions and explain progress. It drafts weekly updates and proposes new milestones, deliverables, decisions and status changes. Each proposal appears as a card, and nothing saves until you select Apply. Client users can ask questions but cannot apply changes.

No. MCP tools read projects, project tickets and time entries. They can write updates, milestones, deliverables, action items, status, owners and priorities after a separate confirmation. Creating native projects, designing templates, and adding or deleting phases and tasks happen in the app.

The report builder has project blocks for health, task progress, timeline, costs, trends, completed tasks and weekly activity. Add a project to a meeting agenda and the card shows its health, milestone progress, next milestone and next client decision, including in presentation mode.

Yes. MSPortal syncs projects, project tickets and time entries from ConnectWise, HaloPSA and Autotask. Status, schedule dates and assignees write back to all three. Milestones, updates, decisions and deliverables stay in MSPortal.

Blocks cover tickets, devices and warranties, compliance and risk, Microsoft 365 licenses and Secure Score, backup, security tools such as Huntress and Avanan, training and security awareness, CSAT from surveys or HaloPSA and Autotask ratings, projects, goals, Planner and budgets. A block shows data only when the matching integration is connected and the reader can access that module. You can also add PDFs from other tools by emailing them to the company's import address.

Choose a template, the companies and a cadence, and MSPortal generates each run at the client's local time. Each run uses the data synced at that moment, which can trail the source tool by one sync cycle. With approval turned on, nothing is published or emailed until someone on your team approves the run.

Yes. Add the report to the meeting agenda and choose Present to walk through it as slides. After the meeting, the wrap-up step takes your transcript and drafts notes, action items and a summary email, which you review before it goes to the client.

Yes, through the logo block and card styling. The logo appears where you place the block, so check the layout and the exported PDF before sharing.

AI helps in two ways. The AI report builder turns a request such as "quarterly review with ticket trends, device health and the roadmap" into a page of blocks. Full reports go further, with AI writing the executive summary, KPIs, risks, recommendations and action plan from the data it was given, citing sources and listing data gaps. A generation review flags missing sections or citations it couldn't verify, and AI edits show the current and proposed text side by side before you apply them.

In the budget editor, the Planner Items and Strategic Goals panels list planned work for the budget's year. Select + to add an item's costs as budget lines, check them and save. Each line keeps its link to the Planner item. Later changes in Planner don't rewrite an approved budget.

After a budget is approved, the Actuals tab reads customer invoices synced from ConnectWise Manage, Autotask or HaloPSA for the budget's fiscal year. Invoices match to lines through linked projects, products or the reference on each line. Spend that doesn't match stays in Unallocated for your team to assign. The overall variance compares against all of the company's invoiced spend, so read a project-only budget line by line.

Yes. Clients with budget access see each line's cost, category and status, the monthly breakdown and, with invoice access, the Actuals tab. You choose which client roles can approve a budget.

The budget locks. Quantities, prices, categories and line statuses become read-only, and each line gets a reference for invoice matching. Approval can't be undone, so to revise the plan, duplicate the budget and work on the copy.

Open a goal and choose Add to Planner to prepare an item linked to it. Add costs and hours in Planner, then add the item to a budget from the budget editor. You review and save each step, so a change in one record doesn't quietly rewrite the others.

The timeline places each item in the month, quarter or year of its due date, and you can drag it to another period. Items with no due date wait in the Unscheduled panel. The list view is a table for search, filters and bulk updates. Both show the same items.

Yes, for items marked Visible to clients. Clients see the timeline, item details, costs, analytics and archived work for their company. Private notes stay internal. Items imported from a PSA are visible to clients by default, so check them after importing.

MSP staff can ask Planner AI questions such as which items are overdue or which work is highest value for a client. It can also draft a new item from a plain description, including the company, due date, cost and hours. The draft appears as a proposal and becomes a Planner item only when you apply it.

Planner, budgets with forecasting and actuals, goals, compliance with a risk register, reports and AI-written QBRs, meetings with presentation mode and wrap-up, and surveys. For your own team there are client health scores, a standards matrix and vCIO workload and pricing calculators.

Clients see the Planner items, budgets, goals, compliance results and published reports you share with them. Editing and approval need permissions you grant to the client's role, so a client can read the roadmap without being able to change it.

Clients book the review from a recurring booking link. You build the agenda from open tickets, Planner items and budgets, and generate the QBR report. AI writes the narrative from the data it's given and lists any gaps. Check the figures and sources, publish the report, then present from the meeting page.

Dedicated vCIO tools focus on the MSP's planning work. MSPortal puts the roadmap, budget and compliance work in the client portal, next to tickets, projects, invoices and documentation, so clients find it where they already go for IT help. Compare the integrations and client permissions you need before choosing.

AI drafts QBR and security review reports, Planner items, compliance checks and meeting summaries. vCIO Chat answers questions about a client and can propose a roadmap, or a QBR with its report and meeting. Each draft appears as a proposal that someone reviews and confirms before it's saved or shared.

Client Health uses eight dimensions: service, engagement, financial, sales, projects, standards, environment and operations. The published score depends on enabled metrics and evidence coverage; insufficient evidence can produce a Limited data result.

Financial Reporting combines supported PSA revenue, support activity and configured endpoint or seat counts. Period and model settings affect metrics and grades; missing evidence can withhold a grade. It does not measure net profit.

You define your standard tool stack with categories and required items. The compliance matrix shows which tools are deployed, in progress, or missing at each client. Gaps can be linked directly to Planner items so they become part of the IT roadmap.

MSP Tools is MSP-facing only. Client users cannot see it. Access is controlled through our role-based access control system, so you decide which team members can view health scores, financials, and tool stack data.

Available reporting sources include ticket, device, compliance, survey, usage and training records. Coverage and refresh timing depend on your connected integrations and configuration.

Client Health uses eight dimensions: service, engagement, financial, sales, projects, standards, environment and operations. The published score depends on enabled metrics and evidence coverage; insufficient evidence can produce a Limited data result.

Client users see the dashboards and metrics their permissions allow. Internal MSP health and financial views are separate; do not assume that a staff health score is published to clients.

MSPortal includes dashboards and reporting alongside its client portal. Compare the specific metrics, integrations, permissions and external dashboard requirements you need when evaluating BrightGauge or MSPbots.

Clients see the dashboards you share with their role, filtered to their company. Each widget also follows module permissions, so a client without device access won't see device widgets. Clients with access to several locations can view one location or several together.

Yes. Set a dashboard to Both or Internal (MSP Team), then choose the client roles that can open it. Tenant-wide exclusions can also keep generic submitters, chosen ticket types and recurring tickets out of ticket charts.

Widgets show the latest data MSPortal has synced from each integration, so a chart is as current as that integration's last sync. Each chart prints the date range it covers.

Yes, once you set up branding. Dashboards appear inside your portal, which uses your logo, colors and custom domain.

You choose which Pax8 and Sherweb products appear in the catalog and which ones to feature. Visibility applies to all your clients, not to each client separately. Prices come from the distributor, either Pax8's suggested retail price for that company or the customer price set in Sherweb. MSPortal does not apply its own markup, and your cost is shown only to staff allowed to see it.

A client picks a product or an existing subscription, enters the new total quantity and term, adds a note and submits. Your team places the order or changes the quantity with Pax8 or Sherweb, then marks the request fulfilled once the next sync shows the new quantity. A request does not change a subscription or assign licenses to users by itself.

Yes. The storefront uses the same logo, colors and custom domain as the rest of your portal. You set up branding and the domain once, and every module uses it.

Client requests wait for approval by an MSP manager or a member of the approver role you choose, and both get an in-app notification. For each subscription, you can let clients change seats within a set range without approval. Approval and fulfillment are separate steps, so an approved request still needs your team to place the order.

Hudu and IT Glue, with one connected per portal. MSPortal syncs documents, folders, assets, procedures or checklists, and password entries. With IT Glue it also syncs configurations. If you use Liongard, its inspector data appears in Documentation too. Content syncs on a schedule, and password values are fetched from Hudu or IT Glue each time someone reveals one.

Yes, but only what you share. You set visibility rules by folder, document, asset, procedure and password, for each client company and role. You can also limit your own team to shared items, so staff see what clients see.

No. MSPortal shows clients what you share from Hudu or IT Glue and adds pages and files you write in MSPortal. You still create and edit passwords, assets and provider documents in your documentation tool.

Global search matches keywords across tickets, devices, companies, projects, invoices and more. It includes Hudu or IT Glue documents, assets and procedures, plus password names for users allowed to see passwords. Pages and files written in MSPortal are found through the resource hub's search. Results only include what the user can access.

Password sharing stays off until you turn it on. Users need a separate password permission, and you share passwords by folder, category or entry. Values are fetched from Hudu or IT Glue at reveal time rather than stored in MSPortal, and each reveal is logged. If the log entry can't be written, the password isn't shown. One-time codes are never displayed.

Configure the company hierarchy and grant the intended users access through company permission groups. Users can then select accessible companies in supported views. Review each group’s company scope rather than assuming the hierarchy grants access automatically.

You can organize clients with multiple child companies. Confirm the required hierarchy and portfolio size during a walkthrough rather than relying on an unlimited-capacity claim.

Access follows configured roles and company permission groups. Grant only the companies a user should access; being associated with a parent or child company is not the complete access policy.

Supported company-scoped views include tickets, devices, compliance and other portal records. Available filters and aggregate views vary by page and integration.

Link each MSPortal company to the intended PSA company and configure portal company access separately. A parent-child relationship does not replace integration mappings or grant users access to every child company.

New client companies. Your MSP uses it to take a newly signed client through discovery, documents, agreements and setup. It isn't built for onboarding a client's new employees.

No. An invitation lets a contact confirm the invited email and enter an active onboarding workspace without first creating a regular portal account. Contacts who already have a portal account can also return through My onboarding after signing in.

Yes. Create a template once, then launch portals for any company from it. Each portal is an independent copy, so you can change tasks and dates for one client without affecting the template.

Describe your onboarding process. The designer proposes phases, tasks and settings, and you accept or reject each section before applying it to the template.

Credentials are encrypted when the client submits them. Only staff with onboarding settings access can reveal one, the submission and reveal are logged, and the stored value is deleted after the reveal. Ask us about key management for your security review.