System Admin Module

System Admin

Module Overview

The System Administration in web2Project is where you control many aspects of the systems core functionality and general maintenance.

System Admin List (index)

The System Administrations main page consists of four (4) main categories highlighted in bold:

Language Management




System Admin Translation Management (translate)

You can change the default language of web2Project with the Translation Management table to meet your own individual or company’s needs.

In order to install a translation you need to have administrative privileges and access to the server’s web2Project directory.

Additional language packs are mostly a user supported contribution. When available you can download language packages to save yourself some time or when not available you can create your own.

System Admin System Configuration - the engine under the hood.

System Admin System Configuration 1 (systemconfig 1)

Access the system configuration via the system administration menu item. For additional help as you configure the system simply hover your mouse over the (i) icon in web2Project to view a tool tip for that option.

System Admin System Configuration 2 (systemconfig 2)

System Admin System Configuration 3 (systemconfig 3)

System Admin Default User Preferences (addeditpref)

Setting the default user preferences dictates what people see and can do by default when creating a new account. It is the same is setting the individual user preferences after a user has an account.

By default when a new user registers for an account, they will adobt the default user preferences you specify here, however, you can change preferences for each user under the user administration preferences

From this page you can:

System Admin System Lookup Keys (keys)

System Lookup Keys and System System Lookup values are used in combination when a lookup list or custom field or pre-set selection field is used.

Warning: Unless you are a programmer we strongly recommend that you do not modify this section!

System Admin System Lookup Values (syskeys)

System Lookup Values are used in combination when a lookup list or custom field or pre-set selection field is used. This includes standard drop down listings and tabs such as the projects list page.

For example the project list page tabs are referenced in the System Lookup Values as “ProjectStatus”

0|Not Defined 1|Proposed 2|In Planning 3|In Progress 4|On Hold 5|Complete 6|Template

Changing these values will change the tabs according but note: You can not modify the All Projects, Archived, or Gantt tabs as these are hardwired by default.

It is strongly recommended you do not modify these settings unless you are comfortable with what you’re doing. Modifying the wrong system values could have undesired results.

System Admin Custom Field Editor List (custom_field_editor)

The Custom Field editor allows you to add custom fields to areas such as Projects, Task, Companies, and Calendar without needing to know programming.

System Admin Custom Field Editor Add/Edit (custom_field_addedit)

To add custom fields click on the custom field editor link in the system administration

After you add your custom field you’ll see it appear on the list under the module you specified, in addition to the editor of the module.

System Admin Billing Code (billingcode)

You can use billing codes to track cost in respect to time, mainly used when creating a task log for example.

Billing codes are usually an accounting code

Value is the dollar amount

Description can be the same as the code or something to easily identify.

When you store billing codes, they will be visible in the task logs cost code dropdown.

System Admin View Modules (viewmods)

The view modules section allows you to view, edit, delete, change order of appearance and configure modules.

Modules are generally located in the web2Project/Modules folder and appear in this table.

The first column lets you move a module up or down. This will also have an effect on how the module appears in the menu when active or visible.

Show or hide a module by clicking on the Menu Status columns Hidden or Visible text.

Roles are an asset to the comprehensive permissions system built into web2Project. You can specify roles for specific types of users or users groups to allow or deny access to various features within web2Project.

Roles make it easier to apply permissions to a user or set of users rather than applying individual permissions to each user.

To create a user role for a group of users click on the User Roles link under the system administration menu.

You will see a table.

Field Description
Icons Edit-Modify-Delete
Role ID ID of Role
Description Description of Role

To create a new role give the role an ID in the textbox located at the bottom of the second column. Then type a brief description in the second textbox located last in the description column.

After you create a role, click on the lock icon to add permissions to it.

Visit the permissions page for more information.

System Admin Permissions Result Table (acls_view)

The permissions result table gives a more comprehensive look into the permissions for each. You can filter the view by user, module, or by action.

When you visit the page and select a filter it will display a table.

Field User ID User User Name Module Item Item Name Action Allow ACL_ID
Description Automatic ID by System Login ID Actual Name Name of Module ID If Applicable Name of Item See Permissions Allow(1) Deny (0) ID of the ACL

Configure web2project to use Active Directory accounts

Create a service Account, the account only needs to be a member of the domain users group in active directory in order to search ldap.

Go to the System Configuration of the Systems Admin page of web2project.

Under “User Authentication Settings”

User Authentication Method: LDAP (Change to LDAP)

Under “Users”

Activate External User Creation: Deselect the checkbox (This is not required)

Under “LDAP Settings” LDAP also allows standard login: (check the box)

LDAP Base DN : DC= peanutbutter,DC=com This would be your domain name in my example I used

LDAP Host: Use the IP address or fully qualified domain controller name. example:

LDAP Port: 389 (This default port used by AD)

LDAP Search User Password: Password for the user entered below

LDAP Search User: Use the user you created as the service account. You must use the full AD path to that user account. Be sure to use OU for an organizational unit and CN for a Container, CN would be used if your users were in the default “User” folder created when you install Active Directory.

LDAP Search User : CN=project,CN=Users,DC=peanutbutter,DC=com

LDAP User Filter : sAMAccountName=%USERNAME%

LDAP Version: 3

Now you can use your active directory usernames and password to login to web2project.

System Admin Import Contact (contacts_ldap)

The import contacts lets you import contacts from an LDAP Directory. This is more of an IT function and documentation will be forthcoming.