If your user's account can install modules in either his own user scope or the machine scope, they will be fine. By giving only a subset of your users write-access to the gallery, you can effectively narrow down who is even allowed to publish production code. Another suggestion would be to give everyone read-access and allow write-access only to gallery administrators, as well as dedicated build services for teams or projects:

# Register internal repository
Register-PSRepository -Name Internal -SourceLocation https://NUGSV01/api/v2 -PublishLocation https://NUGSV01/api/v2/package

# Recreate PSGallery repository if it has been removed
Register-PSRepository -Default

# Discover any existing modules
Find-Module -Repository Internal

# Upload VoiceCommands module
# Data in PSD1 file will be used to generate metadata
$apiKey = 'oy2ihe7sqbggn4e7hcwq66ipg2btwduutimb3bbyxrfdm4'
Publish-Module -Name VoiceCommands -NuGetApiKey $apiKey -Repository Internal -Tags Voice,Automation

# Install module on another server, another user, ...
Install-Module -Name VoiceCommands -Repository Internal -Scope CurrentUser