Most teams underuse Einstein Platform because they enter through one specific feature page and never explore the rest of the tree. Spending an hour walking the full tree once per release catches features that ship without marketing fanfare and would otherwise sit unused.
- Open Setup, Einstein Platform, and walk the tree
Click into every node. Note which features are enabled, disabled, or unavailable for your edition. The walk takes 30 to 45 minutes and produces a written inventory of what is in scope.
- Confirm Trust Layer settings
Open the Einstein Trust Layer node. Verify PII masking matches the data types your org handles, data residency matches your region requirements, and audit logging is enabled. These are org-wide settings; getting them right matters once, not per feature.
- Audit existing per-feature configuration
For each enabled feature, open its configuration page. Confirm settings are current, fields are still relevant, and the feature owner is still on the team. Features whose owner has left often run on stale config.
- Sample the Einstein Activity log
Pull a week of the Activity log. Confirm prompts and responses look sensible, masking applied where expected, no unexpected feature firing high-volume calls. Build the weekly sampling habit before it becomes urgent.
- Pair with Einstein Setup for new feature discovery
Einstein Setup suggests features to enable based on org data. Run through the wizard quarterly to surface candidates you might miss in the per-feature Platform tree.
- Document the Einstein feature inventory
Write the inventory down. Owner, enabled date, last review date per feature. The document is the registry that prevents features accumulating without anyone responsible for them.
- Schedule a quarterly platform review
Quarterly, walk the tree again, sample the log, update the inventory, retire features no one uses. The cadence is the discipline that keeps the Platform area from becoming a graveyard.
Which Einstein features are toggled on for the org. Drives licensing and Trust Layer scope.
Org-wide PII masking, residency, and audit logging settings. Apply to every Einstein feature.
Granular access control per feature (Einstein Case Classification, NBA, Agentforce Builder).
How much detail (prompt content, masking applied) the log captures per call. Verbose for development, summary for production.
Team-maintained registry of enabled features, owners, and review dates. The discipline that prevents accumulation.
- Features ship per release without big marketing pushes. Walking the Platform tree quarterly is the only reliable way to know what is available without missing capabilities.
- Trust Layer settings are org-wide. Changing them affects every Einstein feature. Coordinate before tweaking.
- Per-feature permission sets are easy to misconfigure. Run an audit of who has Einstein Admin and remove broad access from anyone who only needs one feature.
- The Einstein Activity log fills quickly on high-volume features. Set retention policy explicitly rather than letting it become a multi-year compliance footprint.
- Features whose owner has left the team continue to run on stale config. The inventory document is the discipline that catches them.