OK, that is what I thought you were doing. The issue is you made the contents of the page into a Component instead of using the "Share Loop component" menu option of the page in the left nav. So:
- Make your meeting page and convert just the Action Items into a Component.
- Copy the Action Items Component into the leadership pages as needed using the "Copy component" button in the upper right of the Action Items.
- Use the "Duplicate" menu option of the page for each meeting. Change the page name as needed for the new meeting. This creates a new file that is wholly independent of the original, except for the Action Items, which are still the same Component file.
- Use the Share Loop component menu option in the left nave to share a meeting page in an email/invite or Teams chat as needed. When you use this function, it only affects that instance of the page. If you use the Duplicate function the new page will not be tied to the original. This is the critical part, if you make the contents of the page into a Component, every place you "copy" the Component will actually be the same file. Let's say you copy that Component into a meeting invite and set the agenda, then copy it into a different meeting, both meetings will have the same agenda. If you change the agenda items in the second meeting, they will also change on the first.
As you see in the meeting invite below (I zoomed out to reduce size) the whole page shows as a Component with the Action Items as a nested Component. This works because a page is already a file. When you use the "Share Loop component", you're really just using the Loop function in the pasted location to allow collaboration. When you create a Component from the contents of a page you are creating a new file that can ONLY be a Component. The "Copy component" button is horribly named. You are not copying the component in the sense of creating a new instance, you are just copying the URL, the same as you would if you copied a page address in a browser.