Ideas

Communication Flow - Security

Note You are not authorized to edit this feature.

Communication Flow - Security

Communication

Communication Flows currently expose no per-flow security, no audit details, and no send dates in the performance overview. This request covers three related gaps.

1. Per-flow security

CommunicationFlow inherits Model<T> and is already ISecured, and the detail and list blocks already call IsAuthorized. However, no block exposes the security editor. The Communication Flow List block computes an isSecurityDisabled field but does not render a Security column, and the Communication Flow Detail block is a wizard with no panel header, so there is no Security button.

Request: add a Security column to the list grid and a Security action to the detail block so administrators can restrict View, Edit, and Administrate on individual flows.

2. Audit details

CreatedDateTime, CreatedByPersonAlias, ModifiedDateTime, and ModifiedByPersonAlias are stored on the entity but are not shown in the detail block or the list grid.

Request: show the standard audit details (Created By/On, Modified By/On) on the flow detail, matching other Rock detail blocks.

3. Send dates on the performance overview

The Performance block loads SentDateTime per recipient, but the message grid reduces it to a count and hides the Instance Start Date column. Over time there is no easy way to see when each communication in a flow went out.

Request: show the send date (or first/last send date per instance) for each communication in the performance message grid, and enable the Instance Start Date column.

Why

Our team runs flows across multiple campuses with many staff. Without per-flow security, anyone with entity-level edit access can modify any flow. Without audit details, we cannot tell who changed a flow or when. Without send dates, reviewing a flow's history after several instances requires opening each communication individually. These are standard features on other Rock entities and would bring Communication Flows in line with them.

References from the develop branch

  • Rock/Model/Communication/CommunicationFlow/CommunicationFlow.cs
  • Rock.Blocks/Communication/CommunicationFlowList.cs (isSecurityDisabled)
  • Rock.JavaScript.Obsidian.Blocks/src/Communication/communicationFlowList.obs
  • Rock.JavaScript.Obsidian.Blocks/src/Communication/communicationFlowDetail.obs
  • Rock.JavaScript.Obsidian.Blocks/src/Communication/CommunicationFlowPerformance/messageListGrid.partial.obs
Photo of Yeşu ChumSubmitted by Yeşu Chum, Houston's First Baptist Church  ·   ·  Communication
Login to add a comment...

Submission Success Tips

Cultivate your ideas for maximum impact with these helpful submission tips that will increase the chances of your brilliant concepts becoming reality.

  • Clear Title: Craft a straightforward and descriptive title that instantly conveys the essence of your idea.
  • Concise Description: Provide an idea description that is succinct, ensuring it effectively communicates the concept without unnecessary verbosity.
  • Provide Additional Details: With a concise description complete, now provide any other details that are needed to better understand the requirements.
  • Thorough Ministry Need Review: Provide a comprehensive overview of the ministry need your idea addresses, emphasizing its significance.
  • Cover the WHY: Clearly articulate the rationale behind your idea, explaining why it's essential and how it aligns with the organization's goals and mission. Oftentimes a clear "why" sheds light into other possible options.