What belongs in each project environment?
Keep test and production values in separate environments. A machine identity is a login for an app or build, with its own permissions. Give each service only the environment and folders it needs. Review the role and the actual access granted before relying on the separation.
How does adding a service change the plan?
Infisical counts both human and machine identities. The Free pricing page lists five identities and unlimited projects. It lists features such as secret rotation and version recovery on paid plans. A self-managed deployment still needs someone to operate, patch and back it up.
What should you write down for a move?
Record the projects, environment names, service owners and access rules. Note who can replace each private value at the service that issued it. Ask which recovery and migration options apply to your setup before relying on them. Keep the inventory free of the actual values.
Which environment should a build be able to use?
Draw a paper access map for a fictional appointment app, with one test build and one live app. Put a label for each setting in its own environment.
- Give the test build one jobMark which test setting it needs. Leave production outside its access.
- Check the next owner can read the mapWrite who can review the permissions and who can replace the setting without putting any value on the page.