# One dashboard across every app, with nothing to integrate

> See your whole company on one screen: open tickets next to revenue next to who is on vacation. Every Cordango app is born on the same data core and permission model, so a widget that spans apps needs no connectors, no sync jobs and no BI stack.

Source: https://www.cordango.com/dashboard/
Language: en

CONNECTED APPS

# Every app on one screen. No integrations.

Tickets next to revenue next to who is on vacation. Nobody wires up an API, nobody exports a CSV, and you don’t need a technical team, because every app already lives on one platform with one set of records and one permission model.

[Book a demo →](https://www.cordango.com/contact/) [Why there is nothing to integrate](https://www.cordango.com/dashboard/#no-integrations)

## Why there is nothing to integrate.

In a normal stack, one dashboard across five tools is an integration project: API keys, connectors, sync jobs, a BI tool, and someone to keep it all alive. On Cordango every app is born on the same data core with the same permission model. A widget that spans apps is just a view on data that is already in one place.

-   ONE Every app lives on one shared data core
-   ZERO No connectors, no sync jobs, no exports
-   LIVE Widgets read live data, not last night’s copy
-   RBAC Permissions come from the platform, per user

Acme Ltd — company dashboard 4 apps · 0 integrations

€18.4k

OVERDUE · BILLING × CRM

12

OPEN TICKETS · SUPPORT

7

TRIALS ENDING · CRM

3

ON VACATION · HR

## Connected by default, not integrated later.

Cordango apps do not simply sit next to each other. They belong to the same company system. Win a deal in the CRM and the delivery project is already there, knowing the customer, the deal owner and the responsible team. Approved leave shows up in project planning without connecting two separate products.

That is what makes the dashboard cheap. Other platforms let a builder integrate applications, and the dashboard is the reward at the end of that work. Here shared company context is the default, so the dashboard is a consequence of how the platform is built rather than a project of its own.

-   CTX Every app knows your people, teams and customers
-   FLOW Work in one app can start work in another
-   VIEW Widgets from every app, on one screen
-   RBAC Everyone sees only what they’re allowed to

Acme Ltd — dashboard All apps

12

OPEN TICKETS

248

CUSTOMERS · 14 TRIAL

€18.4k

INVOICES DUE

3

ON VACATION THIS WEEK

## The interesting numbers live between your apps.

Which trial customers have an overdue invoice. Which projects are at risk while the lead is on vacation. Which big accounts opened tickets this week. None of those questions belongs to one app, which is exactly why they are the hard ones to answer in a normal stack. Describe the widget in plain words and it pulls from every app it needs.

-   ASK Describe a widget the way you’d ask a colleague
-   MIX Numbers, charts and lists across any apps
-   PIN Put it on your dashboard or your team’s
-   EDIT Change it later by asking again

[Ask the same questions over MCP →](https://www.cordango.com/ai/)

New widget Support + CRM

\# you > open tickets for our five biggest customers \# cordango ai ✔ widget created Support × CRM · list, live ✔ on your dashboard visible to sales & support

## Anyone can build one.

01

### Say what you want to see

Describe the widget in plain words, or pick the fields yourself. No query language, no data modeling.

02

### It finds the data

Because every app shares one data model, the widget can reach across all of them. Nothing to connect first.

03

### Share it safely

Pin it for yourself or your team. Every viewer sees only the records their permissions allow, automatically.

Your dashboard is yours. Two people can watch the same company from completely different angles without either of them seeing a record they shouldn’t.  
[How personal views work →](https://www.cordango.com/make-it-yours/)

## Side by side with the old way.

|     | Cordango | BI tool + connectors | Spreadsheet exports |
| --- | --- | --- | --- |
| Combine data from several apps | ✓   | ✓   | ~   |
| Built by the people who need it | ✓   | ✗   | ~   |
| Data is live | ✓   | ~   | ✗   |
| Respects each user’s permissions | ✓   | ~   | ✗   |
| Setup and maintenance needed | none | connectors, modeling, licenses | copy-paste every week |

✓ built in  ·  ~ possible with extra work  ·  ✗ not really  
A BI stack is the right tool for deep analytics. For “show me the company on one screen”, it is a lot of machinery for a job the platform can just do.

MORE

## The rest of the platform.

-   [**Run on Cordango** The live app: personal views, governance, shared context and connected work](https://www.cordango.com/run-on-cordango/)
-   [**App Contract** What the app offers: purpose, events, actions, queries and dependencies](https://www.cordango.com/app-contract/)
-   [**Personal by design** One app, different ways to work](https://www.cordango.com/make-it-yours/)
-   [**Governance built in** Identity, permissions and audit included](https://www.cordango.com/security/)
-   [**Agents & APIs** Agents, MCP and APIs across your whole company](https://www.cordango.com/ai/)
-   [**Platform foundation** The company foundation underneath every app](https://www.cordango.com/platform/)
-   [**Sample apps** Explore real apps you can install and make yours](https://www.cordango.com/templates/)

NEXT

## See your company on one screen.

Watch Cordango build an app from a description and put a cross-app widget on the dashboard, live, in about 30 minutes.

[Book a demo →](https://www.cordango.com/contact/) [The one-pager](https://www.cordango.com/one-pager/)