Permissions

team permissions voltage team permissions control what a person can do across the voltage team specific pages and actions can apply additional product or credential checks use security > access model for the complete product by product boundary the team permissions are read view resources on permitted pages write create or modify supported resources and settings on permitted pages team management invite, remove, and update team members and their roles billing manage permitted billing settings and information owner organization owner actions the current product also requires owner to create, list, or delete infrastructure api keys the current product treats owner as satisfying the other team permission checks, but a team role does not bypass environment scoped payments api permissions, node password checks, lnd macaroon permissions, or other security boundaries payments ui permissions are team level, while payments api keys are scoped to one environment use security > access model and security > payments access when separating staging and production access invitation form when inviting a user, enter an email address and enable at least one of the permissions presented by the product review every toggle before continuing and grant only the access needed for the person's role invitation permissions govern human team access they do not reveal or replace environment api keys, infrastructure api keys, node passwords, lnd macaroons, or recovery material invite user form with example team permissions selected roles are selected during invitation product specific credential and permission checks still apply