Isolation for restricted records

Shivanath Devinarayanan · Updated

On this page

Compensation, budget, and similar records: session isolation, on-behalf-of Salesforce permission sets, a human on the review line. Some jobs stay no-screen. Some stay with a person. No agent nicknames.

Row-level policy exists before a Slack demo of a restricted worker. That family is on four policy families . On-behalf-of hops are on identity . The reviewer is named on owners .

Separate session, OBO, review

Restricted records get their own session box. The hop into Salesforce uses permission sets for that named person. A named reviewer sits on the line. CIBA is the out-of-band approval path when the action is sensitive enough to leave the channel.

Some work should never get a screen in front of an agent. Some work should stay with a person even when the rest of the fleet is digital labor. That is an operating choice, not a model upgrade. The governance hub is governance .

How to hire

Hiring starts with a governed production agent on one documented job, then a consultation.

Start at stand up production AI agents , then book a consultation . These pages are the operating model. The nine services remain the paid catalog.

SHIVANATH DEVINARAYANAN · SALESFORCE MVP HALL OF FAME ·

SD

SHIVANATH DEVINARAYANAN · SALESFORCE MVP HALL OF FAME ·

SD

Stand up the first production agent

Hiring starts with a governed production agent on one documented job, then a consultation.

Also in this file: Home · About · Services · Portfolio · Success Stories · Writing · Events · Contact · Media kit · Privacy Policy