Skip to main content

URL-First Navigation and Shareable Links

In the web client, the browser address bar is the view. Whatever you're looking at — a queue, a specific request, a user record, the appointment calendar on a particular day — is reflected in the URL at the top of your browser. That means you can do something the old desktop client never could: copy the address, paste it into an email or chat, and the person who opens it lands on the same request, queue, or record you were looking at. (Two things stay local to your browser and aren't part of the link — your split-view layout and your pinned tabs; more on that below.)

Most of the time you never think about this. You click queues, requests, and search results, and the URL quietly updates to match. You reach for it on purpose in three situations: when you want to bookmark a view you return to often, when you want to send a coworker a link to a request you need help with, and when you use browser Back and Forward to retrace your steps.

When you'll use this
  • "Can you take a look at request #12345?" — copy the address bar and paste the link, instead of telling them the number and making them search for it.
  • You check the same queue every morning — bookmark it once and open it with one click.
  • You moved through a few different queues or pages and want to step back — the browser's Back button returns you through the views you navigated to (not through every request you clicked along the way).

How a view maps to a URL​

You don't build these URLs by hand — Aeon writes them as you navigate. But it helps to recognize what they mean when you see one. Here are the views you'll share most often:

What you're looking atURL in the address bar
The dashboard (home)/dashboard
A specific queue/requests?queue=5
Everything carrying a flag/requests?flag=3
A single request, full-screen/requests/12345
A request opened to a particular tab/requests/12345?tab=history
A user record/users/jdoe
The appointment calendar on a date/appointments?date=2026-06-04&view=day
A single activity/activities?activity=12
A saved search or search results/search?q=civil+war&type=requests

A couple of things worth noticing:

  • The numbers and names are real and stable. /requests/12345 always points at transaction #12345; /users/jdoe always points at the user jdoe. These don't change between sessions, so a link you save today still works next week.
  • Question-mark pieces are filters and selections. Everything after the ? (like queue=5 or tab=history) describes how the page is set up. You can usually ignore it, but it's why a shared link can reopen not just the right page but the right queue, tab, or calendar day.
  • Some links also carry a display label you can ignore. A flag link, for example, usually looks like /requests?flag=3&flagName=Special%20Processing — the flag=3 is what does the work (it filters to requests carrying that flag), and the flagName is just a label Aeon adds so the heading reads correctly the moment the page opens. A trimmed /requests?flag=3 opens the same view; Aeon fills in the flag's name from the flag itself.
Why this matters in day-to-day work

On the desktop client, "go look at this request" meant telling a coworker a number and trusting them to find it. In the web client you send the actual address and they're looking at it in one click — no searching, no "which queue was that in again?" The URL carries that context.

The most common use. Say a coworker asks you to weigh in on request #12345:

  1. Open request #12345 — click it in a queue, or use the command palette, or however you'd normally get there.
  2. Look at your browser's address bar. It now reads something like .../requests/12345.
  3. Copy the whole address (click into the address bar and Cmd/Ctrl+C, or use your browser's Copy option).
  4. Paste it into your email, chat message, or ticket.

When your coworker clicks it, Aeon opens straight to request #12345 — same as if they'd searched for it themselves.

Share the exact tab, too

If you've opened the request to a specific tab — say its history — the address includes that (.../requests/12345?tab=history). Copy it as-is and the recipient lands on that same tab. Handy for "look at the History on this one" without extra explanation.

There's no special "Copy link" button — sharing is just copying the address bar, exactly like any other website. The same approach works for a user record (/users/jdoe), a queue (/requests?queue=5), or a calendar day.

Split view and pinned tabs aren't part of the link

A link carries the navigational view — the queue, request, user, activity, calendar day, or tab you're on. It does not carry your split-view layout or your pinned tabs; those live in your own browser (see Multi-Tab Workflow and Pinned Items). So if you copy the address while comparing two requests side by side, the link reopens only the active request on its own — not the two-pane layout — and the recipient opens it with their own pins, not yours. To point someone at both requests, send the two links (/requests/12345 and /requests/67890) and let them pin and split on their end.

Bookmarking views you use often​

Because each view has its own stable address, you can bookmark it in your browser like any web page:

  1. Navigate to the view you want — for example, your team's main queue.
  2. Use your browser's bookmark command (Cmd/Ctrl+D in most browsers) to save it.
  3. Open it any time straight from your bookmarks bar.

Common things staff bookmark: a specific processing queue, the user-clearance page, or the appointment calendar. The bookmark reopens the same view every time.

Back, Forward, and how Aeon tracks history​

Aeon distinguishes between moving to a new view and changing something within the view you're already on, and it treats your browser history accordingly:

  • Moving to a new area or view adds a history entry. Switching between Requests, Activities, Appointments, and the Dashboard, opening a different queue, or opening a request as its own page (from a shared link or the command palette) — each of these is a step your browser's Back button can return from.
  • Selecting an item or switching a tab within the area you're already in does not add history. Clicking through the requests in a queue one after another, picking users from the users list, or flipping a request's tabs all update the address bar in place rather than stacking up Back steps. So Back moves you between the areas and views you navigated to — not back through every individual record you clicked.

The practical upshot: Back is a reliable way to retrace your real navigation without getting stuck clicking through every individual record you glanced at.

The command palette (Cmd/Ctrl+K) is just a fast way to reach these URLs. Whatever you do there — opening request #12345, jumping to a user, navigating to the dashboard with the / prefix, or running a search — ends with you on one of the addresses above. So a place you reach through the palette is just as bookmarkable and shareable as one you click to.

Permissions — a link doesn't bypass them

Sharing a link doesn't grant anyone access they don't already have. When a coworker opens a link you sent, Aeon applies their permissions, not yours:

  • A link to a request (/requests/12345) requires the View level of the Requests permission to open. Someone without it sees an access message instead of the request.
  • The same is true for users, activities, and every other view — the recipient needs the matching permission for that area.

So you can share freely: a teammate who isn't allowed to see something still won't see it, link or no link.

Unsaved edits are protected when you follow a link

If you're partway through editing a request or user and you click a link, a bookmark, or Back that would leave the page, Aeon stops and asks what to do with your unsaved changes before navigating away — so a stray click on a shared link won't silently throw away work in progress. Switching the selected item or tab within the same page doesn't trigger this; only leaving the page does.