Permissions: team, spaces and users
For each user to have a different experience, it is necessary to play with the concept of teams.
Let's assume that you want to build an experience within Skore for your Customer Success team as well as the onboarding use case for your Sales Team, combined with corporate university and knowledge hub.
How would you do that? Read until the end and we'll show you the best way to do this.
Before we begin, you need to know what each use case is. We have a dedicated article for this, with several tips, but to save us a little time, I will tell you here briefly:
Onboarding: Onboarding is the experience dedicated to the new employee of the company - everything he or she needs to know about the company, their work tools and focal points should be concentrated in the onboarding.
Corporate University: This is the use case dedicated to what we call ongoing learning. It is the occasion when the training team makes available several knowledge trails for the user to freely enjoy. Examples of university materials are leadership and management courses, in-depth courses on a company work tool, advanced Excel training, and others that can improve employee productivity on day-to-day tasks.
Knowledge Hub: This is the use case for informational content. Companies leave user-friendly content and internal information such as company manuals, transportation vouchers, refund requests, spreadsheet templates, general company information, and it is also the use case which uses the expert extensively as being the person responsible for including market-related content or articles that he or she thinks is important to share with the team, forming a large liquid knowledge hub.
Ok, now that you already know the use cases, let's use this information to explain the contents separation focused on the initial example of Sales and Customer Success teams training.
You only have one Skore, but you can add as many spaces as you want.
With that in mind, let's build the first spaces on the management area focused on the Onboarding use case:
Create a space each for: (a) Customer Success Onboarding, (b) Sales Team Onboarding, and (c) company's general information.
Once done, it is understood that the contents that will be in the Customer Success space will only be available for the users who work in that area, while the contents that concern the Sales team are only for the Sales team. The general contents of the company don't have a specific audience.
Thus, the correct thing to do is:
- Create a team named 'Customer Success' and allow the Customer Success onboarding space only for this team;
- Create a team called 'Sales Team' and allow the Sales team onboarding space for this team only.
This prevents both the Customer Success and Sales team from seeing information that is not relevant to them on the platform, leaving the general information space with public permission, so that everyone can freely access that information.
Still in Onboarding, once you have included all the materials, you can organize them on the platform. To make sure that the contents are in a specific order to the user, assemble a mission.
The number of missions per audience is unlimited. You can make as many missions as you want for the same audience, different audiences, or you can also make them public.
Once you've created your missions (tracks) for the Onboarding use case, feel free to create even more missions for the Corporate University use case.
Remember that if the subject is specific to only one team, you can assign that space to this team only, hiding the information from other platform users. The team in which the user is in must be the same as the space allowed for the user to see the content.
Here's an article about managing users and how to include them in teams.
And don't forget:
If you set up a mission for the Customer Success team for example, make sure that the following points were followed so that there is no problem for the student to view the content:
Private mission for one audience or more:
- The mission is set for team A;
- The space(s) from which the mission presents contents are hidden and either public or allowed for team A to access;
- The user is in team A.
In that way, your team won't have any trouble to access the content!
If you have questions, please let us know. =)