Share and embed native dashboards
Plan interactive dashboard viewing, authentication and application context alongside the administrative API.
Embedding a dashboard lets people use reporting within an application they already work in. Build that viewing journey around IFBI’s supported sharing and embedded-link features, with the API handling appropriate resource administration.
Separate viewing from API administration
Use your installation’s API URL, normally on port 50255, for REST requests. Dashboard viewing and sign-in use the web application, normally served over HTTPS on port 443. Keep these addresses separate: an embedded viewer link is not the base URL for API calls.
REST operations manage supported dashboard resources and sharing configuration. They do not constitute a general JavaScript embedding or dashboard-designer SDK.
Share Secure Dashboard returns a share identifier in Data. Treat it as the documented identifier, not as a rendered dashboard or a complete viewer URL. Use the installed product’s sharing experience and documented link format to establish the viewing route.
Start with a working dashboard and authenticated link
Prepare a native dashboard that already shows the correct data. Generate its embedded link using IFBI’s sharing controls and select the appropriate authentication requirement. Confirm that an intended reader can sign in and reach the expected dashboard before placing the view inside your application.
The product walkthrough is How do I setup Dashboards in IntelliFront BI?. Use its sharing section alongside the behaviour of your installed build.
Add application context deliberately
For a dashboard that supports parameters, agree the parameter names, types and permitted values with the reporting owner. A reporting period or selected branch can provide useful context. Validate the actual link syntax and the dashboard’s handling of those values in your installation.
A parameter is an input to reporting. It is not an authorisation boundary: a customer must not gain access to another customer’s data by changing a URL value.
Verify the complete browser journey
Check sign-in, expired sessions, access-denied behaviour, parameter encoding, navigation and display size. When embedding crosses origins, validate the actual browser, framing, cookie and network behaviour for the deployment. Do not assume a bearer token used by a server-side API client automatically signs in the dashboard viewer.
Keep API credentials out of public pages and embedded URLs. Retain the supported authentication and access controls for the reader journey.
Continue with users, groups and content access and native dashboard definitions.
Updated 34 minutes ago