Surface: clinic community

A clinic community is what one clinic's own clinicians have shared with each other: a worksheet, storybook or form a colleague put into the clinic's shared library for anyone in the same clinic to browse, preview and copy into their own. It is framed inside the workspace as the Internal Library area — a promoted-clinic concern, not the PlaySpace-wide practitioner community, which stays out of the frame entirely — and it is also reachable directly on the REST API: an organisation token can list one clinic's library with partner_clinic_id, and every write — sharing, copying, removing — is delegated, acting as the clinician, as is previewing one item's content.

There is no standalone SDK mode for it. The only way to frame it is inside shell, the same way Rooms sits inside Creative Suite.

What it renders

`surface`	What the clinician sees	The URL the SDK builds
`clinic-community`	the clinic's shared worksheets, storybooks and forms — browsable and filterable by kind	`/embed/shell/clinic-community`
`clinic-community` opened on one item	that item's preview: a worksheet's or storybook's pages. A form shows its name and description with Copy to my library; its questions are seen after the copy, in the Forms area	`/embed/shell/clinic-community/{id}`

There is no editor here. A preview is read-only in both directions — nothing typed or drawn in it is saved anywhere, because the item on screen is the clinic's shared copy, not the clinician's own.

The identifier it needs

None, to open the area. The clinic is the acting practitioner's own, resolved from the seat the token names, exactly as the rest of the workspace needs no identifier to open. Previewing, copying or removing one item needs that item's clinic-community id, which comes off a row in the list — it is not the id of the underlying worksheet, storybook or form.

Capabilities

Capability	What it adds
`community:read`	required to open the area at all: the list and one item's preview.
`community:write`	Share with clinic on the worksheet, storybook and form screens, Copy to my library on every card in the list as well as on an item's preview, and Remove on an item the clinician shared themself.

community:write is never implied by community:read: a seat bought to browse what colleagues shared has not thereby bought one that adds to or removes from the shared library.

The REST side

The clinic-community operations, all under the "Clinic community" tag, all requiring a delegated token except the list, which an organisation token may also call:

Operation	Purpose	Token
`GET /v1/partner/clinic-community/items`	List what the clinic has shared, newest first, filterable by kind.	Delegated or organisation
`POST /v1/partner/clinic-community/items`	Share one of the acting practitioner's own worksheets, storybooks or forms with their clinic.	Delegated only
`GET /v1/partner/clinic-community/items/{id}`	Preview one shared item, with its content.	Delegated only
`POST /v1/partner/clinic-community/items/{id}/copy`	Copy a shared item into the acting practitioner's own library.	Delegated only
`DELETE /v1/partner/clinic-community/items/{id}`	Remove an item the acting practitioner shared.	Delegated only

An organisation token may list one clinic's community, by passing that clinic's id as partner_clinic_id — required on that tier, and refused with a 422 on a delegated token, whose clinic is the acting practitioner's own. Every other one acts as one clinician and stays delegated-only.

Sharing the same content with the same clinic twice answers 409 community-item-conflict. Errors covers it in full; in short, it is not retriable with the same content — list the clinic community to find the existing item, or remove it first.

Things that will bite you

A shared copy is independent of the original, in both directions. Editing the clinician's own worksheet, storybook or form after sharing it does not change the shared copy, and a colleague's copy of that shared item does not change either. Three separate pieces of content exist the moment a copy is made.
Games are not shared here. item_type is worksheet, storybook or form only — a game session has no library entry to share in the first place.
There is no search and no sort on the wire. The list takes only item_type and cursor pagination, and is fixed newest first; there is no free-text search parameter and no caller-chosen sort order, so a host that wants either filters what it has already fetched rather than asking the endpoint for it.
Removing a shared item does not undo the copies colleagues already made. DELETE takes the item out of the clinic's list; anything a colleague already copied into their own library stays exactly where it was.
An organisation token gets metadata only. The list gives titles, descriptions, tags, age categories and a thumbnail — enough to render a catalogue — but never the content itself: preview, copy and remove are all delegated-only, so a server-side read of the clinic's library cannot open, duplicate or retire what it lists.