How to set up roles and permissions so everyone sees only what they should
CS
The more people on a team, the more it matters who sees what and who can change what. In KoraGate we handle this with a simple role system that you can set up right at the start - and extend later as needed.
Basic roles in a workspace
Every workspace has its owner (who creates it and has full control), and optionally another admin with the same management rights. Regular team members work on the projects and tasks assigned to them, without access to the administration of the whole workspace.
Limited access for a contact person
Not everyone on the team needs to see every project. For people who are only meant to handle one specific thing - such as invoicing or reporting problems - there is a limited role with no access anywhere else.
Who sees which project
Access to projects and folders can be set individually - a project is assigned either to the whole team or only to specific people. This way not everyone on the team has to see everything that happens in the workspace.
Why set it up right at the start
Setting up roles once the team is large and chaotic is always harder than doing it straight away. Even if you are only two or three people now, a few minutes spent setting up roles will pay off when the team grows.