@jayde_colquhoun ,
Are you doing the roll-over for them or are they doing it themselves?
If you're doing it for them, presumably though the API, you should be able to specify which pages to include in the course migration.
If they're doing it, then blocking those three pages is going to be difficult. If they're choosing a complete course copy, then they don't have to select the content and you won't be able to block it.
What you will probably need to do is delete the pages after they're copied.
- You could do is periodically check each course to look for the presence of those three pages. If the pages are there, then you delete them.
- You may be able to use Canvas Data to get at this quickly, but the data is likely a couple of days old by the time you can act on it. That may be acceptable.
- You may be able to use Canvas Live Events and look for the content_migration_completed event to get triggered. This gives you close to real-time notification when someone copies content into a course and then you could use the API to check for the presence of those pages.
That last two items have extra overhead associated with them, but you may already be using Canvas Data or Canvas Live Events. Either of those will be faster than polling the pages in each course to look for the presence of those three.
One thing to watch out for is that if you delete those three pages, you may be breaking links. You know the situation and I don't, just something for someone coming along and reading this to think about.
