docs: sections: 1 row where breadcrumbs = "["Authentication and permissions", "Configuring permissions in metadata.json"]" and title = "Controlling access to specific tables and views"

1 row where breadcrumbs = "["Authentication and permissions", "Configuring permissions in metadata.json"]" and title = "Controlling access to specific tables and views"

Search:

descending

id ▼	page	ref	title	content	breadcrumbs	references
authentication:authentication-permissions-table	authentication	authentication-permissions-table	Controlling access to specific tables and views	To limit access to the users table in your bakery.db database: { "databases": { "bakery": { "tables": { "users": { "allow": { "id": "*" } } } } } } This works for SQL views as well - you can list their names in the "tables" block above in the same way as regular tables. Restricting access to tables and views in this way will NOT prevent users from querying them using arbitrary SQL queries, like this for example. If you are restricting access to specific tables you should also use the "allow_sql" block to prevent users from bypassing the limit with their own SQL queries - see Controlling the ability to execute arbitrary SQL .	["Authentication and permissions", "Configuring permissions in metadata.json"]	[{"href": "https://latest.datasette.io/fixtures?sql=select+*+from+facetable", "label": "like this"}]

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
);