--- title: "Keep businesses and clients separate in AI work" description: "Review AI boundaries across your businesses and clients, from selecting the right record to checking approvals, shared reports, staff access, and handoff." canonical: "https://scalewithsearch.com/articles/ai-client-boundaries-owner-review" --- ## 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) # How do I keep businesses and clients separate in AI work? Require each AI job to identify its business, client, source record, output destination, and approval owner before work begins. Enforce those choices in access controls. Review the boundary again before sharing or acting on the result. This article gives an owner a way to review those boundaries across daily work and staff changes. The implementation guide to [separating business contexts for AI agents](/articles/separate-business-contexts-ai-agents) covers the technical controls. Use the review here to ask whether those controls match how your company works. Consider an illustrative firm preparing reports for two clients. Both use the same report structure. One has private delivery terms. The shared format can remain available to both jobs. The private terms should appear only in the job authorized to use them. ## Review the moment a job is selected Ask someone to start a sample job and explain how they selected the client. Require an unambiguous identifier and an approved relationship between that client and the business doing the work. Do not accept the last open conversation as the selection method. If a request says to update the report but names no client, the job should stop for a resolved identity. It should not search every client folder to guess the intended account. Look at how similar names are handled. Create test clients with nearly identical names and different identifiers. Ask the job to prepare one client's report. Confirm that the chosen sources and output path belong to that identifier. Record the result as a test of that selection path. Repeat it when intake, client naming, or account routing changes. A passing test for one entry point does not cover a separate inbox or imported job queue automatically. ## Check access before checking the prose A polished output does not show whether the job retrieved another client's private file. Ask for evidence of allowed and denied access. Inspect which records the job could read before reviewing its summary. OWASP recommends checking tenant authorization across resource access paths, including work handled asynchronously. Ask your builder to demonstrate the equivalent boundary for your client jobs. [OWASP Multi Tenant Security Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Multi_Tenant_Security_Cheat_Sheet.html), checked 2026.10.26. For an owner review, use harmless test records. Put a distinctive invented phrase in a second client's restricted material. Attempt to request it through the first client's job. Require denial at retrieval, and inspect the output and receipt for unintended exposure. Keep these test records separate from live customer material. Have the builder explain which controls deny the request. A prompt telling the model to keep clients separate should not be the only answer. ## Share the method with a defined update process Use the [client data memory guide](/articles/client-data-in-ai-agent-memory) to decide which private material belongs in each permitted record. Review what is inside your common templates. A reusable method can describe report sections, writing rules, and checks. Remove private customer examples and client-specific prices before making it shared material. For each shared method, name the person who can approve updates. When the report format changes, test it with each affected client configuration. A client may require an extra review step or prohibit a certain field. Keep company and client corrections in their proper scope. If one client changes its terminology, update that client's record. Do not convert its preference into a global rule without a separate decision. This is also a training question. Ask a new user where they would save a correction. They should be able to distinguish a shared method change from a private client fact without asking the model to decide ownership. ## Carry the boundary into the approval screen Ask the reviewer to open the exact proposed action. The review should show the selected business, selected client, sending account, destination, and final artifact. Approval should refer to that combination. Then change one field in a safe test. Replace the destination or choose another sending account. Confirm that the prior approval no longer authorizes the changed action. Test the check where the action executes. For a firm working on a client's behalf, record the client's authority as well as your staff role. Your employee's ability to prepare a draft does not establish permission to send it from a client account. The guide to [who approves what an AI agent sends](/articles/who-approves-what-an-ai-agent-sends) provides the action-level design. Keep the owner's review focused on whether the real people and accounts match that design. ## Review summaries, receipts, and shared views Source boundaries should extend to the places where people inspect results. Review a staff dashboard, its exported report, and its run receipts using a client-limited test role. Ask which details the role can see. A failure message may reveal a source title or customer identifier. A portfolio summary may include an issue that belongs only to one client. Define what each audience is allowed to receive. For shared management reports, choose a small set of approved fields. Show the period, source status, and responsible person. Keep private source references behind their own permission check when the audience should not open them. Test a downloaded report as well as the live view. Identify where exported files are stored and who can retrieve them. Apply your handling rules there before treating the shared view as accepted. ## Make staff changes a boundary review trigger Write down what happens when someone joins a team, changes role, or leaves. Name the person responsible for approving access changes. Keep a record of the permissions granted or removed. In an illustrative role change, an account manager moves from Client North to Client South. Test whether North's sources, stored drafts, and receipts remain accessible through the old role. Remove access your policy no longer permits before assigning routine South work. Check scheduled jobs separately. A function may run under a service account rather than the departing person's account. Record who now owns the job, who receives its alerts, and which client permissions remain necessary. Do not hand an incoming employee a previous user's entire chat history as the default training package. Prepare a role-appropriate record with approved instructions and current facts. Review any private material before including it. ## Plan client exits before they become urgent Define the handoff package while the client is active. List the client's owned files, functions, runbooks, acceptance examples, account references, and relevant receipts. Specify any shared material the client is entitled to keep. Keep retention and access removal as separate decisions. A retained business record does not need to remain accessible to every former worker. A closed account does not prove every copy has been handled under your policy. Before an authorized handoff, test that the package contains the selected client's material and excludes other clients. Ask the receiving person to locate the current instructions and explain the job's stopping conditions. Also identify schedules and connections that must change at the end of service. Put those actions through their own approval process. A prepared handoff checklist is not permission to delete data or disable a live account. ## Keep the owner's review small enough to repeat Choose one client job and follow it from intake to receipt. Note the selected identity, permitted records, proposed action, approval evidence, and final destination. Include one denied request and one changed-role test. Record the exceptions and the person responsible for resolving each one. Repeat the review after a change to access, source storage, client scope, or action permissions. Keep the prior result so the team can compare what changed. The [AI systems method](/ai-systems) builds one function at a time on a business-owned record, then trains the people running it. For firms serving clients, apply that method inside each client's agreed boundary. [Send your brief](/work#send-your-brief) with the first client job, its required sources, and the approval boundary you need to verify. ## Related: Agent Governance - [How to Keep Businesses, Clients, and Roles Separate for AI Agents](/articles/separate-business-contexts-ai-agents) - [What Client Data Belongs in AI Agent Memory?](/articles/client-data-in-ai-agent-memory) - [Who Approves What an AI Agent Sends?](/articles/who-approves-what-an-ai-agent-sends) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```