Workspace Datasheets

/datasheets mirrors the whitepaper workflow for one-page gated assets: create the datasheet, attach the file, review captured leads, and sync or export them. The sibling flow is documented at Whitepapers.

Routes and guards#

Route	Purpose	Guard
`/datasheets`	Admin list + stats (`DatasheetsAdminPage`)	`org:content:view` (`page.tsx` + `layout.tsx`)
`/datasheets/new`	Create form	`org:content:create`
`/datasheets/[id]/edit`	Edit form for one datasheet	`org:content:edit`

Entry point: page.tsx and layout.tsx both enforce requirePermission("org:content:view"); the write views narrow to create/edit. Client state lives in hooks/useDatasheets.ts.

Backing API routes#

Like whitepapers, this area uses the legacy admin tree:

Route	Purpose	Clearance
`/api/datasheets/admin`	List / create datasheets	`org:content:view` / `org:content:create`
`/api/datasheets/admin/[id]`	Update / delete one	`org:content:edit` / `org:content:delete`
`/api/datasheets/admin/leads`	Captured-lead inbox	`org:leads:view`
`/api/datasheets/admin/leads/export`	CSV lead export	`org:leads:export`
`/api/datasheets/admin/leads/sync-salesforce`	Push leads to Salesforce	`org:leads:export`
`/api/datasheets/admin/stats`	Download / conversion stats	`org:analytics:view`
`/api/datasheets/admin/upload/wordpress`	WordPress media attach for cover assets	`org:content:create`
`/api/datasheets/admin/health`, `/test/*`	Integration health + MongoDB/Sheets/Slack self-tests	`org:dev:tools_access`

Backed by MongoDB datasheets and datasheet_leads, with WordPress rendering the public detail pages.

Notable behaviour#

The extra route versus whitepapers is leads/sync-salesforce — datasheet leads can be pushed directly to CRM without going through a CSV export.
Lead export and Salesforce sync both gate on org:leads:export (unlike whitepapers export, neither writes audit entries); keep the two permissions (leads:view for reading, leads:export for extracting) separate when assigning roles.

Related: Whitepapers · Audience · Sales

Loading…