The interface moved. The permissions did not.

For twenty years, doing anything in a CRM meant opening the CRM. On September 16, Salesforce announced it is letting that go. For deciding which work to hand to AI in the first place, see What to hand to AI first.

The company unveiled AIforce, a layer that brings Salesforce’s data, workflows, business logic and permissions into other AI tools and chat interfaces, so people and agents can use it without opening the Salesforce screen. It launches with three front doors: Claudeforce, which puts Salesforce inside Claude; Slackforce, inside Slack; and Agentforce Coworker. Salesforce says every request runs inside the customer’s existing permissions and business rules, and that business data is not retained by the model providers. It also says 100,000 people activated Agentforce Coworker in its first 35 days, a figure from the company’s own release.

The interface moved

This is a big company admitting something small companies have felt for a while: the place where work starts has changed. People now start in a chat window, an assistant, or an agent that is already open. The system of record is becoming a service that answers those tools, rather than a screen everyone has to visit.

For a business of one, that is good news. You do not need a department that lives inside the CRM. You need your records to answer the tools you already use.

The permissions did not

The part of the announcement worth copying is the boring part. Every request respects the access controls that already exist, and every action goes through the same governance. The interface got flexible. The rules stayed put.

That is the design principle for a lean company too:

• One source of truth per kind of record. Clients live in one place. Money lives in one place. Let every tool read from it instead of keeping its own copy.
• Agents get the smallest access that does the job. An agent that drafts follow-ups can read contacts and write notes. It does not need to delete deals.
• Every write leaves a trail. When an agent changes a record, you can see what changed, when, and why.

What to do this week

1. List the three places your business keeps records: clients, money, and work in progress.
2. For each one, write down which tools and agents can read it and which can change it.
3. Take away any write access an agent does not need.

When the next interface arrives, and it will, your business plugs it in without rebuilding anything. The records answer the new tool, and the rules come along with them.