JLT Platform — Access Model
The JLT Platform Access Model defines how users, contributors, subscribers, and administrators interact with platform resources, APIs, documentation, automation assets, and downloadable toolkits.
Access Flow
User → Authentication → Role → Subscription Tier → Entitlements
→ Resource Group Policy → Access Decision (Allow / Deny)
Identity Roles
| Role | Description |
|---|---|
| Public visitor | Access to public documentation and blog |
| Guest contributor | Access to contributor protocols and collaboration areas |
| Basic member | Access to basic member content |
| Toolkit subscriber | Access to toolkit downloads and previews |
| Platform subscriber | Access to platform runbooks and premium resources |
| Advisory client | Access to client-specific resources |
| Admin | Platform management and billing |
| Owner | Full platform control |
Subscription Tiers
- None
- Starter
- Toolkit
- Platform
- Advisory
- Internal
Resource Groups
All platform resources are grouped and protected by policy.
- docs.public
- docs.private
- comments
- contributor.protocols
- downloads.starter
- downloads.premium
- toolkit.preview
- toolkit.full
- runbooks.public
- runbooks.private
- automation.templates.basic
- automation.templates.premium
- api.platform.read
- api.platform.execute
- api.admin
- billing.customer
- billing.admin
Security Principles
- Deny by default
- All premium assets are API-protected
- Authentication does not equal authorization
- Access is evaluated per request
- Downloads require entitlement checks
Platform Boundary Model
| User Type | Access Level |
|---|---|
| Public Visitor | Public docs and blog |
| Guest Contributor | Contributor protocols and collaboration areas |
| Subscriber | Premium downloads, toolkit, private runbooks |
| Advisory Client | Client-specific resources |
| Admin | Platform management |
Related Pages
- Access Control — Entitlements and authorization enforcement
- Architecture Map
- Deployment Flow
- Entitlement Architecture