Libraries
This content is intended for all Studio users. All users. Licensed Studio users can have access to private libraries, while trial Studio users only access the public library on Marketplace.
Libraries are the organisational layer beneath the Marketplace. Every piece of content in the Marketplace belongs to a library, and your membership of a library determines what you can see, install, and upload.
Understanding how libraries work helps you collaborate effectively, control who has access to your content, and know where to publish when you are ready to share your work more broadly.
What libraries are and how they work
A library is a repository of Marketplace content shared with a specific group of members. Think of it as a scoped workspace within the Marketplace — all content inside a library is visible to its members, and members with the appropriate permissions can upload, edit, and manage content in that library.
Libraries serve two main purposes:
Organisation: Libraries group content by team, organisation, or clinical domain, making it easier for members to find content that is relevant to their work.
Access control: Content in a private library is only accessible to its members. This allows teams to develop and share assets without making them publicly available until they are ready.
All libraries coexist within the Marketplace. When you open the Marketplace, you see content from the public library and any private libraries you are a member of.
The public library
The public library is open to all Studio users. It contains content that has been validated, documented, and published for broad reuse including widgets, forms, templates, AQL views, and bundles provided by Better and by verified contributors.
Anyone with a Studio account can browse and install content from the public library. To publish content to the public library, see the Uploading content to the Marketplace section.
Private libraries
Private libraries are created for specific organisations or teams. They allow groups to share content with a controlled set of members without exposing it to the wider Marketplace community.
As a member of a private library, you can:
- Browse and install content from that library.
- Upload new content and new versions of existing content to that library, if you have the required permissions.
- Invite additional members to the library.
- Edit documentation and presets for content in the library.
Private libraries are typically used for:
- Internal clinical tools developed by an organisation's implementation team.
- Work-in-progress content being tested before wider release.
- Organisation-specific adaptations of public Marketplace content.
Joining and managing a library
To join an existing private library, you must be invited by a current member of that library. There is no self-service join flow. When you are invited, you gain access to the library's content the next time you open the Marketplace.
To request a new library or to carry out administrative actions beyond adding members and managing content, contact tools@better.care.
Once you are a member of a library, you can manage content and invite others without administrator involvement.
Sharing content within a library
Content you upload to a library is immediately available to all members of that library. There is no approval step within a private library — you are responsible for the quality and readiness of the content you share.
Edits to documentation and widget presets in the Marketplace are visible to all library members as soon as you save them. There is no draft or staging mode for documentation edits within the Marketplace interface. If you need to prepare documentation before making it visible, draft it outside the Marketplace and paste it in when it is ready.
Inviting members to a library
If you are a member of a private library, you can invite additional members directly within the Marketplace. Members you invite gain the same access to the library's content as you.
To invite a member:
- Open the Marketplace and navigate to the library you want to manage.
- Select the library settings or member management option.
- Enter the email address of the person you want to invite.
- Confirm the invitation.
The invited user receives access to the library. If they do not yet have a Marketplace account, one is created automatically when they first sign in with their Studio credentials.
For administrative changes beyond member invitations, such as removing members, renaming the library, or changing library-level permissions, contact tools@better.care.
Frequently asked questions (FAQs)
What is the difference between the public library and a private library?
The public library is open to all Studio users and contains content validated for broad reuse. Private libraries are scoped to specific organisations or teams, and their content is only visible to members. Both types coexist in the Marketplace interface.
How do I get access to a private library?
You must be invited by an existing member of the library. Contact your team or project lead to request an invitation. There is no self-service way to join a private library.
Can I create my own library?
You cannot create a library from within Studio. To request a new library, contact tools@better.care.
If I edit documentation or a preset in the Marketplace, who can see the change?
Everyone who is a member of the library where the content lives sees your changes immediately. This applies to both public and private library content.
Can I upload content to the public library directly?
Not directly. Content is first uploaded to a private library. See the Uploading content to the Marketplace section for the full flow.
What happens to my installed content if I leave a private library?
If you lose access to a private library, you will no longer be able to see or update that library's content in the Marketplace. Content you have already installed to a project may still be present in that project, but you will not be able to update it to newer versions or access the original library listing.
Can a library contain more than one content type?
Yes. A library can hold any combination of widgets, forms, templates, AQL views, bundles, and other supported content types. There is no restriction on the types of content within a single library.