A dashboard earns its keep where the work happens. Any Insights chart or dashboard can be rendered inside Salesforce — on a record page, an app page, or a home page — using the OrgAdmin Insight Lightning component. On a record page it filters itself to the record being viewed, so one dashboard serves every account, every opportunity, every case.
It travels between orgs, too. Switch embedding on once and the dashboard becomes a template: place it in a sandbox and it shows sandbox numbers, place the same one in production and it shows production numbers. The dashboard supplies the questions; each org answers them with its own data.
Set an org up once
Four steps, in this order. You only do them once per connected org — after that, embedding any further dashboard is a single switch.
- 1
Turn embedding on for the dashboard
Open the dashboard, click Embed, and switch on Allow embedding. Nothing is shared until you do this, and it is deliberately a person's decision — the AI that builds dashboards has no way to flip it. - 2
Deploy the component to your org
In the same panel, choose Add package to Development Studio. That creates a project holding an Apex class, the Lightning component, a custom setting, and a Trusted URL. Review it, then deploy it the usual way — see Development Studio. Deploying to a production org must run the test classOrgAdminEmbedControllerTest, so pick Run specified tests and name it. - 3
Create an embed key
On the org's settings page, under Salesforce embedding, create a key. The secret is shown once and never again — copy it before you close the page. - 4
Tell Salesforce where to look
In Salesforce Setup, go to Custom Settings → OrgAdmin Embed Settings → Manage → New and paste three values: the URLhttps://orgadmin.ai, the Key ID, and the secret. Custom setting values are data rather than metadata, which is why the deploy cannot fill them in for you.
Place it on a page
In the Lightning App Builder, drag OrgAdmin Insight onto a page and set its properties:
- Dashboard or chart ID — copy it from the Embed panel. This is the only required property.
- Record filter ID — record pages only; see below.
- Extra filters (JSON) — optional fixed values, for example
{"stage":["Closed Won"]}, when one placement should always show a particular slice. Build it in the Embed panel and copy it across: each filter type takes a different shape (a stage picker wants an array, a date wants an object), and a value in the wrong shape is quietly ignored rather than reported. - Card title, Initial height, Theme — presentation only. The dashboard measures itself and corrects the height once it renders, so the initial value just avoids a jump on first paint.
Filters you do not fix stay live inside the page: a viewer can still change the date range without leaving Salesforce.
Filtering by the record
A dashboard does not automatically know what an Account page is about — it has to declare a filter for the record, and you point the component at it. The simplest way to get one is to ask the builder for it: “this will go on the Account record page, filter it by the record it's embedded on.” The AI then adds a filter bound to the right lookup field and gives it a working sample record so the dashboard still previews properly inside Insights.
The Embed panel shows that filter's id — put it in Record filter ID and the page's record is substituted every time the component loads. If the panel says no record filter exists, the dashboard will simply show org-wide numbers on every record, which is occasionally what you want (a company-wide average to compare against) but usually is not.
One dashboard, every record
Keys and rotation
The key is a shared secret: your org's Apex signs each request with it, and this app checks the signature. Two keys can be active at once, which is the whole rotation story — create the new one, paste it into the custom setting, then revoke the old one.
Revoking takes effect on open pages at their next refresh rather than whenever a session happens to lapse, so it is a real off switch. Revoke a key if you suspect it has been copied out of the org, or when someone who could read the custom setting leaves.
Who sees what
Embedded data is read as the connected org user
Because each org answers with its own data, nothing crosses between them — a dashboard in your sandbox cannot show production figures. What switching embedding on does decide is that any org connected to this workspace may render it. Which orgs those are is governed by embed keys: an org with no key shows nothing, and revoking a key cuts it off at the next refresh.
In practice that means you should choose the pages deliberately. A pipeline dashboard on an Account page that every sales user already has access to is fine. A dashboard covering the whole company, dropped on a home page everybody sees, is a decision worth making on purpose rather than by accident.
Every embedded load is written to the audit log with the dashboard, the key used, and which filters were applied — never the filter values themselves.
When something looks wrong
- “OrgAdmin embedding is not configured” — the custom setting has no org default record yet, or one of its three fields is blank.
- An empty box where the dashboard should be — the Trusted URL is missing, inactive, or does not match
https://orgadmin.ai. Salesforce refuses to frame anything it has not been told to trust. - “This embed is not available” — the key was revoked, or the Key ID and secret belong to a different org.
- “This dashboard is not shared” — embedding was switched off for it. Turn it back on in the dashboard's Embed panel.
- “This dashboard is not available here” — the Dashboard ID is wrong, or it belongs to a different workspace. Re-copy it from the Embed panel.
- One tile shows an error, the rest are fine — that query references a field the org you placed it in does not have. Nothing checks this ahead of time, so it surfaces the first time you view it there.
- “This link has expired” — normal for a tab left open a while; the component signs a fresh link by itself and the message clears.
Related: Insights for building the dashboard in the first place, Development Studio for the deploy, and Connect your Salesforce orgs for org settings and roles.