| |
---|
Exposing UI’s of Building Blocks: | The need to expose the UI’s of BB’s in the sandbox environment was discussed. This would allow users to directly use or at least view the interfaces of the building blocks, providing a complete understanding of all features beyond the USCT use case. Security concerns associated with this exposure were also discussed.
|
Documentation Requirements: | There was a discussion on the need for proper documentation in the GovStack Gitbook, specifically under the building blocks section or the sandbox section. This documentation should include details on customizations made for each BB DPG to meet GovStack specifications, along with a summary of lessons learned and challenges faced during customization.
|
Security and Access Control: | Discussed security concerns and access control mechanisms for the BB implementations. The possibility of creating a view-only user role and ensuring secure public exposure of UIs without compromising the system was a significant point of discussion.
|
Integration and Deployment Issues: | |
Centralized vs. Decentralized Authorization: | Discussions around whether there should be a centralized point of authorization in GovStack. Different perspectives were shared on the benefits of centralized vs. decentralized authorization mechanisms. Mention of role-based access control and where these roles should be stored and managed within the system.
|
User Experience and Usability: | |
Customization and Compliance with GovStack Specifications: | |