Error
10-24-25
As of v17.0 Event Registration Templates now inherit permissions from their assigned category, but Workflow Types continue to not inherit privileged from their assigned category. Additionally, I discovered that Registration Templates automatically assign Edit Item permissions for RSR - Staff Workers and RSR - Staff Like workers. In our setup we restrict edit access to templates to a subset of staff. With these permissions added at the item level they override the settings at category. Accordingly, you have to update each and every registration if you categorically want to avoid giving RSR - Staff Workers edit access to templates. It would be more desirable and flexible if these permissions were hardcoded at the category level when a new category is created instead of being added as item permission for each template.
--------------------------------------While our current system typically facilitates permissions inheritance from parent objects or categories, certain exceptions disrupt this process, posing two significant challenges:
Where do permissions not extend from parent object/category to their child?The specific areas where inheritance breaks down are Workflow Categories to Workflow Forms and Registration Categories to Registration Templates.Why is this crucial to our goal and mission as a church?Imagine a scenario where a staff member discovers they have unintentionally gained access to confidential information within Rock. The misconfiguration of permissions not only poses a risk of breaching confidentiality but also undermines this staff members trust in Rock's capacity to safeguard sensitive data. Rectifying these discrepancies in permissions inheritance isn't just about streamlining administrative processes; it's about reaffirming confidence in Rock's ability to maintain the utmost confidentiality of our data.
Cultivate your ideas for maximum impact with these helpful submission tips that will increase the chances of your brilliant concepts becoming reality.