Best practices for shared credentials for pack development

I’ve developed a couple of packs for my team that are currently published with my credentials/API key. I would like to enable others in the team to contribute. Is there a recommended model for shared pack development within an organization that does not require sharing my API key with them?

1 Like

Hi Randolph!
Perhaps the system-wide authentication is what you’re looking for?

1 Like