Customer safeguards
- Grant only the repository access required for the selected analysis.
- Treat generated recommendations as review inputs, not automatic code changes.
- Keep secrets, generated artifacts, and excluded paths outside analysis scope.
- Use team-approved standards so scores do not replace engineering judgment.
Review cycle
- Confirm the workspace, scope, and product access before a sensitive action.
- Review the product result with the accountable customer owner.
- Record the decision and assign follow-up work.
- Verify the outcome before closing the task.
- Revisit policies, access, and notification paths when the environment changes.
Get support
When contacting support about Phoenix, include the workspace, affected workflow, approximate time, and any visible correlation identifier.