Document how permissions determine what the new Edit Content Screen shows and allows

Abierto
#38,657 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
56/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java, typescript

Línea de trabajo

Start by reading the permission logic in core-web/libs/edit-content/src/lib/store/features/user/ and store/features/workflow/workflow.feature.ts, then compare it with the implementation of #38649. Use that behavior to build the requested permission table for the docs site and library README, covering the listed editor elements and role cases. Done means the reference is linked from #37467 and any mismatches found are filed as defects under the relevant EPIC.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

dotCMS: New Edit Contentlet Team : Scout Type : Task
Description

Several reports in #feat-edit-content (October 2026) describe permission behaviour in the new editor as a black box: which permission hides a sidebar section, which disables a field, which removes a workflow action, and how limited roles without the Search tool behave. There is no page that answers this, so support and Professional Services test by trial and error.

This task produces that reference, for the docs site and as a short section in the library README, and files any mismatch it finds as a defect.

Acceptance Criteria
  • A table lists each UI element of the editor (fields, sidebar sections, workflow actions, lock, language selector, history, relationships picker) and the permission that controls it.
  • The behaviour for READ-only, EDIT without PUBLISH, and missing portlet access is described, matching the implementation of #38649.
  • Mismatches found while writing the table are filed as defects under the relevant EPIC.
  • The reference is linked from #37467.
Priority

Medium

Additional Context
  • Pillar #38634; adoption tickets #38649 and #34787
  • Code: core-web/libs/edit-content/src/lib/store/features/user/, store/features/workflow/workflow.feature.ts
Lenguaje dominante
Java
Estrellas
972
Forks
493
Merge medio
2 d 12 h
PR fusionados (30 d)
228

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de dotCMS/core

Todos los issues de dotCMS/core

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.