Company based accounts?

[draco2003]

We promote opensource contributions at work and attempting to setup an account with PowerShellGallery to publish our packages to in order to share, but the account creation link Prevents us from using a shared mailbox with this message:

"You can't sign up here with a work or school email address. Use a personal email such as Gmail or Yahoo! or get a new Outlook email."

Any thoughts on allowing teams/companies to publish to the PowerShellGallery?

Thanks!

[draco2003]

Looks like a personal address can be used and then you can change the Email address after the fact.
This doesn't let others manage the account, but at least they get notifications, etc..

[JamesDawson]

This seems to work fine now, however, in this post from 2018 there was talk of having organisation support (like nuget.org) - is this still on the roadmap?

[bormm]

I do not like using some shared-mailbox account for login and I think it is also not state of the art. A login should be only for people identification, not for a role. You can't share yourself and a password should never be shared. If you use a shared mail adress and shared passwords, how do you handle a password change? How handle a person should not have access anymore, because the person left the company? So for me its totaly ok not to allow login with shared mailboxes, as there are no identities.

I agree that there is a organisation feature missing, that in a perfect world would allow using AzureAD to handle who is part of that organisation and who can push new versions of what packages. As even this could be totaly different in the same company. People should only have the needed rights for security reasony.

Unfortunatly it seems that MS assigned only very few resources to the gallery for the last 2 years. That would be ok, If the powershell gallery would be depricated and everyone could install also powershell modules via cmdline from the Windows Store. But thats not the case, PowerShell Gallery is still the place to get packages for our loved shell that of course as now more a future than ever before with .Net Core.