Content Management, Curated Collections, and Permissions
Content model
Gallery content includes workflows, apps, macros, and datasets. Content is organized into districts/collections and shared via permissions. Curated Collections are admin-curated groupings that surface selected content to defined audiences - they are about discoverability, not a substitute for permissions. A user still needs permission on the underlying asset to open it, even if it appears in a collection.
Sharing and permissions
Sharing can be to individual users, groups, or everyone. Permission levels (view, run, edit, manage) stack with role ceilings. Ownership matters: the owner controls sharing; Curators can administer any asset. Know that subscriptions let users follow content and receive notifications, and that districts (in older terminology) group users for sharing.
Traps
The biggest trap: assuming adding content to a Curated Collection grants access. It does not - the collection is a lens, permissions are the gate. Another trap: assuming deleting a user deletes their workflows; ownership must be transferred or the content becomes orphaned/managed by Curators. Also watch for confusion between "shared with me" and "public" - public means everyone in the instance, not the internet.
Worked example
A Curator adds a sensitive workflow to a collection visible to all users. Users still cannot open it because asset permissions exclude them. To fix discoverability and access, the owner must also share the asset (or a Curator adjusts permissions). Both steps are required.
Rule of thumb
Collections control what you see; permissions control what you open. Grant both, or the item is a dead link.