Permissions & User Management
This section is a status placeholder. The Permissions & User Management topic is currently blocked pending finalized product specifications for the Lytics access model. Rather than publish governance guidance that does not reflect current product behavior, this section describes why the topic is blocked, what preparatory work you can do in the meantime, and how to track unblock status so your team is ready to implement permissions efficiently once the product-aligned documentation is available.
Status and Scope
Learning Objectives
By the end of this section, you will be able to:
- Explain why this topic is blocked and cannot yet be finalized
- Identify which permissions concepts are expected once updated product specifications are released
Why This Topic Is Blocked
This topic is currently blocked pending updated product stream information for the permissions model.
- The access model is undergoing product changes.
- Final role definitions, permission boundaries, and UI workflows are not yet stable for academy publication.
- Implementation instructions are intentionally withheld to avoid publishing inaccurate governance guidance.
Key Concepts
- Stability requirement: permission guidance must match current product behavior exactly.
- Enterprise impact: role and access design affects compliance, security, and operational ownership.
- Deferred publication: this section should only be expanded when product specifications are finalized.
Step-by-Step
- Treat this topic as a status placeholder, not an implementation source.
- Continue using account-level controls documented in Account Configuration.
- Track unblock status in the section-specific CLAUDE instructions.
- Revisit this topic when product-approved permissions documentation is available.
Examples
Blocked-topic rule:
- Do not publish role matrices or permission screenshots until product specifications are finalized.
Summary
This topic is intentionally blocked because the Lytics access model is undergoing active product changes. Publishing role matrices or permission workflows before specifications are finalized would risk introducing inaccurate governance guidance into enterprise implementations. Track unblock status in the CLAUDE topic notes and revisit this section once product-approved documentation is available.
Documentation Links
Preparation Until Unblocked
Learning Objectives
By the end of this section, you will be able to:
- Prepare account governance inputs needed for future permissions implementation
- Document open questions so the final permissions rollout can be completed efficiently
Interim Readiness Work
Until this topic is unblocked, you can prepare the following:
- Document team roles and operational responsibilities (implementation, analytics, marketing ops, security).
- Inventory integrations and destinations that will require scoped access controls.
- Define review cadence for access audits and ownership changes.
- Track open questions internally until product-approved documentation is available.
Summary
The most productive use of this blocked period is building the governance inputs the permissions rollout will need: a documented map of team roles and responsibilities, an inventory of integrations requiring scoped access, and a defined audit cadence. Capturing open questions now means the final implementation can move quickly once the product specifications are stable.
Documentation Links
What You've Learned
This section established that Permissions & User Management is a blocked topic within the D&I Implementation Academy, deferred until the Lytics access model product specifications are finalized. Publishing incomplete or inaccurate governance guidance carries enterprise-level compliance and security risk, which is why this section functions as a placeholder rather than an implementation guide. The preparatory work outlined here — documenting team roles, inventorying integrations, and capturing open questions — ensures that when the block is lifted, the implementation can proceed without delay.
Key Terms
📘 Permissions model — The system that defines which roles can perform which actions within a Lytics account. Role definitions, permission boundaries, and UI workflows are pending product finalization at the time of this writing.
📘 Access control — The set of rules and configurations that govern which users can view, edit, or manage specific platform resources, including integrations, audiences, and account settings.
📘 Governance runbook — A documented set of operational procedures for managing user access, including onboarding, access reviews, ownership changes, and offboarding.
