# Make it yours: everyone works their own way, on one shared app > People work differently, and forcing one screen on all of them is how you end up with a spreadsheet on the side. In Cordango everyone shapes their own columns, layout and dashboard without copying the app, forking the process or creating a second source of truth. Source: https://www.cordango.com/make-it-yours/ Language: en PERSONAL VIEWS # Your screen. Everyone’s data. People work differently, and forcing one screen on all of them is how you end up with a spreadsheet on the side. In Cordango everyone shapes their own interface: the columns they need, the layout that suits them, their own home dashboard. If a list annoys you, ask for a board. [Book a demo →](https://www.cordango.com/contact/) [Why it doesn’t fragment](https://www.cordango.com/make-it-yours/#one-app) ## Personal, without becoming fragmented. The usual trade is between one rigid screen everybody resents and a copy of the app per team. The first pushes people into private spreadsheets. The second gives you three versions of the truth and nobody sure which is current. Cordango takes neither. Shaping your view does not copy the app, fork the process or create a second source of truth. The application still belongs to the company, permissions still decide who can use it, and the records underneath stay one set of records. Everyone can work their own way. The company still runs one system. - YOU Your columns, your layout, your dashboard - ONE One app underneath, not a copy per person - SAFE Personal views never widen what you may see - ROLE A warehouse view and a finance view of the same data Same app · three people Deliveries \# mara · dispatch board by route · today only · driver + van columns \# tomas · finance table by customer · unbilled first · value + terms \# lena · support list by promised date · late at the top ✔ one app one set of records · one permission model ## A view can never show you more than you may see. This is the part that makes personalisation safe to hand out. A view describes layout: which columns, which order, which grouping, which filters. It is not a permission, and it cannot become one. Permissions are decided by the platform, underneath, before any view is applied. So you can share a view with a colleague without thinking about it. They get your layout applied to their own records. If half of what you see is invisible to them, their copy of your view simply has fewer rows. Nobody has ever leaked a record by sharing a saved view, because a saved view carries no data. [How permissions are decided →](https://www.cordango.com/security/) Shared view “Late deliveries” \# mara shares her view with lena ✔ layout columns, sort, grouping, filters ✗ records never travel with a view \# what lena sees ✔ mara's layout ✔ lena's permissions her rows, not mara's ## Three levels, depending on how far you want to go. LVL-01 ### Tune what is there Choose your columns, sort them how you think, filter to your own work, save it as a view you can come back to. The everyday case, and it takes seconds. LVL-02 ### Change the shape A list is a board is a calendar. Same records, different way of looking at them. Dispatch wants a board by route, finance wants a table by customer, and neither has to argue for it. LVL-03 ### Build your own page Assemble a screen from the app’s own pieces, or describe the page you want and have it built. Yours by default, shareable with your team when it turns out to be good. All three run on the app the company owns. None of them creates a second copy to keep in sync, and none of them can widen what anyone is allowed to see. ## Your home screen, not the company’s. The same idea runs up to the dashboard. A finance lead opens Cordango and sees invoices due and cash in. A support lead opens the same platform and sees the queue and who is away. Neither of them is looking at a report someone built for “the business”, and neither of them had to ask for it. Widgets can pull from every app at once, so a personal dashboard is not limited to the app you happen to be in. It is the part of the company you are responsible for, on one screen. [How cross-app widgets work →](https://www.cordango.com/dashboard/) Two people · one platform Monday morning \# henrik · finance → invoices due €18.4k · 3 overdue → cash in this month €212k \# lena · support → open tickets 12 · 2 breaching today → team away 3 this week ✔ same platform different job, different screen 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/) - [**Connected by default** Apps work together from day one](https://www.cordango.com/dashboard/) - [**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 ## One app. Everyone’s own way in. See the same app from three different jobs, live, and what happens to permissions when a view gets shared. [Book a demo →](https://www.cordango.com/contact/) [The one-pager](https://www.cordango.com/one-pager/)