One department. Defined roles. Connected people.

Residents may follow multiple participating agencies in one app. That convenience does not imply a combined police department, a shared command structure, or universal agency access to resident information.

Department access should be evaluated with the agency's authorized representatives. The onboarding process needs to establish who can approve personnel and the responsibilities attached to each available capability.

Ask for the actual account-approval and access behavior during evaluation rather than relying on a general security statement.

Document which records are public, which stay within the workspace, and which can be disclosed or transferred under the agency's procedures and the available implementation.

Technical controls and operating policies should be reviewed together. Claims about audit logging, certifications, retention periods, or tenant isolation require the corresponding evidence.

Residents should understand which department publishes a post and which department receives a tip. Clear attribution helps the public choose a relevant source and the intended recipient.

A resident’s life may span several jurisdictions. That does not turn several departments into one organization. A useful network preserves the source of public information and the identity of the agency handling an incoming contribution. It should be possible to explain the citizen experience without implying that every agency can inspect every other agency’s records.

This distinction matters during onboarding and in public language. Explain who issues an update, who receives a submission and which organization answers questions about its handling. If a record needs to move, examine the supported transfer workflow and the agency’s own authority and procedures.

The Sentinel product listing describes department-code joining with departmental approval before data is visible. A demonstration should show that sequence and explain who may approve access. The existence of an approval step does not by itself establish every security property a department may require.

Source: Sentinel Dashboard — Detailr Corp. product listing

Use a practical access review: identify the roles expected to publish, review tips and manage personnel; establish how authorized staff are approved; and ask what happens when a person changes roles or leaves. Record questions about logs, data export, retention and support as questions until the relevant evidence is available.

A professional evaluation distinguishes the product’s current controls, the department’s operating rules and requirements that remain to be resolved. Clear answers are more useful than a broad claim that a workspace is secure or compliant with an unnamed standard.

Begin with the roles your agency needs: someone may prepare a public draft, someone may authorize publication and someone may review tips. One person may perform several roles in a small team. Write down the tasks first, then inspect how the current product supports the intended access.

Ask who can approve or remove an account, what happens when a person changes role and how a department verifies that a former staff member no longer has access. These are evaluation questions. Do not infer a particular permission model, audit system or certification from the phrase separate workspace.

Use representative accounts in an authorized demonstration. A diagram can explain the intended separation, but the decision to rely on it needs evidence from the actual implementation and the agency’s requirements.

Also discuss temporary cover and staff departures. A supervisor should know who is authorized to act when the regular publisher is unavailable and how that authority ends. Record the operating answer separately from the software behavior you inspect, so a staffing decision is not mistaken for an automatic product control.

An agency can need both a public explanation and details that are not suitable for release. The Sentinel listing describes public and internal cases; evaluation should establish how staff recognize those states and what a resident can actually see.

Follow a fictional case from preparation to publication. Check the visible department name, the public details and the tip recipient. Then examine the department-side record. Make sure the team understands what changes at publication rather than relying on an icon or a color alone.

The question is practical: can the people operating the workspace distinguish the information they may use internally from the information they are authorized to release? Confirm that distinction through the current product and the agency’s own review process.

Source: Sentinel Dashboard: Detailr Corp. product listing

The IACP’s ALPR guidance addresses documented purpose, authorized use, training, retention, sharing and review of misuse. Those recommendations concern ALPR specifically. They also suggest sensible questions for a broader information-system evaluation, provided the adaptation is made explicit.

For Sentinel, ask which policies govern staff use, which organization holds a delivered record and how a sharing or records request is handled. Identify the owner of each decision. A connected resident network should not blur the legal and operational responsibilities of participating agencies.

Keep a written list of demonstrated controls, supporting documents and open questions. Where the evidence is incomplete, record the gap. A clear evaluation is more useful than treating a product name or a vendor statement as proof of every control.

Source: IACP: responsible use of license plate recognition