How do you add premade collections to a user’s library in Adalo?
Choose whether premade collections stay shared or become user-owned copies, then preserve their movie relationships instead of copying only the title.
Decide whether each premade collection is a shared template or an editable user copy. For a shared template, relate the user to the existing collection and display its related movies. If users can edit it, create a separate user-owned collection and recreate the movie relationships; adding only the title does not copy the contents.
Treat saving and copying as different operations. Saving can relate a user to the existing template; copying creates a new record and must also recreate the relationships that give the collection its contents.
The intended outcome
A user can add a premade movie collection and still see its movies, with ownership modeled according to whether that user may edit it.
Requirements
- Premade Collections and Movies connected by a relationship
- A User collection
- A decision about whether added collections remain shared or become editable copies
Step by step
- 01
Choose the ownership model
Keep premade collections shared when users only need to save or view them. Create user-owned copies when each user may rename or edit a collection independently.
- 02
Preserve the movie relationship
For shared collections, relate the User directly to the existing Premade Collection so its related Movies remain available.
- 03
Copy editable collections deliberately
If the collection must be editable, create a user-owned Collection record and recreate its relationships to the source Movies. Copying a Name field alone cannot copy related records.
- 04
Filter the library by user
Show collections related to the Logged-in User, then open each collection in record context so its related Movies can be listed.
The underlying logic
A relationship points to an existing collection and preserves access to its related movies; copying scalar fields creates a new record without those relationships.
Shared templates avoid duplicate data, while user-owned copies support independent edits at the cost of explicit copy logic.
Data model
| Collection | Important properties | Relationships |
|---|---|---|
| Premade Collections | Name and template metadata | Many Movies; optionally many Users when templates stay shared |
| User Collections | Name and ownership metadata | One User; many Movies when users need editable copies |
| Movies | Movie details | Related to premade or user-owned collections |
What still needs checking?
- This is a forum-native answer with no original Adalocado video. It is automatically organized from the accepted reply and remains open to correction reports.
Common failure modes
The collection appears but contains no movies
Check whether the workflow created a new collection with only its title. Relate the user to the original template or recreate every movie relationship on the user-owned copy.
One user’s edits affect everyone
The app is still using a shared template. Create a separate user-owned record before allowing edits.
Testing checklist
0 of 6 checked on this device
Current limitations
- This is an accepted community pattern and has not been reproduced by Adalocado in a current builder project.
- Duplicating a record and its related records can require multiple actions or a backend workflow; the forum source does not establish one universal copy implementation.
What the Adalo community is reporting
These are concise editorial summaries of public forum posts—not endorsements or independently reproduced results.
How can a user add ready-made collections/selections to their collections?
The accepted reply distinguishes a shared collection from a separate user-owned record and notes that editable user copies need their own stored record.
Boundary: The reply does not provide a verified end-to-end copy workflow for every related movie.
olga.solovyeva60 (question) and Dilon (accepted answer) · February 2026Sources and status
This page was last reviewed on Aug 14, 2026. Its current status is Documented from current sources.
Verification owner: Automatically organized from an accepted forum answer; monitored for corrections. Next review: Oct 14, 2026.
Changelog
Automatically posted from a solved Adalo forum topic; corrections are monitored on the live site.
Report this answer.
Automated Answers still pass evidence and publication checks, but they can be wrong, outdated, unclear, or missing an important boundary. Send the exact correction and the editor will check the live page.
Report a problemDid this solve your problem?
Never deal with an Adalo problem again.
Rehost becomes the monthly team behind your app. Fixes, releases, integrations, and ongoing changes have an owner.
See monthly managementBring us the messy version.
Describe what you expected, what happened instead, and what you already tried.
Ask Adalocado 💬
