Guide Library

BOSG-52Notion Business OSFree to read

Using Business OS Responsibly: Data, AI and Your Responsibilities

Summary

Practical guidance for using Business OS with real business and personal data. Covers the adopting business's responsibility for data, permissions, connected services, backups, AI review, client visibility and incident response, with a clear boundary between operational guidance and the separate legal terms.

v1 · Updated 16 Nov 2026

Summary. The Business OS Templated System helps you organise and act on business information. However you use it, you stay responsible for the data you add, the permissions you set, how it is configured, the services you connect and the decisions you make from its output. That applies to both the business that owns the workspace and the people working inside it — some responsibilities sit with the business (lawful basis, retention, who may access what), others with whoever is adding data or running an agent day to day. Start with ordinary information, grant the smallest useful access, and keep a person in control of anything that matters.

When to use this guide. Read it before you add real business, client, employee or personal data; when you decide what a teammate, guest, agent or connection may access; when you enable AI-assisted work; or when you review backups, retention and what happens if information is shared incorrectly.

Questions this guide answers. What am I responsible for? What data should I add, and what should stay out? Who should be able to see it? How do I check AI-generated work? What do I need to test and back up? What should happen if something goes wrong?

Practical guidance, not the contract. This guide explains how to operate Business OS responsibly. Using Business OS is subject to the separate Terms of Use, Licence and Disclaimer, published at app.agenticbusinessmethod.com/library/business-os-terms-of-use. Neither page replaces advice from a qualified legal, privacy, security, tax or financial professional. The approaches across the Business OS guides are our recommendations — how we build and run these systems ourselves, and what we have found works. Treat them as a considered point of view, not rules or guarantees. Take what fits, adapt what does not, and make your own call: you know your business, your clients and your risk better than any guide can.


The one question that matters

Before you put anything into Business OS, the useful question is not "Can Notion hold this?" It is "Do I have a good reason, the right permission, and a safe setup for putting it here?" Most of this guide is just that question, applied to data, access, AI and connections. A few things follow from it:

  • AI output is a draft until a person checks it.
  • Read-only access can still expose sensitive information inside an answer.
  • Connecting a service does not remove your need to check that provider's terms, permissions and data handling.
  • Important information needs an owner, a backup or recovery route, and a point at which it gets reviewed.
  • Passwords, API keys, tokens and recovery codes do not belong in ordinary Notion pages.
  • Business OS cannot certify that your business is compliant, secure or protected from loss. That part is yours.

Before you add real data

Start with sample or low-risk information while you learn the system. Add real client, employee, financial or commercially sensitive information only once the access and responsibility decisions have been made. For each source, ask:

  1. Who owns the information?
  2. Why does the business need it in Business OS?
  3. Is the business authorised to store and use it?
  4. Who should be able to see or change it?
  5. Does an agent or connection need access?
  6. How long should it be kept?
  7. What happens when it is wrong, out of date or no longer needed?
  8. How would you recover it if the workspace or connection were unavailable? If any of those questions has no clear owner, pause before you import or connect the source.

Who is responsible for what

Better Creating supplies the template, guides and examples. Notion supplies the platform. Connected services supply their own systems. You run the live setup — so the day-to-day responsibility sits with you and your business, not with us. That means your business stays responsible for:

  • workspace and teamspace structure;
  • members, guests and public links;
  • page, database and agent permissions;
  • lawful use of client, employee and personal information;
  • retention, deletion and backups;
  • assessing vendors and connections;
  • testing formulas, imports, automations and agents;
  • training the people who use it, and the way they work;
  • checking AI output; and
  • the decisions and actions taken from the system. A supplied default is a starting point. It cannot know your contracts, jurisdiction, industry rules, insurance terms or risk tolerance. One point worth stating plainly: if you put personal data into your workspace — client contacts, employee records, anything that identifies a living person — your business is responsible for it under data-protection law. In most cases you are the "data controller" (the one who decides why and how the data is used), and Notion and any connected service are your "processors" (they handle it on your behalf). Business OS does not take that responsibility on for you, and using it does not make you compliant. If you are not sure what that means for your business, treat it as one of the "ask a qualified person" points at the end of this guide.

Decide what belongs in the workspace

Sort information into one of these before you capture it.

Ordinary internal information

Project plans, internal meeting notes, general SOPs and non-sensitive reference material. These can normally be handled with standard workspace permissions and a named owner.

Confidential business or client information

Unpublished commercial plans, client delivery material, pricing, contracts and private correspondence. Limit access to the people and agents involved in the work. Check client visibility before you relate anything to a Client Portal.

Personal or employment information

Contact details, performance notes, absence information and recruitment material. Store only what the business is authorised to keep and needs to keep. Restrict access and agree retention with the right owner.

Regulated or highly sensitive information

Health information, identity documents, payment-card data, detailed financial records, or anything covered by a regulated-client agreement. Do not add it until the business has assessed the legal, contractual and security requirements.

Secrets and credentials

Passwords, API keys, bearer tokens, licence keys, recovery codes and private encryption keys do not go in ordinary pages. Use the authentication screen for a connection, or an approved secrets-management tool.

If you do not know which category applies, stop and ask the data owner, your workspace admin, or a qualified privacy or security adviser before you add it.

