model-command-access

Add the command name to the commands.access block in the model's manifest.json with an action like view, create, edit, delete, post, unpost, or authenticated. Then run deno task sql:registry so the declaration is copied into the generated model registry.

A 501 error means the command is non-standard and has no permission declared in commands.access. Standard commands like list, get, save, delete, and lookup derive their actions automatically, but every other command must declare one explicitly or it will not run.

Use view for reads, create for copy/import, edit for modifications, delete for deletions, and post/unpost for document posting. Use authenticated only for self-service commands whose result depends on the caller, and when torn between view and edit, pick edit.

No, standard commands derive their actions automatically: list/get/lookup map to view, save maps to create or edit, and delete maps to delete. An explicit declaration overrides the derivation, which is rarely needed except for sensitive models.

Declaring a permission in commands.access makes a command callable but not visible to the agent. You must also list the command name in agent.allowCommands in the manifest, since the agent only offers the default set derived from the model type plus explicitly listed names.

Use authenticated only for self-service commands whose result depends on who is asking and grants nothing beyond what that user already has, such as menu/current. Never use it to bypass a 501 error for commands that touch other users' data or write anything.