Hi @MariahBirgen - some good responses for you here from earlier replies.
We have multiple use cases where we want to 'mirror' content across courses, and we do this by having discipline, school or faculty pages that hold the content as pages or files.
There are two approaches to ensuring that students can access this central content:-
1. By making sure all students are bulk enrolled in the repository site (in our case by award code in either a community site or delivery code in a zero credit delivery site)
2. By making the repository site 'institutional access' - the downside of this is that because students are not enrolled in the repository site you will weaken or remove the analytics stats on use
In terms of how this is then presented in the destination Canvas courses, there are two (or more) options
A. The repository course asset is added as an external link either as a moduleitem or within the RCE (in the repository site a file needs to be 'available to anyone with the link')
B. The content is iframed into a page within the destination course
iframing results with Canvas within Canvas, and students can end up navigating down a rabbit hole - it would be useful to be able to switch the normal menus off. We had considered going back to pdfs etc. on the basis that this would be less technical and aesthetic overload, however testing reveals that when files are updated with a new version, at the time of testing the file link breaks in the app (it seems to work everywhere else). There have been some tangental fixes affecting image storage recently which might or might not have fixed this.
Notwithstanding the point that your use case is (as identified by other contributors) facilitated by the Canvas profile page, I go back to something I mentioned on the forum a while ago, which is that Instructure are missing a trick in not making it more straightforward to reuse Canvas RCE based and other content from a common source in a more elegant way than iframing allows.