Grant the smallest useful access

Give each person and agent the access the job needs, not access that might be useful one day.

  • Use groups and specific pages where you can.
  • Add clients as guests only to the pages meant for them.
  • Select the exact databases, folders, calendars or Slack channels a Custom Agent needs.
  • Start connections and agents with view access.
  • Add edit access only when the job has a named destination and a tested result.
  • Keep external messages, publishing, deletion, payments and permission changes behind a human check.
  • Review access when someone changes role, leaves, or no longer owns the work. A dashboard or linked view displays information. It is not automatically a security boundary. Test the experience as the intended member, guest or agent rather than assuming a filtered view is enough.

Use AI as checked assistance

AI is a fast assistant, not a decision-maker. It drafts, retrieves, compares, structures and spots patterns well. It will also invent facts, miss context, and follow the wrong source with complete confidence. You are the one in charge — treat every result as a draft until someone who knows the answer has checked it. Match the check to the cost of being wrong.

Low consequence

Brainstorming, formatting, internal summaries and reversible draft work can move quickly. Check names, figures, links and source claims before you reuse them.

Business consequence

Client work, project commitments, pricing, reports, policy changes and operational recommendations need review by the person who owns that area.

Human, legal or financial consequence

Contracts, employment, tax, payments, access decisions, legal claims and sensitive client matters stay with a qualified person. AI can help organise the material, but it does not make or approve the decision. One successful run is not proof that an agent is safe to run unattended. Test:

  • a normal case;
  • incomplete input;
  • a request outside the intended boundary;
  • a duplicate-sensitive case; and
  • what happens when the source or connection fails. Add schedules and event triggers only after the manual route works.

Check connected services

Email, calendar, Slack, Google Drive, CRMs and custom MCP servers stay separate services, with their own permissions and terms. Before you connect one:

  • verify the provider and the official connection route;
  • identify which account authenticates it;
  • check what data and actions the connection exposes;
  • enable only the tools the job needs;
  • keep write confirmation on where you can;
  • record the owner and the fallback; and
  • read the provider's current privacy, security and retention information. A connection being technically available does not mean your business should enable it.

Keep one source of truth, and keep it current

Decide which system owns each piece of maintained information. Use the Context Map to tell agents where it lives, and the Business Wiki to give people a reliable signpost. Do not keep two editable copies of a policy, SOP or client record just because one is easier for an agent to search. Old information can mislead as badly as missing information, so give important policies, SOPs and shared guidance a named owner, a status, a review date or change trigger, a canonical source, and a route for resolving conflicts. When something changes, update the human source first. Then review the guides, skills, automations and agents that depend on it. Use Bring Your Business Context into Business OS: Import, Migrate and Seed (BOSG-47) before moving business information, and Guide: Company knowledge and specialist knowledge architecture (BOSG-30) when deciding where maintained knowledge belongs.

Backups and recovery

Notion is the operating surface, but you decide how you will recover information you cannot afford to lose. For important sources and workflows:

  • identify the canonical system;
  • choose an export, backup or retained-source approach;
  • record who owns recovery;
  • keep the previous source available during a migration;
  • write down what happens when Notion or a connection is unavailable; and
  • test recovery rather than assuming an export is usable. A backup is only useful if you know where it is, who can reach it, and how to restore it.

If something is shared incorrectly

Act quickly, and keep a record of what happened.

  1. Stop the trigger, agent or connection involved.
  2. Remove the incorrect share, public link, portal relation or permission.
  3. Work out what information was exposed and who could see it.
  4. Tell the workspace owner and the person responsible for the data.
  5. Keep the relevant audit information rather than deleting the evidence.
  6. Follow your business's incident, client-notification and legal-review process.
  7. Fix the source rule, permission or workflow before you switch it back on. Business OS does not replace an incident-response plan. If your business handles client, employee or regulated information, agree that route before an incident happens, not during one.

A practical pre-flight check

Before a new import, connection, Custom Agent or client-facing workflow goes live:

  • The job and its owner are named.
  • The canonical source is clear.
  • The business is authorised to use the information.
  • Access is limited to the intended people and agents.
  • Secrets and unnecessary sensitive data are excluded.
  • AI output has a named human reviewer.
  • Normal, incomplete, boundary and duplicate cases have been tested.
  • The experience has been checked as the intended member or guest.
  • A backup or fallback exists where the information matters.
  • The review trigger and incident route are recorded.

When to ask for qualified help

Ask a qualified professional when the decision depends on:

  • privacy law or lawful basis;
  • employment or HR records;
  • tax, accounting or financial regulation;
  • contractual confidentiality;
  • regulated or special-category data;
  • cybersecurity design or incident response;
  • cross-border data handling; or
  • enforceable terms, warranties or liability limits. A template can organise these decisions. It cannot make them safe or lawful for your business.

Next useful action

Before you add the next real source, ask your agent:

Help me run the responsible-use pre-flight check for this information or connection. Identify the owner, source, audience, permission boundary, AI review point, backup or fallback and incident route. Do not import, connect or share anything until I approve the plan.

v1 · Updated 16 Nov 2026
This page always shows the current version. Members of the Agentic Business Community can also ask their own AI about it, through the Agentic Business Guide MCP.