--- name: adobe-enterprise-rbac-544342fd4f43 description: >- Govern Adobe Developer Console roles, product profiles, technical accounts, User Management API automation, and periodic access review. Use when the task requires adobe enterprise access governance. Trigger with "Adobe RBAC", "Adobe product profiles", or "Adobe user provisioning". allowed-tools: Read,Glob,Grep,Write,Edit argument-hint: " " version: 1.8.0 license: MIT author: Jeremy Longshore tags: [saas, adobe, rbac] model: inherit effort: high compatibility: "Designed for Claude Code; live Adobe actions require network access, appropriate entitlement and authentication, and explicit approval" --- # Adobe Enterprise Access Governance ## Overview Govern Adobe Developer Console roles, product profiles, technical accounts, User Management API automation, and periodic access review. This workflow produces a reviewable artifact and evidence before any live side effect. ## Prerequisites - Current first-party Adobe documentation for every selected service, API version, auth flow, limit, and lifecycle. - Named product, identity, security, data, budget, release, and operations owners appropriate to the scope. - Synthetic or approved non-production fixtures with secret and content canaries. ## Current Contract Developer Console project access, API scopes, product entitlement, product-profile assignment, and resource ownership are distinct. User Management API manages enterprise users/groups/entitlements under its own authorization; it is not a generic fix for application API access. Recheck the dated evidence map before relying on mutable product behavior. ## Authentication Use named admin/automation identities with least privilege, environment binding, approver separation, rotation, and review dates. Technical-account access is constrained by assigned product profiles. ## Instructions 1. Inventory organizations, directories, admins, developers, projects, credentials, users/groups, products, profiles, and automation. 2. Build a role-to-operation matrix and calculate effective access across Console roles, scopes, profiles, and resources. 3. Identify orphaned credentials, broad profiles, stale users, shared admins, and cross-environment grants. 4. Design joiner/mover/leaver and service-account changes with approval, idempotency, reconciliation, and rollback. 5. Canary UMAPI changes on a synthetic group where authorized and compare intended versus effective access. 6. Schedule recertification, exception expiry, secret rotation, audit export, and emergency revocation. ## Tool Discipline Use Read, Glob, and Grep to inspect current documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Skill invocation alone does not authorize network access, credentials, Adobe content, consent, uploads, generation, spend, deployment, registration changes, replay, cancellation, or deletion. ## Approval Boundaries Organization, product, identity, and security owners approve grants and revocations. Bulk membership/profile changes and credential deletion require explicit execution approval. ## Error Handling - Do not equate an OAuth scope with product entitlement. - Do not use UMAPI against an unverified organization. - Quarantine drift rather than auto-removing critical access without an approved rollback. ## Output Return organization/access inventory, effective-access matrix, findings, approved change plan, reconciliation, exceptions, and recertification schedule. Mark assumptions, observed environment behavior, owners, evidence dates, and unresolved gaps explicitly. ## Examples - Prove a technical account is limited by its product profile. - Remove a synthetic group assignment and verify intended loss of access. ## Validation Exercise and record expected and observed results for: - orphaned account - overbroad profile - wrong organization - stale admin - bulk partial failure - rollback ## Resources - [Current first-party evidence map](references/official-docs.md) — recheck dated Adobe sources before execution. - Treat observed tenant or product behavior as environment-specific evidence, never a universal Adobe guarantee. --- Source attribution: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/adobe-pack/skills/adobe-enterprise-rbac/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Dave AI. ## Upstream license notice MIT License Copyright (c) 2025 Jeremy Longshore Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Dave AI resource metadata Creator / publisher: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/adobe-pack/skills/adobe-enterprise-rbac/SKILL.md Attribution basis: Source repository record Fields of work: Design, Development & Engineering, Product Management Roles: Backend Developer, DevOps / SRE, Product Manager, Technical Product Manager, UX Designer Specialties: API, Design, DevOps, Word Documents, Frontend Tools: Adobe Creative Suite, Azure Ad, Google Workspace Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 9d0d2010b23d2a711a8dca973d6de48d603e49ca5e09236a52e65b38cc92139f