configuration

Hierarchical configuration uses settings.json files at user, project, and enterprise levels with precedence rules. Project-level settings override user defaults, and enterprise policies apply organization-wide, ensuring consistent behavior across your team's workflows.

Permissions use allow, deny, and ask patterns to grant or restrict access to files and tools. Configure these in settings.json to auto-approve common commands, block sensitive files like .env, or prompt for approval on risky operations.

Set environment variables in settings.json or via slash commands to persist critical values across sessions. This centralizes configuration, prevents hardcoding secrets, and ensures consistent variable behavior in your Claude Code environment.

Yes, project-level settings.json files enforce consistent configuration across your team. Place settings in your project root to standardize model choices, restrict file access, and auto-approve build commands, ensuring uniform security and behavior.

Sandbox controls restrict Claude Code's system access and file operations based on your permission rules. Configure sandbox settings in settings.json to isolate sensitive directories, limit tool execution, and control what Claude Code can read or modify.

Yes, interactive slash commands let you configure Claude Code settings on demand without editing files. Use them to toggle permissions, set environment variables, or adjust sandbox behavior for immediate changes during your session.