Building Out your Structure
There's no need to get too crazy or intricate at this stage. Most organizations will start with their broad departments as the parent collection - think of this like creating an org chart. Keep in mind that users can belong to multiple collections.
Company Wide (will include all your employees)
Go to Market
Once you have your parent collections created, you can create children/sub collections within if the department further breaks down into separate teams or even into topics within the team. Don’t worry too much about this during the initial set-up as you can assign Collection Editors (i.e VP’s, Directors, Managers) who can build out their preferred organization with the children collections.
Engineering (Parent Collection)
→ Weekly team meeting (child collection - all users have access)
→ Product Demos
→ Architecture Reviews
→ Tech Talks
Go to Market
→ Weekly Team Meetings
→ Customer Success
→ Monthly Roundtable
→ Customer Interviews
→ Training & Enablement
Setting Collection Permissions
By default, all collections are set to public (this requires being an active user in your organization). Even if a user in your organization isn’t manually added, they can still discover videos in those collections by searching for keywords. Rewatch is a great way to build a culture of trust and learning by keeping your collections open. This will also promote transparency and co-working amongst teams.
There will be a small handful of meetings that are confidential (i.e Leadership meetings, 1:1 meetings, etc.) which you can set up using a ‘secret’ collection. You have the option to set Channel Members as Restricted, which will hide the collection from the Channel Members and will only display to people you manually add as Editors.