Application Settings gets a new design
Many of you have requested a simpler way to enable features in application settings. Enabling a feature often requires the feature to be enabled in the settings page then in the application itself.
Now that we have more feedback from our users on what our default settings should be, we have redesigned the settings page with many features already enabled in topics (in the Discussions app) and tasks lists so you don’t have to enable them in the app.
A quick reminder of when and how to use application settings for a project
Applications settings allow you to enable or disable options in an application. For instance you might decide that no email notifications be sent out from a particular project. You can also decide not to allow all project members to edit a wiki page.
Using applications settings to configure a multi-company project
If you are collaborating with a client in a project, you will probably want to limit the features which can be accessed by users of the customer organisation. For instance they should not be allo wed to deleted files or edit tasks to change due dates. If you are using a wiki for collaborative writing among your company you might find it useful ti prevent users from the customer company from editing wiki pages.
Please bear in mind that application settings work on a per project basis for the two highest plans of GroupCamp Project. In the two lower plans application settings apply for all projects.
Please note also that beyond the company information you can also use the Manager role (in plans Best and Max for GroupCamp Project) to assign higher privileges to a user. The benefit of the Manager role is to allow a user for a single project to have higher privileges without making him or her an administrator which would mean giving that user access to all projects.