JLT Platform — Resource Groups

Resource groups define the protected boundaries of the JLT platform. They are the units used by the access-control layer to allow or deny access to documents, APIs, runbooks, toolkit surfaces, and billing features.

Current Resource Groups

• docs.public — public documentation
• docs.private — restricted documentation
• comments — commenting and contribution surfaces
• contributor.protocols — contributor-facing protocols
• downloads.starter — starter downloads
• downloads.premium — premium downloads
• toolkit.preview — preview toolkit access
• toolkit.full — full toolkit access
• runbooks.public — public operational runbooks
• runbooks.private — private/internal runbooks
• automation.templates.basic — basic templates
• automation.templates.premium — premium templates
• api.platform.read — read-only platform API access
• api.platform.execute — execution-capable platform API access
• api.admin — administrative APIs
• billing.customer — customer billing surfaces
• billing.admin — billing administration

Why Resource Groups Matter

Resource groups make the authorization model explicit. Instead of protecting isolated pages or endpoints one by one, the platform protects categories of assets consistently through policy.

Typical Flow

Request
  ↓
Session Context
  ↓
Access Profile
  ↓
Resource Group
  ↓
Entitlement Check
  ↓
Allow / Deny

Related Pages

• Access Model
• Access Control
• Architecture Map
• Domains