Can you clarify on why a CKSubscription is needed? [Scenario A] User A shares a list of tasks with user B through a CKShare. User B gets access to the CKShare record and any modification made by user B is done directly to the CKShare object which represents a reference to the list of tasks of user A. The same applies to modifications made by user A -- they would be directly reflected on the CKShare record. Why would I need a CKSubscription in this case? [Scenario B] The only scenario where a CKSubscription would be needed is if CKShare is copied over to user B's Core Data/CloudKit. Then I would implement a CKSubscription to notify the Core Data object on user B's end of any change to CKShare and vice versa. What does Apple recommend: Implementing A or B?

Hi @DTS Engineer thank you for your reply. I have already reviewed the sample code prior to asking my question and it's also worth mentioning that I have implemented various compositional layout configurations with section headers without any problem. However, when I attempted to implement this specific configuration (Kanban), I ran into issues with the headers. To clarify, I don't want the headers pinned, I want them to be on top of the content and scoll with the reste of the content when I scroll up and down, just like they would in a tableView. I would appreciate some insights. Thank you.