[FOLIO-2578] Misleading Permission Set Configuration - Part 2 Created: 30/Apr/20  Updated: 13/Jul/21  Resolved: 15/Jun/20

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P2
Reporter: Craig McNally Assignee: Craig McNally
Resolution: Done Votes: 0
Labels: platform-backlog, security
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks FOLIO-2524 Security Audit raised issues Open
Relates
relates to FOLIO-2607 Spike: Permissions migration Open
relates to FOLIO-2611 Create stories for permission set rev... Open
relates to FOLIO-2565 Misleading Permission Set Configuration Closed
Sprint: CP: sprint 87, CP: sprint 90, CP: sprint 88, CP: sprint 89
Story Points: 1
Development Team: Core: Platform

 Description   

Overview

Continuation of FOLIO-2565 Closed .

Acceptance criteria

  • Walkthrough the proposed permission set guidelines with Tech Leads on the TL meeting
  • Create Jira tickets for individual teams to perform verification of permission sets in the modules they are responsible for, according to the best practices


 Comments   
Comment by Craig McNally [ 20/May/20 ]

Tech leads didn't have any objections.

Codified this here: https://folio-org.atlassian.net/wiki/display/DD/Permission+Set+Guidelines

Created and linked task FOLIO-2611 Open for story creation, which is blocked until we figure out a way to migration permissions ( FOLIO-2607 Open )

Generated at Thu Feb 08 23:21:41 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.