Hasp apps have four roles:Documentation Index
Fetch the complete documentation index at: https://docs.usehasp.com/llms.txt
Use this file to discover all available pages before exploring further.
viewer, org_admin_viewer, editor, and admin. The current user’s role is returned by sdk.getBootstrap().
Role Capabilities
| Action | viewer | org_admin_viewer | editor | admin |
|---|---|---|---|---|
| Read records | Yes | Yes | Yes | Yes |
| Create records | No | No | Yes | Yes |
| Update records | No | No | Yes | Yes |
| Delete records | No | No | Yes | Yes |
| Manage app settings | No | No | No | Yes |
The org_admin_viewer Role
Org admins and owners have baseline read access to every app in their organization — including apps configured as private or invite_only where they haven’t been invited as a member. When an org admin visits such an app, sdk.getBootstrap().role returns 'org_admin_viewer'.
This role:
- Has the same permissions as
viewer(read-only) - Signals that the user is seeing the app via baseline admin visibility, not via per-app membership
- Does NOT grant write access
'org_admin_viewer' to your read-allow set:
Getting the Current Role
Role-Based UI
App Access Modes
Each app has an access mode that determines the default role for org members:| Mode | Members can access | Org admins always see? | Default role for members |
|---|---|---|---|
| Open | All org members | Yes | viewer |
| Open + guests | All org members plus guests from allowed domains | Yes | viewer |
| Invite-only | Only members with an explicit grant | Yes — via org_admin_viewer baseline | No access without a grant |
| Private | Only members with an explicit grant | Yes — via org_admin_viewer baseline | No access without a grant |