We’ve been working on something new in My Pega (my.pega.com) that I think many of you managing larger implementations will appreciate: Organization Settings.
As teams grow and more people start working with Blueprints, keeping things consistent and governed can get… complicated. This capability is designed to help bring a bit more structure and visibility to that process—especially for those responsible for governance.
Here’s what Organization Settings helps you do:
• Get a centralized view of blueprint adoption across your organization
• Apply administrative controls to manage blueprint access and lifecycle
• Align blueprint oversight with your org structure
• Customize branding (logo, colors) as it appears in Blueprint
If you want a quick walkthrough, you can check out this video: Watch the Blueprint Governance overview
Curious to hear from this group:
• How are you currently handling blueprint governance today?
• What challenges are you running into as usage scales?
Drop your thoughts, questions, or examples below—we’d love to learn from how you’re approaching this and what would make it even more useful.
Hi Dave,
First of all , Welcome to the Blueprint and App Design Expert Circle!
thank you for highlighting the feature around governance, having these finer controls is critical given the Blueprint Adoption is going to grow in the organisations.
Re: the Organisational Governance Admin role
How it is validated that the person requesting the role belongs to the organisation ? I would presume by validating their email address but worth mentioning explicitly.
How many members can request this role. is there some kind of cross referencing or organisations and people responsible in those organisations have to take care of who can request access?
Once granted, can someone see who else from their organisation have this access?
When settings are changed, do we have some audit trail of who change when and to what value ?
I think having this traceability would be important when there is more than one person that can have this access for any given organisation.
Thanks for the inquires. You are correct that the person requesting the role does need to be associated to the organization and email domain will make that connection.
There is not currently any cap or limit, but it’s something we could consider in future, and in general across all Pega Roles.
Finally we are considering an external audit history for this capability. Please stay tuned!
Hi Dave,
Thank you for response.
talking about cap on the numbers, I meant access to this function from the organisation point of view and not only cap on Pega roles only.
I will for sure be tunned to this as this is the question I expect to be providing answers to our clients and partners.
Watch the Blueprint Governance overview