sections: authentication:authentication-permissions

This data as json

id	page	ref	title	content	breadcrumbs	references
authentication:authentication-permissions	authentication	authentication-permissions	Permissions	The key question the permissions system answers is this: Is this actor allowed to perform this action , optionally against this particular resource ? Every permission decision can be understood in terms of those three values. Datasette implements the decisions using SQL, but you do not need to understand the generated SQL to configure or debug permissions. Actors are described above . An action is a string describing the action the actor would like to perform. A full list is provided below - examples include view-table and execute-sql . A resource is the item the actor wishes to interact with - for example a specific database or table. Some actions, such as permissions-debug , are not associated with a particular resource. Datasette's built-in view actions ( view-database , view-table etc) are allowed by Datasette's default configuration: unless you configure additional permission rules unauthenticated users will be allowed to access content. Other actions, including those introduced by plugins, will default to deny .	["Authentication and permissions"]	[]