Permission denied – How roles and permissions work in aC 1.0

There are two groups of users in any activeCollab setup:

1. Members of owner company
2. Members of client companies

Any member of the “owner company” has a role he or she plays in the system. By default activeCollab ships with four predefined roles:

1. Administrator
2. Project manager
3. Contractor
4. Company member

Every role has its own set of permissions. For instance, project managers don’t require access to administration but they certainly need to be able to start new projects and manage existing ones. On the other hand, members and contractors are just involved in the project. They don't do any project management or administration so they don't require those permissions.

You are not limited to predefined roles. Setting up and managing roles is easy thanks to the role management tool in the administration section. The roles management tool lets you define new roles, see who has specific roles, alter them.

Note: In order to make the delete option available there must not be any members with that role assigned.

Clients have a simpified role system.

1. Company manager
2. Member
   

Every client company needs to have at least a company manager. The manager has some extra permissions, for example he or she can alter company details and manage accounts of other members. If the client company logo changes or one of their members changes his or her email address they can handle the change themselves without the need to contact your stuff and distract them from their regular duties.

The number of users the client company manager can create is limited with the "Max. members" property. It can also be set to 0 in order to remove any limitations (the manager will be able to add as many users as needed).

Note: If you decide to let your clients create new projects in the system you just need to open - Administration / Settings / General settings, and make sure that the option "Let clients start new projects" is enabled.

While roles define permissions on a system level there are also project level permissions that let you specify what users can and cannot do per project – giving you more flexibility when needed.

So, now you know how roles and permissions work. We dare you to find a flaw in the system! Remember, if you do “crack the code” – let us know!