Help

Entities All help

Entities (admins)

Every organization the system knows, arranged in a tree with OPN at the root.

Kinds, and who owns a case

Every entity is one of three kinds, by its relationship to OPN: a financial institution is OPN's customer, an integrator is a customer's customer, and a service provider makes OPN's service possible. A service provider also records the services it renders OPN, and may render several: core system (the core itself), core integration (connecting a core to OPN), digital banking (the web and app layer through which an FI's customers reach their accounts on the core — the industry's term), payment screening (fraud and sanctions screening of payments), FI network (a payment network), software and business services.

Any entity can own cases and have an intake address. A case's owner entity is whoever wrote to us — an FI, an integrator, or a provider asking about its own integration. Its staff work the case; anyone else works it by being involved. The Cases column counts every case the entity owns, whatever its status; click it for that list. Open cases (in the column picker) counts only those not yet resolved or closed; click it for the open list.

What an entity can see

An entity's users can select — for a new case's owner, for involvement, for a broadcast audience — only entities above or below it in the tree, plus any on its Can also select list. Never siblings, cousins or unrelated entities.

The list belongs to the entity whose users get the extra choice, and it is one-way. Putting a service provider on an FI's list lets the FI's people pick the provider (to involve it, say); it does not let the provider's people pick the FI. For that, put the FI on the provider's list. Set both if the relationship goes both ways.

Cases follow the tree: a user sees a case if its owner is their entity or one beneath it, or their entity is involved. Broadcasts targeting an entity reach everything beneath it.

Finding an entity

The list loads as you scroll and the search box at the top matches name or slug. There are hundreds of entities — most of them credit unions directly under OPN — so search first. Every entity picker in the tool (parent, Can also select, a case's owner, an audience) works the same way: type, scroll, at most 20 matches shown at a time.

Verified intake

Beside each intake address and SMS number in the list is a mark: a tick once the service has received a message there, a question mark until it has. Nothing else turns the mark — only a real delivery. Hover the tick for when the latest message arrived: every delivery refreshes it, so a test you send today shows today, not the first day it ever worked. Click either mark for how to send a test (an email to the address, a text to the number; each opens a case you then close as a test) and what to check if nothing arrives.

Editing an entity

  • Details — name, kind (and, for a service provider, its services), parent, intake address, intake SMS number (the shared platform number unless the entity has its own; a number can be shared, and entities beneath inherit it — an OPN administrator adds a new one right here with Add a dedicated number… once it exists in Twilio, and only an OPN administrator can give an entity a number that isn't already its own), active. Moving an entity to a different parent changes what its users can see immediately.
  • Broadcast recipients — how broadcasts reach the entity's people: each person's regular and emergency channel and mobile, set on Users or by the person; contacts are people added for this alone, who never sign in. Everyone who signs in sees broadcasts in the tool regardless; do not notify turns the channels off.
  • Can also select — the exceptions to the tree rule, described above: what this entity's users may pick beyond the entities above and below it. You can list only entities you can see yourself.

Removing

An entity with users or cases can't be removed — history has to keep pointing at it. Deactivate instead: its users can't sign in, it drops out of every picker and audience, and its cases stay readable. Remove is available only while nothing refers to the entity.