Sharing projects with paid assets WITHOUT sharing paid assets

I am new to Unity and initiating a collaboration / tutorial project.
In this project I'd like to inspire people to engage with a variety of Assets in the store.

A simple use case might be building a scene heavily leveraging something like SNAPS, sharing the project but without the SNAPS package.
The other person opens the project and is informed they are missing paid assets (e.g. snaps - whatever) and it takes them to the right page on the store.
They download and install - the project opens up seamlessly and are good to go.

Is this the existing user flow? (Unity makes it hard to recreate an anonymous user flow)
Is it simple to exclude paid packages when prepping to share Unity projects?
Any weird "gotchas" in such a user flow (like projects getting confused, scrambled, or corrupted) if they are missing assets / packages on open or complex re-import nightmares?

Snaps is the example - but this could be useful for almost all paid content (including tools).

TIA for any insight,
SAVR

 

If you upload your tutorial project to, say, GitHub, add .gitignore entries for the paid assets. Double-check your commits before pushing them up. You don't want to become an accidental software pirate.

Any code that depends on the paid assets will not compile until the paid assets are imported, and the project won't be able to play. So it's difficult to have a custom editor window or something like that pop up with instructions.
Instead, you'll want to include text instructions on how to acquire and import the paid assets. Once they import the paid assets, the project should automatically compile and be playable without any extra required steps.

 

Fantastic!
That solution will work great for us.
Thanks for the perspective.