Your job has one question. Your screen should answer it.

Twelve views. One question each.

Every cell below is a real, out-of-the-box view — not a template you assemble. Find your job, read the question in its cell, and that is what your screen answers when you sign in. Every role sees only what maps to its revenue responsibility, designed to fit within 1.5 desktop viewports at the default layout.

Why does my dashboard never show me what I need?

Because it was built for everybody, which is the same as nobody. The all-you-can-eat dashboard puts every metric for every team on one endless page, and your four tiles are on it somewhere — below the CFO’s, next to marketing’s, three scrolls down. So it becomes wallpaper, your team goes back to the spreadsheet, and the renewal that was quietly going wrong was technically on screen the whole time.

The fix is not more customization homework. It is a screen that already knows what your job is: one question per role, answered with the evidence behind it, on the view you land on.

How does it know which view is mine?

Three layers, from coarse to fine — and the last word is always a person’s.

1. 1

   Function

   Sales, Customer Success, or Product & Service Delivery. Your function decides which evidence matters at all — a seller’s week and a delivery lead’s week are built from different tools.

2. 2

   Level

   From individual contributor to CXO. Your level decides the altitude: an IC gets a queue of what to do next; an executive gets whether the machine is healthy and where the systemic risk sits.

3. 3

   Title

   An SDR, an AE and a sales engineer share a function and a level but not a job. Title families adjust the defaults — the SDR’s view leads with outreach, the AE’s with closing — without ever changing what you are allowed to see.

SalesSynq suggests your function and level from your job title using plain, inspectable rules — the same title always produces the same suggestion. The suggestion is never applied silently: you or your admin confirms it, and until someone does, you are asked rather than guessed at.

Does my role decide what I am allowed to see?

No — and this is the boundary that makes role views safe to roll out. Your role decides relevance: which view you land on, what it leads with, what the defaults are. What you are allowedto see is decided by your team’s permissions, exactly as before, checked on every request. A view never grants access, and confirming a different role never widens it.

What happens where our data does not reach yet?

The view tells you, in the most useful way it can: by naming the missing input. The Sales views run on evidence most teams already have connected. The Customer Success and Delivery views are honest about their appetite — a renewal book without tagged renewals asks you to tag them or connect a subscription source; a delivery view without a connected tracker names the tool that would light it up.

That refusal to fake it is the same rule the scores follow everywhere in SalesSynq: when the evidence is too thin, it tells you what it could not see instead of showing a number that came from nowhere.

Can I still shape my own workspace?

Yes — on top of your role view, not instead of the safety around it. Say what you are trying to do this week and the assistant proposes a personal workspace drawn only from tiles your permissions already allow. You look at the draft, and you keep it or bin it.

• It will not apply a layout without you saying yes — approval creates your own copy.
• It will not touch the role views or shared dashboards your team relies on.
• It will not widen your permissions, because permissions are settled by the server before the assistant is involved.
• It will not invent a metric. It arranges real tiles, which say when they do not know exactly as they do everywhere else.