When you're working on a project, you might not want everyone to be able to see everything in it.
That's why activeCollab requires every user to have an account and a defined role which determines what the user can see and access inside your activeCollab setup. By correctly using the roles and permissions functionality though, you can relax knowing that any confidential project data will not be disclosed to anyone it shouldn't.
activeCollab has two groups of permissions that control who can access certain parts of the system:
System Permissions lets you configure what a user can do in the system - eg. access administration controls, manage people or projects, create and access assignment filters, etc.
Project Permissions enables you to give or restrict access to specific sections and features inside a project. One great thing about project permissions is that they work on a per-project basis. For example, you may want a user to be able to start new Discussions in one project, but you don’t want to give them access to Discussions in another project.
Permissions are controlled in the Roles area, where System Roles define system-level permissions and Project Roles define project-level permissions. To manage roles, go to the Administration panel, and select the Roles tool in System section. You can learn more about Roles management in the Roles and Permissions article of our Administrator's Guide.
Each user can only have one System Role that controls what he or she can do on a system level. This role is set when the user account is created and can be changed at any time on the Profile page of the given user in the Company and Role option.
Unlike system roles, each user can have as many different project roles as projects they are working on (though only one Project Role per project). The Project role is set when the user is added to the project, via the People tab.