--- title: "MSP AI rules: data, approvals, and spend" description: "Define MSP AI rules for client records, credentials, healthcare data, change and message approvals, and enforced budgets for each service-desk function" canonical: "https://scalewithsearch.com/articles/msp-ai-rules-data-approvals-spend" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # MSP AI rules: data, approvals, and spend Write MSP AI rules at the client boundary. A shared service desk can use common procedures while keeping each client's assets, tickets, incidents, and outputs separate. Give every preparation function an explicit client scope and a defined stopping point. Begin with the [IT provider hub](/for/it-and-managed-service-providers). Choose one read-only preparation job. Keep credentials, remote sessions, production commands, and client messages outside its initial capabilities. Add operational effects only through their own reviewed scope and authority. The controls below are proposed business rules. The cited guidance supports particular security and healthcare boundaries. Establish the applicable legal and contractual requirements for each actual client before processing its records. ## Separate shared instructions from client data Keep the generic service catalog, accepted templates, and common review rules in a controlled shared library. Keep tenant-specific configuration, contract terms, contacts, incidents, and tickets in client-restricted sources. Set permissions at retrieval and storage, rather than relying on text asking the model to be careful. | Record | Proposed AI boundary | |---|---| | Shared procedure | Permit the current approved revision | | Client service agreement | Restrict to the named client's function | | Ticket or incident extract | Minimize to the facts needed for the output | | Security findings and configuration records | Require a purpose-specific reviewer and destination | | Passwords, private keys, tokens, and recovery codes | Exclude from model inputs, outputs, and ordinary logs | | Regulated client records | Hold until the applicable handling route is accepted | Enforce the client identifier before reading sources. Reject a mismatch among the ticket, source set, and output destination. Keep the original record available for an authorized reviewer without placing the whole archive in each run. The FTC recommends limiting sensitive information to legitimate business needs. [FTC data-handling guidance, checked 2026.10.26](https://www.ftc.gov/business-guidance/resources/protecting-personal-information-guide-business). ## Keep security responsibility visible in the agreement CISA's joint MSP advisory recommends that contracts identify ownership of security roles and responsibilities. It also recommends multifactor authentication for MSP accounts accessing customer environments. [CISA AA22-131A, May 11, 2022, checked 2026.10.26](https://www.cisa.gov/news-events/cybersecurity-advisories/aa22-131a). Use the accepted agreement to determine which records the function can read and which decisions need client approval. Do not infer authority from a technician having used an account previously. Keep the service boundary current when the commercial scope changes. For the preparation function, remove production capabilities from the account entirely. Give it a restricted source connector and draft destination. Keep credential retrieval and operational execution in the established controlled systems. Review access when a user, client, service, or connector changes. A new client's onboarding should not make its archive readable by every existing function. Test denied access and verify that it produces a blocked receipt rather than a wider search. ## Review healthcare processing as a separate boundary HHS states that a cloud service provider creating, receiving, maintaining, or transmitting electronic protected health information on behalf of a covered entity or business associate is itself a business associate. This can apply even without an encryption key. [HHS cloud computing guidance, checked 2026.10.26](https://www.hhs.gov/hipaa/for-professionals/special-topics/health-information-technology/cloud-computing/index.html). The same guidance describes the required business associate agreement for that arrangement. Do not treat encryption, an IT support label, or a vendor's general assurance as the completed review. Establish the applicable agreement, safeguards, permitted use, and subcontractor route before processing that information. HHS also lists MSP support services requiring creation, receipt, maintenance, or transmission of electronic protected health information as a business-associate example. [HHS business associate guidance, checked 2026.10.26](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/business-associates/index.html). Use fictional or approved non-sensitive examples until the route is accepted. An ordinary ticket export can contain copied health information in its body or attachment. Check the actual content before it enters an AI preparation service. ## Keep payment material out of support drafts If a ticket concerns billing, provide the invoice reference and approved status needed for the task. Keep card details and payment collection in their authorized system. Do not use an AI draft as a place to preserve security codes received from a caller. PCI SSC prohibits storage of card verification codes after authorization. [PCI SSC FAQ 1280, checked 2026.10.26](https://www.pcisecuritystandards.org/faqs/1280/). Define how staff handle accidentally received credentials or payment material. Include the prompt, processing logs, temporary extraction files, and saved outputs in the review. Removing a secret from the final draft does not establish that it was absent from those other locations. Keep any required incident assessment with the responsible security and privacy people. The function should preserve references and stop further processing while they decide the response. ## Approve changes and communications separately A ticket brief can prepare a decision. It cannot provide its own authorization for the resulting action. Keep the person who validates evidence identifiable alongside the person who approves an operational effect. | Output or effect | Proposed review owner | |---|---| | Ticket evidence brief | Assigned technician checks sources and uncertainty | | Security-related summary | Security lead reviews classification and disclosure | | Change review packet | Change owner checks scope, prerequisites, and rollback evidence | | Production action | Named approvers authorize exact client, system, action, and window | | Client incident update | Incident lead checks facts; communication owner approves recipients and text | | Public statement | Authorized publisher checks disclosure and supported claims | Bind approval to the client, source versions, exact action, recipient, attachments, and output version. Changed commands, targets, scope, or timing need review again. Put the check in the executing system so a model cannot grant itself permission in prose. The [public status-page guide](/articles/msp-public-status-page-website) covers publication. Keep private incident findings in their approved client channel even when a public update is due. ## Cap spend without weakening client boundaries Give ticket preparation, onboarding review, and reporting separate monthly limits. Track client allocation inside those limits where needed. A larger budget should not widen the permitted source set or enable another tenant's retrieval. Set maximum document size, tickets per run, output size, and attempts. Reserve the permitted maximum before starting. Reconcile actual charges afterward. Coordinate reservations across concurrent jobs so each cannot spend the same remaining balance. Alert the budget owner before the enforced limit. At the limit, stop paid calls and write a blocked result. Keep the ordinary service process available for pending work. Count failed calls, rejected drafts, and any permitted additional processing in the measured total. Each receipt should contain function, client reference, sources, model, attempts, output location, approval state, and cost. Mark delayed cost data pending until reconciled. Keep secret values and detailed incident content out of routine spend reports. ## Prove isolation and review before acceptance Use two fictional clients with distinct harmless facts. Test ordinary retrieval, a wrong-client record, a swapped output destination, and a source document asking for broader access. Confirm that the boundary holds before and after changing models or connectors. Also test missing rollback evidence, an unapproved client recipient, a rejected draft, and budget exhaustion. Rehearse stopping the function and handing pending work to staff. Save the accepted rules and results in records the MSP controls. Ask a technician outside the build to follow the runbook, find the current source permissions, inspect one cost receipt, and reject an output. Resolve any dependence on unwritten instructions before accepting the handoff. ## Rehearse a client-specific change boundary Use a fictional change request for one client with a valid scope reference and missing rollback evidence. The preparation packet should identify the missing evidence and stay pending. It should not borrow a rollback procedure from another tenant because the device names look similar. Next, provide the accepted evidence and obtain a test approval. Change the target system after that approval. Confirm that the executing path rejects the changed action. Record the client, request version, target, and review state without including credentials. This exercise checks the boundary between a useful packet and permission to operate. [AI systems](/ai-systems) describes the owned-record and review method. Bring Scale With Search one MSP function through the [written scope form](/work), with client scope, approval owners, and forbidden data classes named. Continue the website review: [AI-native IT providers: the first functions to build](/articles/ai-native-managed-service-providers-first-functions); [Managed IT pricing pages: explain what sets the quote](/articles/managed-it-pricing-website-page); [MSP case studies: publish evidence without client names](/articles/msp-anonymous-case-study-website); [MSP onboarding pages: explain the first steps](/articles/msp-client-onboarding-website-page); [MSP contact form spam: inspect the receiving path](/articles/msp-contact-form-spam-controls); [MSP cybersecurity website claims: show the scope](/articles/msp-cybersecurity-website-claims); [Google Business Profile for an MSP: check eligibility](/articles/msp-google-business-profile-eligibility); [MSP service area pages: separate on-site and remote](/articles/msp-onsite-service-area-website-pages); [MSP status pages: publish approved incident updates](/articles/msp-public-status-page-website); [MSP buyer guides: make the download useful](/articles/msp-website-buyer-guide-download); [MSP inquiry emails missing: trace the delivery steps](/articles/msp-website-inquiry-email-not-arriving); [MSP website design: separate sales from support](/articles/msp-website-sales-and-support-paths). [IT and managed service providers](/for/it-and-managed-service-providers): website and search resources. ## Related: IT and managed service providers - [MSP case studies: publish evidence without client names](/articles/msp-anonymous-case-study-website) - [MSP onboarding pages: explain the first steps](/articles/msp-client-onboarding-website-page) - [MSP contact form spam: inspect the receiving path](/articles/msp-contact-form-spam-controls) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```