Start by building out your structure

There is 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)

  • Product

  • Engineering

  • Marketing

  • 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 Admins (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

    • Sales

    • Customer Success

  • Marketing

    • Monthly Roundtable

    • Customer Interviews

    • Training & Enablement

Setting collection permissions

By default, all collections are set to public (still have to be a user in your organization, not the general public) so even if a user in your organization is not explicitly 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 amongst teams.

There will be a small handful of meetings that are truly confidential (i.e Leadership meetings, 1:1 meetings, etc.) which you will want a ‘secret’ collection set-up. You will have the option to mark collections ‘secret’ upon creation.

Did this answer your question?