# Read-only by default, a sane rule for connecting tools

Source: https://founder.nexxascreen.com/articles/read-only-by-default  
Updated: 2026-11-20  
Publisher: Sentient AI Inc

> Read-only by default means every new connection between tools, apps or AI assistants starts with permission to look but not to change anything. You widen access only when a specific job needs it, for a specific place. It limits damage from mistakes, leaked access and confused automations, and it costs little because most connections only need to read.

Read-only by default is a simple rule: every new connection, whether between two tools, from an app to your account, or from an AI assistant to your work, starts with permission to look and not to change anything. You widen access only when a specific job needs it, in a specific place. It limits the damage from mistakes, leaks and confused automations, and it costs little, because most connections only ever need to read.

## The key points

- Most connections only need to read. Start them that way.
- Allow changes for a specific job, in a specific place, not in general.
- Read-only limits the damage from mistakes and from leaked access.
- When a tool has no read-only option, be explicit about what the app does.
- Review connections regularly, and remove what you no longer use.

## Why it matters more now

A few years ago, a typical account had a handful of apps connected to their accounts. Now a small company might connect dozens: calendars to schedulers, chat to trackers, finance tools to accounting, and AI assistants to almost everything. Each connection that can write is one more thing that can break something.

When you run several companies, the connections multiply. Each company's tools, each client's workspace, each assistant you try.

## What can go wrong with write access

| Risk | What happens | How read-only helps |
|---|---|---|
| A mistake in an automation | It edits or deletes the wrong records | It cannot change anything |
| A leaked connection | Someone else acts as the app | They can see, but not change or send |
| A confused AI assistant | It acts on an instruction it should not have followed | It can only read and report |
| An app you forgot about | It keeps its access long after you stopped using it | The forgotten door only opens one way |
| An app that is sold or changes | New owners do things you did not expect | The scope of harm is smaller |

None of these risks disappear with read-only access. Seeing data you should not is still a problem. But they shrink, and the worst cases, such as deleted records or sent messages, mostly go away.

## Most connections only need to read

Look at what you connect apps for:

- Seeing your calendar to find a free slot.
- Gathering tasks or requests into one view.
- Summarising a week's activity.
- Answering questions about your work.
- Building reports and dashboards.

None of these need to write. The jobs that do need to write, such as creating an event, posting a message or updating a record, are fewer than they seem, and can be allowed one at a time.

## How to apply the rule

### When you connect something new

1. **Look for the read-only option first.** Many tools offer it on the permission screen, sometimes below the default.
2. **Choose the narrowest place.** One workspace, one calendar, one folder, rather than the whole account.
3. **Check who is asking.** The permission screen should name the app and where it will send you back to.

### When you need to allow changes

Widen access for a specific job, and keep it visible:

- Allow changes only where the job happens, such as one company or one project.
- Make sure every change is recorded with who made it and what it was before.
- Make sure you can undo it, or at least see exactly what to fix.
- Write down why you allowed it, so you can review it later.

### When a tool has no read-only option

Some tools only offer broader permissions. An app connecting to them has to ask for more than it needs. In that case, prefer apps that say so plainly, check that the app's own behaviour matches, and remove the connection as soon as you are done with it. Operators, for example, says on the card when a tool offers no read-only permission, as with GitHub and DocuSign, and only reads from them.

## Applying it to AI assistants

AI assistants are the newest and widest doors. An assistant connected to your work can read a great deal, and may be able to act on what it reads. Treat it like any other connection:

- **Start read only.** Ask it questions, have it summarise, check what it says.
- **Limit where it can look.** One company or one client at a time, not everything you have.
- **Allow changes for specific jobs**, such as adding items to one board, once you trust its output.
- **Make it ask before decisions.** Anything that commits money, people or reputation should come back to you for approval.

Operators applies this to assistants by letting you tick the companies each one may see, with none ticked to start, and a Read only switch on each that starts on. The articles on [delegating to AI agents](/articles/delegate-to-ai-agents) and [human-in-the-loop operations](/articles/human-in-the-loop-operations) go further.

## Review your connections

Once a quarter, look at the apps connected to each of your main accounts. Most tools have a page for this, often under security or connected apps. For each one, ask:

1. Do I still use it?
2. Does it need the access it has?
3. Could it do its job read only?

Remove what you do not use. Narrow what you can. It usually takes half an hour per company, and it is one of the cheapest security improvements you can make.

## The trade-off

Read-only by default means a little more friction when you genuinely need an app to act. You will occasionally connect something, find it cannot do what you hoped, and come back to widen it. That small cost buys a lot: fewer surprises, smaller mistakes and a clear record of who can do what.

## What to do next

- [How to delegate to AI agents without losing control](/articles/delegate-to-ai-agents)
- [What Operators stores, and what it never does](/guides/what-operators-stores)
- [How to let an agent work for you safely](/guides/let-agents-work-safely)

## Questions

### What does read-only access mean for a connected app?

The app can see the information you allow, but cannot create, change, send or delete anything in your account. It is the narrowest useful permission most tools offer.

### What if a tool does not offer read-only access?

Some tools only offer broader permissions. In that case, check what the app actually does with them, prefer apps that say plainly what they use, and remove the connection when you stop needing it.

### When should I allow an app to make changes?

When a specific job needs it, in a specific place, and you can see and undo what it changes. Allow it for that job, not for everything the app could do.

### Does read-only make AI assistants useless?

No. Reading, summarising and answering questions are most of what people use assistants for. Changes can be added later for the jobs that need them.
