DocID®DocID® Documentation
Back to DocID®
  • Overview

    • DocID® Documentation
  • Introduction

    • Introduction
    • How DocID® works
    • Core concepts
  • Getting Started

    • Getting Started
    • Drupal module
    • WordPress plugin
    • Custom website
    • Go-live checklist
  • Features

    • Features
    • Standard Login
    • Access and personalization
    • Analytics
    • Campaigns
  • Licenses

    • Licenses
  • OAuth 2.0

    • OAuth 2.0
    • Configure a client
    • Authorization code flow
    • Scopes and UserInfo
    • Security and environments
  • API

    • API
  • Help

    • Troubleshooting

Features

Access and personalization

Use approved DocID® profile claims to create relevant website journeys.

DocID® profile claims can support access rules and tailored website experiences when the corresponding information is available and your organization has an appropriate purpose for using it.

Example decisions

  • Route a user to content for a selected language or country
  • Adapt content for a professional group or discipline
  • Permit an employee-only area
  • Exclude a defined audience from a campaign or action

Implementation pattern

  1. Request only the scopes required for the experience.
  2. Read claims on your server after successful authentication.
  3. Convert the approved claims into a small application-specific access decision.
  4. Store the decision—not unnecessary raw profile data—in the local session.
  5. Define a safe default when a claim is absent or not eligible.

Do not assume every claim is present. Your application must handle optional profile fields and changed profile information.

Review scopes and claims

PreviousStandard LoginNextAnalytics

On this page

  1. Example decisions
  2. Implementation pattern