Salesforce's named agents are only as safe as your permissions
Rebecca Wettemann's read on Salesforce's named agent roster turns on one condition an admin can test, that permissions are correct today.
Topic coverage
Identity
Source-linked reporting and practical patterns organized around a shared enterprise applications question.
Latest reading
Oracle Health outsources identity proofing to ID.me
An Oracle press release pairs undated patient intake with prescriber credentialing that ships now. The reusable credential model is the part worth copying.
ServiceNow's kill switch reaches into Okta, GCP and AWS
ServiceNow's new agent kill switch orchestrates credential revocation across Okta, GCP and AWS. What the post does not say matters more.
Analysis and architecture
Designing a Salesforce sharing model that still scales
Salesforce sharing only ever adds access, and the platform stores the result. How to set the baseline, the hierarchy and the rules so growth stays affordable.
Dataverse security that survives ten times the size
Business units, depth, teams and sharing decide whether a Dataverse security model survives growth. How to design each one so it still makes sense later.
Movers break the identity lifecycle across business apps
Provisioning is the easy part. Transfers add access and almost never remove it, and every application keeps entitlement in a model of its own.
Power Pages identity decisions that are hard to undo
A Power Pages site authenticates against an identity provider and authorises against a Dataverse contact. Matching the two on email is the mistake that lasts.
Service accounts are the least governed identity you run
Integration accounts miss every joiner and leaver process. Give each one a named owner, a readable name, narrow scopes and a rehearsed rotation.
Identity architecture when you run two Salesforce orgs
When a company runs more than one Salesforce org, single sign on is the easy part. The gap audits find sits in deprovisioning across two login domains.
Give every Dataverse access exception an owner and an expiry
Access exceptions in Dataverse and ServiceNow outlive their reason. Give each one a named owner, an end date, and a record small enough to review.
When a Workday change completes and nobody owns the fix
A Power Automate flow can report success on a Workday employee event while the team that gets the ticket cannot see what arrived or how to correct it.
AI agents need a pause button someone can actually reach
A pause control with an owner, a written reason, and a resume record should be an ordinary operating control for Copilot Studio and ServiceNow agents.
Related guides
Power BI row-level security for Dataverse data
A Power BI import carries everything the refresh account could read. Rebuild the row filters, maintain the mapping table, and test as a restricted user.
Segregation of duties when the team is too small
When finance is too small to split creating a vendor from paying one, pick the two conflicts that carry the money and mitigate them in writing.
How to keep a ServiceNow access catalog honest
A practical method for keeping ServiceNow access requests auditable long after the project that justified them ends.
The Workday security group cleanup no one owns
A first-person audit method for finding duplicate Workday security groups, tracing mystery access back to its origin, and setting a review cadence that sticks.