Users can only see preloaded content strategy meta data for calendars to which they have access/permission. So if you give a user access to Calendar A, but not Calendar B, then they will only see content strategy meta data for Calendar A throughout the application. This architectural structure maintains separation between calendar data/customizations, and ensures that certain users are only seeing content strategy meta data that pertains to them.
For Example: You're a marketing agency and you're using Divvy to manage content for multiple clients. You've set up a calendar for each client. Each client's marketing manager has been set up as a user on your account. You obviously don't want Client A to see Client B's calendar, content or unique meta data. As long as you're only giving Client A access to their individual calendar, Divvy will hide all other client data from that user. They'll only see their stuff.