Project Management Software Project Manager Software Project Management Project Software
Project Management Software


Home     |     Features Detailed     |     Live Demo     |     Support

Back to Overview

User Accounts & Permissions, Version 2.0

The User Persmission system is based upon roles.

Roles should be established which allow permissions to be edited to best fit your companies needs.

Roles are then assigned to user(s) as required. Once a user has been assigned a role they will be able to log into the system. Until then their account will be listed as "inactive".

After a users role is set then their "permissions mask" may be customized that will allow customization above and beyond that of the roles you have set up.

For example: a role may allow access to the "Companies" Module, but an extra restriction could be applied to the user's account that would limit their view to a single companie's information.

Usage Instructions:

Creating Roles: Click on "System Administration" > "User Roles"

Setting the permissions for "roles" works exactly the same as setting the permissions for a individual accounts, except that when you set permissions for a role you should approach it with a more categorical type of user in mind instead of a persons individual permissions restrictions needs.

A role ID will be generated along with a description, clicking on the padlock option then takes you into the main permission allocation screen.

Permissions are established on a per module basis - as well as a series of groupings as follows:

  • Admin Modules: This grouping refers to all of the modules including the System Administration and User Administration module
  • All Modules: Self-Explanatory
  • Non-Admin Modules: Refers to all modules excluding "System Administration" and the "User Administration" modules.
  • Individual Modules: Allows you to set permissions for your own custom group of modules you choose.

An access level is then defined - selecting either:

  • allow: To permit the following access levels
  • deny: To prevent the following access levels

Individual permission levels are then provided:

  • Access: Allow or deny access to a particular module
  • View :View or read access to the nominated module
  • Add: Permission to add items in the nominated module
  • Edit: Permission to edit items in the nominated module
  • Delete: Permission to delete items in the nominated module


Examples

Example 1

If you would like to set up permissions for a user to have "read-only" access to all the non-administrative modules - you would set the following permissions:

Module Non-Administration Modules

  • Access: allow
  • Access: ticked
  • View: ticked

Example 2

If you wanted to create a user who was able to access the contacts module but nothing else you could create a role:

  • Module: Contacts
  • Access: allow
  • View :ticked

Example 3

If you wanted to modify a particular user's access so that they could not see anything to do with a particular company:

  • Module: Companies
  • Item: Select the particular company that you wish to block
  • Access: deny

Example 4

If you wanted to allow a user to see everything (projects etc.) to do with a specific company:

  • Module: Companies
  • Item: Select the particular company that you wish to block
  • Access: allow

Back to Overview


Remedysoft |   Web Design   |   Web Hosting   |  Graphic Arts  |   Portfolio |   Group Software


Copyright 2004 Remedysoft, Inc. Remedysoft, Inc. (949) 215-9194