Permissions and safety Beta

Grants from the consent screen, risk tiers and confirmation that the model cannot skip

Beta. The Device SDK is live for design partners: Dopl issues your project's keys while the developer portal is being built, and @dopl/sdk is available on request. Agents that act for one signed in Dopl user can use the hosted MCP server instead.

Permissions work in three layers. Your project requests capability scopes when it opens a Connect session, the user grants some or all of them on the consent screen, and a policy engine checks every call against that grant. The policy engine is plain code that runs outside any model, so a prompt cannot talk its way past it.

Risk tiers

TierExamplesOn the consent screenAt call time
T0Read state and presenceTicked by defaultAllowed
T1Display, notify, speak, askTicked by defaultAllowed
T2Camera, microphone or screen captureUnticked until the user ticks itAllowed only when the user ticked it
T3Lights, media, navigationUnticked until the user ticks itAllowed when ticked, unless your profile asks for confirmation or denies the tier
T4Locks, vehicle and robot motionUnticked until the user ticks itDenied by default, even when ticked. With a confirmation mode in your profile, every call returns needs_confirmation and does not run

What the policy engine checks

  1. The connection is active, not revoked and not expired.
  2. One of its granted scopes covers the capability, at the capability's tier or above.
  3. The tier's confirmation rule in the device's context profile. T4 is denied unless the profile sets a confirmation mode.
  4. The project's rate limit: 600 deliveries and device actions per minute per environment by default.

A failed check returns grant_missing, grant_expired, needs_reauth, confirmation_denied or rate_limited in the standard error shape. Only rate_limited is worth retrying.

Confirmation

A context profile sets how each tier is confirmed: none, on_device, trusted_surface or deny. T4 can never be none, and a T4 grant on the consent screen only records the user's consent; it never removes the confirmation. When a tier needs confirmation, the call returns the status needs_confirmation and the action does not run. Approving it from the device or a trusted surface is not available yet, so today a T4 action never runs.

Audit and revoke

Every call is logged with the key's project, the device and profile it used, the routing decision, the outcome and its latency. Revoking a connection from the API takes effect on the next call.