Somebody's role is missing a permission it should have. You want a colleague to look at it, so you open Slack and type: open Administration, then Access Management, then the Roles tab, then find Jane. Four sentences to get someone to a screen you are looking at right now. By the time they land there, you've both spent longer navigating than the actual fix will take.
That tax gets paid constantly and counted rarely: a support ticket where the customer has to describe a screen instead of naming it, a bug report where "it happens on the entity editor" could mean five different tabs. Every screen in Primentra has its own bookmarkable link, so most of that description collapses into one paste.
What MDS actually gave you instead
MDS Explorer's Silverlight UI opened to a single entry point and rebuilt its own state as you clicked through models, entities and members. The browser's address bar barely moved. There was no link for "this entity, this member, this version" to drop into an email, because the screen you were looking at had no address of its own to give. You told the next person which model, which entity and which filter to set, from the beginning, every single time. Set the wrong filter and you were looking at the wrong data without knowing it.
Every single-page application does this by default, Silverlight or not, unless someone deliberately wires the router to the URL. We wired it in for every screen in the product.
Names in the address, not IDs
A URL can also fail you while technically existing. /entity/47/member/1839 tells you nothing until you open it, and it breaks the moment you move data between a test and a production database where the IDs don't match. Primentra builds the address from the name instead. A model called Cost Center becomes cost-center in the URL: lowercase, no punctuation, spaces turned into hyphens. That's why /model/products and /admin/access-management/users/jane-doe read the same way on a test server, a production server, and a screenshot in a ticket six months from now.
| Screen | Address |
|---|---|
| Data grid | /data/products/suppliers |
| One user | /admin/access-management/users/jane-doe |
| Business rules overview | /admin/business-rules |
| One integration view | /admin/integration-views/vw-suppliers |
| Entity editor, staging tab | /admin/models/products/suppliers/staging |
Reloading the browser reopens the same screen on the same tab, because the address is the state. Nothing extra is being remembered behind it. If a session times out mid-task, signing back in returns you to that screen instead of the dashboard, so the five minutes you'd already spent finding the right entity aren't spent twice.
A bookmark is only as stable as the name it was built from. Rename the entity a link points to, and the old link stops resolving. It opens the parent screen rather than a broken page, but it isn't the screen you meant anymore. If you're the kind of team that renames things people have bookmarked, that's worth a Slack message of its own the day you do it.
Where it actually saves time
An auditor asking for evidence is the clearest case. Point them at the permissions report for the entity in question, or at the exact Preview As view that proves a role can't reach a field, and the link carries the whole claim. We wrote more on what that evidence actually needs to show in the auditor doesn't ask who changed the record, they ask who still can.
Onboarding gets the same benefit in smaller doses. A new steward's first week is full of "go look at how the Supplier entity handles approvals." A link does that in one line instead of a paragraph of navigation, and it's a link you can paste straight into a training doc without it going stale the next time the sidebar gets reorganized.
Common questions
Does every screen have a URL, or only the main pages?
Every screen, and every tab inside it. General Settings puts the tab in the address: /admin/general-settings/email opens the Email tab directly. The entity editor does the same for business rules, staging config, staging data and staging batches. The first tab of a screen is the default and stays out of the address, so a plain link is never longer than it needs to be.
What happens to a bookmark after I rename the thing it points to?
It breaks, on purpose rather than by accident. Primentra builds the address from the name, so a renamed model or entity leaves its old link pointing nowhere useful. It opens the parent screen instead of a dead page. Rename something people have bookmarked, and send them a fresh link.
Does the link still work after my session times out?
Yes. Sign in again and Primentra reopens the exact screen and tab the link named, instead of landing you on the dashboard and leaving the rest of the click path to you.
Can I link to one row, not the whole entity grid?
No, not yet. The address reaches the entity, such as /data/products/suppliers, not a filtered view or a single record inside it. Once your colleague is on the right grid, naming the row is still a sentence, not a link.
Try pasting a link instead of writing one out
The 60-day trial installs on your own SQL Server. Open any screen, copy the address bar, and see how far it gets a colleague on its own.