Access Model

voltage access has several layers use the narrowest layer that fits what the user or integration needs quick guide need use human dashboard access across the team team permissions human payments ui access team permissions application access to one payments environment payments api key infrastructure automation infrastructure api key direct node access node password or lnd macaroon team permissions team permissions apply across the voltage team they are not scoped to a single payments environment read view resources write create and modify resources team management invite/remove team members and change permissions billing manage billing related settings and information payments ui permissions payments ui access follows team permissions today read view wallets, balances, payments, and related resources across environments write create/manage wallets, create api keys, and send/receive payments across all payments environments in the team current limitation ui write cannot be scoped to staging only or production only within one team today roadmap environment scoped payments user access is tracked internally in dev 2322 payments api key permissions payments api keys are environment scoped read view resources in the selected environment write create/manage writable payments resources in the selected environment billing access billing or line of credit api operations where supported environment scope use separate keys for staging and production infrastructure dashboard permissions infrastructure dashboard access also follows team permissions team write create and modify infrastructure resources and settings infrastructure api keys team write users can create infrastructure api keys node sensitive material some fields and actions are still gated by the node password or decrypted node credentials dashboard limitation team write alone does not expose seed, macaroons, lndconnect , or other decrypted node sensitive material voltage infrastructure api the infrastructure api manages hosted node infrastructure it is separate from direct lnd access purpose manage node infrastructure and settings, such as listing nodes, getting node details, and managing node lifecycle api key creation infrastructure api keys are created from the infrastructure dashboard by a team member with write access api key permissions infrastructure api keys do not have their own permission set today access boundary the infrastructure api does not bypass the node password or lnd macaroon permissions direct node access direct node access is separate from dashboard permissions and api keys node password path decrypt or unlock node sensitive material through voltage macaroon path use the node endpoint plus lnd macaroon credentials through rest, grpc, or lncli broad macaroons admin, super admin, or broad custom macaroons can move funds if their permissions allow it narrow macaroons read only or invoice macaroons are narrower node state direct node operations generally require the node to be running and unlocked recommended setup during development, it can be reasonable to give developers team write so they can create wallets and api keys in the ui before production go live, revoke developer write and issue production api keys with the right environment scoped permissions if developers need ongoing ui write in staging but not production, use a separate team boundary until environment scoped payments ui permissions are available