Skip to main content
When a user arrives at the HASP authorization endpoint, they see a consent screen that identifies your application and lists the permissions being requested.

​
What’s displayed

ElementSource
App iconicon_url on your application registration
App name (linked)display_name + homepage_url
Agent nameThe agent the token will be bound to
Permission listauthorization_details from your authorization request
If no icon_url is set, the app name appears without an icon. From your application’s detail page in the developer console, click Preview consent screen. This shows exactly what users will see with your current application metadata, using placeholder permissions.

​
Customizing the display

Update your application’s metadata via Developer Console → Applications → (your app) → Settings:
  • Display name — shown as the app name on the consent screen
  • Homepage URL — makes the app name a clickable link so users can learn more
  • Icon URL — 48×48px minimum; HTTPS required; shown as a rounded square
Changes apply immediately to future consent requests.

​
Authorization details

The permissions shown on the consent screen come from the authorization_details parameter in your authorization URL (Rich Authorization Requests, RFC 9396). Each entry maps to a human-readable label:
TypeLabel shown
hasp.data.readRead <entities> [in <app>]
hasp.data.writeWrite <entities> [in <app>]
external.tool.invokeInvoke tool: <tool_id> [(<rate_limit>)]
agent.delegateDelegate to agent <id> (depth ≤ <n>)
human.escalateEscalate to <role/user> [via <channels>]
Write and escalation grants are highlighted in red to signal elevated access.

​
Approval and denial

After the user approves, HASP redirects to your redirect_uri with a short-lived authorization code. If the user denies, HASP redirects with error=access_denied. HASP records the consent decision and the full authorization_details in the audit log. Users can view and revoke granted applications from their agent’s credential settings at any time.