Skip to content

Portal Overview

The Dory Portal is the web app where organizations manage everything they need to produce and consume events: members and roles, app clients, processor templates, lenses, sensors, event types, and the subscriptions their app clients hold. It's the human-facing counterpart to the API and a companion to the Application SDK.

Who uses it

Role What they do here
Organization admins Invite members, manage roles, create app clients
Operators Register and review sensors, define event types, compose lenses
Template developers Publish processor templates and submit new versions for review
App developers Create app clients, use the Request Builder to get a ready-to-run Python snippet, and check or delete the subscriptions an app client holds

Signing in

Opening the portal shows a sign-in screen, and Continue with SSO takes you to the Dory sign-in page and back. The portal renews your session in the background while you work. There is no separate portal password: you sign in with your Dory account. Account settings, the light/dark theme and Sign out are in the user menu at the top right.

Organizations & the org switcher

You act within one organization at a time. The organization switcher at the top of every page shows the active organization and lets you change it. It also offers Create new organization, which asks for a license key.

Switching organizations reloads what's on screen for the new organization. Lists start again from the top, and their search, sort and filters go back to their defaults. Your role, and therefore what you can see and do, is evaluated per organization. See Identity & Access.

The portal is permission-gated: the sidebar shows only the pages your role in the active organization allows, and every page only offers the actions you're allowed to take. If you open a link to a page you can't use, the portal says You need access to view this page: switch organizations, or ask an organization admin for the permission. The same permissions are enforced by the API behind the scenes.

Sidebar item Guide
App Clients App Clients
Processor Templates Template developer guide
Lenses Lenses
Sensors · Event Types Sensors & Tags
Organization Organizations & Members
Organization → Roles Roles & Permissions
Request Builder App Request Builder

A System Admin group, covering users, organizations, templates, running processors, sensors and lenses across the whole platform, appears only for platform administrators.

Working with lists

Every list in the portal works the same way.

  • Lists load as you scroll. Rows arrive in batches of 50 as you near the end of the list. A Load more button stays at the bottom while more rows exist, and there are no page numbers.
  • Search, filters and the column picker sit in the table's header, above the rows. Changing the search, a filter or the sort reloads the list from the top. The rows already on screen stay visible, dimmed, until the new ones arrive.
  • The count is shown in the same header. It reads "312 sensors" once every row has loaded, or "Showing 150 of 312 sensors" while more remain.
  • Hide or show columns with the column picker, on lists that have optional columns. The portal remembers your choice in this browser. When a table includes other organizations' records, it shows an Organization column that can't be hidden.
  • Your search, sort and filters are kept in the page address, so a filtered view can be bookmarked or shared. The address never carries your active organization: someone who opens the link sees the same query applied to their own active organization.
  • If a batch fails to load, the rows you already have stay, and the list shows "Couldn't load more…" with Retry. If the list changes on the server while you scroll, it says so and offers Reload from top.
  • After 1,000 rows, loading stops. Search, filter or reverse the sort to reach the rest. When a long list has fully loaded, Back to top takes you back to the start.
  • Pickers over large sets (event types, templates, lenses, organizations) search as you type, so every item is reachable even inside a dialog.

What you see is what has loaded

Your browser's find-in-page and print only cover the rows loaded so far. Rows whose sort value changes while you scroll, such as a status or a last-seen time, can be skipped or repeated until the list next reloads.

Opening a record

  • Click a row, or its trailing Open button, to open the record. Opening only needs read access. A few lists hold no record to open. On Organization, each member row carries its actions directly: Resend invitation for someone who hasn't accepted yet, Manage roles and Remove member.
  • Each record has one dialog that both shows and edits it. A field you may change is an input, and a value you can't change is plain text. Without edit rights you see the same dialog with values only and no Save.
  • Larger records are split into sections listed down the left side of the dialog, for example a sensor, an app client or a processor template.
  • A save bar appears as soon as something differs from what was saved. It reads "n unsaved changes" and offers Discard and Save changes. Typing a value and changing it back doesn't count as a change. Closing the dialog with unsaved changes asks Discard unsaved changes? first.
  • Delete lives inside the record's dialog, below its fields or at the foot of the section it removes, and only for members allowed to delete. Row buttons never delete a record that has a dialog. The more an action breaks, the more it asks of you:
    • Reversible actions just happen.
    • Destructive actions contained to your organization ask for confirmation.
    • Irreversible actions that stop live traffic or reach beyond your organization ask you to type the record's name. Examples are deleting an app client or a lens, and decommissioning a sensor.
  • Creating starts from the page's main button, which opens a create dialog. A newly created record is pinned to the top of the list and marked New. An edited one stays where it is, marked Updated, and records move into their sorted place the next time the list reloads.

The sensor dialog is the same wherever a sensor appears: on the Sensors page, whether the sensor is yours or another organization's public one, and on the Request Builder's map pins. Another organization's sensor shows its owning organization by name and never its connection details. A sensor's device login is never shown to anyone, your own organization included: the dialog says only whether one is saved. You can edit a sensor only if it belongs to your organization and your role allows editing sensors, and making a sensor public asks you to confirm when you save.

Fastest path to your first event

Create an app client and choose a lens, either one of your own or another organization's public lens by its alias. Then open the Request Builder: click a map tile and press ✓ to add it as a geo area, pick event types and the lens, and choose Get Python snippet. Running that snippet creates the subscription. The portal itself never creates subscriptions, but each app client's dialog lists the ones it holds.