Permissions and Safety Modes

4 min
Audience
curious developers, beginner to intermediate
Time
15 to 25 min
Module
2/5
Skill goal
decide, on purpose, what Claude Code may do without asking you first

In one picture

Handing a new employee a company badge is a great way to think about permissions. On day one, they might need approval for almost everything — even the printer. A trusted senior colleague, by contrast, has a badge that already opens most doors. You choose exactly how much of Claude Code's "badge" is punched: which actions run silently, which ones must always pause and ask, and which stay locked. And, crucially, that setting is not written in stone — you can retighten it as soon as trust wobbles or the project changes.

Preview — the rest of the lesson is for enrolled readers.

Already enrolled with a code?

Your access is tied to your account, not to this link. Sign in with the same email you used in class: your course is waiting, no need to enter the code again.

Sign inNo account yet? Create one
This lesson is part of the “Safety and customization” module

The first modules of the course are open to everyone. For the rest you have three options: buy this course once and for all, subscribe, or enter the code handed out in class.

Are you a student on this course?

The code is tied to your account: sign in or create an account and it will be applied automatically when you come back.

No account yet? Create one