Tutorial — Connecting External Reporting (Power BI)

What This Tool Is For

How to feed your numbers into an external reporting tool safely — per project, read-only, and revocable.

Step-by-Step Walkthrough

Step 1 — In the integration area, each project can issue its own reporting key. The key grants READ access to that project's prepared figures and nothing else.

Step 2 — Hand the key to the report builder (or use it yourself in the external tool's data connection screen). The external tool can now pull cost, revenue, and KPI figures for that one project on refresh.

Step 3 — Scope keys tightly: one key per project per consuming tool. When an agency engagement ends or a key may have leaked, revoke that key alone — nothing else is affected.

Step 4 — Refresh discipline: external reports show data as of their last refresh; put the refresh timestamp ON the report so nobody reads stale numbers as live.

Real-World Example

Scenario: The leadership team lives in their existing BI tool and won't adopt another screen. The analyst issues a reporting key for the main project, builds the monthly pack in the BI tool against it, and schedules a nightly refresh. Leadership keeps their habits; the figures keep their single source of truth. When the external analyst who built it leaves the company, that one key is revoked in ten seconds — the data was never copied anywhere, only read.

Tips & Common Mistakes

• Keys are credentials: never paste them in chat or email; store them where your team stores secrets.
• Per-project scoping is the safety net — a leaked key exposes one project's read-only figures, not the company.
• If external numbers disagree with the platform, check refresh time first; nine of ten "discrepancies" are stale refreshes.

---

Everything described in this tutorial is a working feature of TupicFinance, the financial management platform of the Tupic ecosystem. The screens, workflows, and guardrails above behave exactly as written there — this guide doubles as the platform's user manual for this tool.