docs: sections: 7 rows where breadcrumbs = "["Authentication and permissions"]", breadcrumbs contains "Authentication and permissions" and references = "[]"

7 rows where breadcrumbs = "["Authentication and permissions"]", breadcrumbs contains "Authentication and permissions" and references = "[]"

Search:

descending

id ▼	page	ref	title	content	breadcrumbs	references
authentication:authentication-actor	authentication	authentication-actor	Actors	Through plugins, Datasette can support both authenticated users (with cookies) and authenticated API agents (via authentication tokens). The word "actor" is used to cover both of these cases. Every request to Datasette has an associated actor value, available in the code as request.actor . This can be None for unauthenticated requests, or a JSON compatible Python dictionary for authenticated users or API agents. The actor dictionary can be any shape - the design of that data structure is left up to the plugins. A useful convention is to include an "id" string, as demonstrated by the "root" actor below. Plugins can use the actor_from_request(datasette, request) hook to implement custom logic for authenticating an actor based on the incoming HTTP request.	["Authentication and permissions"]	[]
authentication:authentication-actor-matches-allow	authentication	authentication-actor-matches-allow	actor_matches_allow()	Plugins that wish to implement this same "allow" block permissions scheme can take advantage of the datasette.utils.actor_matches_allow(actor, allow) function: from datasette.utils import actor_matches_allow actor_matches_allow({"id": "root"}, {"id": "*"}) # returns True The currently authenticated actor is made available to plugins as request.actor .	["Authentication and permissions"]	[]
authentication:authentication-ds-actor	authentication	authentication-ds-actor	The ds_actor cookie	Datasette includes a default authentication plugin which looks for a signed ds_actor cookie containing a JSON actor dictionary. This is how the root actor mechanism works. Authentication plugins can set signed ds_actor cookies themselves like so: response = Response.redirect("/") response.set_cookie( "ds_actor", datasette.sign({"a": {"id": "cleopaws"}}, "actor"), ) Note that you need to pass "actor" as the namespace to .sign(value, namespace="default") . The shape of data encoded in the cookie is as follows: { "a": {... actor ...} }	["Authentication and permissions"]	[]
authentication:authentication-permissions-metadata	authentication	authentication-permissions-metadata	Configuring permissions in metadata.json	You can limit who is allowed to view different parts of your Datasette instance using "allow" keys in your Metadata configuration. You can control the following: Access to the entire Datasette instance Access to specific databases Access to specific tables and views Access to specific Canned queries If a user cannot access a specific database, they will not be able to access tables, views or queries within that database. If a user cannot access the instance they will not be able to access any of the databases, tables, views or queries.	["Authentication and permissions"]	[]
authentication:id1	authentication	id1	Built-in permissions	This section lists all of the permission checks that are carried out by Datasette core, along with the resource if it was passed.	["Authentication and permissions"]	[]
authentication:permissions-plugins	authentication	permissions-plugins	Checking permissions in plugins	Datasette plugins can check if an actor has permission to perform an action using the datasette.permission_allowed(...) method. Datasette core performs a number of permission checks, documented below . Plugins can implement the permission_allowed(datasette, actor, action, resource) plugin hook to participate in decisions about whether an actor should be able to perform a specified action.	["Authentication and permissions"]	[]
authentication:permissionsdebugview	authentication	permissionsdebugview	The permissions debug tool	The debug tool at /-/permissions is only available to the authenticated root user (or any actor granted the permissions-debug action according to a plugin). It shows the thirty most recent permission checks that have been carried out by the Datasette instance. This is designed to help administrators and plugin authors understand exactly how permission checks are being carried out, in order to effectively configure Datasette's permission system.	["Authentication and permissions"]	[]

Advanced export

JSON shape: default, array, newline-delimited, object

CREATE TABLE [sections] (
   [id] TEXT PRIMARY KEY,
   [page] TEXT,
   [ref] TEXT,
   [title] TEXT,
   [content] TEXT,
   [breadcrumbs] TEXT,
   [references] TEXT
);