Profiles¶
The profile is an entitlement group, each with specific access rights to the database.
So, each user is linked to a profile which defines the data he can see and possibly manage.
Display format
- In the next screens, the name of profiles is displayed in columns.
- Access rights and options are displayed in rows.
- This display format allows to manage easily authorizations for each profile.
Value of Field “Name”
- The value of field “Name” is not the name displayed, but it is a code in the translation table.
- The name displayed at right of the field is the translated name.
- See: Translatable name.
New profile
- The value of field “Name” must be a significant name and must not contain spaces or special characters.
- Ideally, the value of the field should start with “profile” (to be easily identified in the translation table).
Section: Description
| Field | Description |
|---|---|
| Id | Unique Id for the profile. |
| Name | Name of the profile. |
| Profile code | A code that may be internally used when generating emails and alerts. |
| Sort order | Number to define order of display in lists. |
| Closed | Flag to indicate that profile is archived. |
| Description | Complete description of the profile. |
Field: Profile code
- ADM: will designate administrator.
- PL: will designate project leader.
Access modes¶
The access mode defines a combination of rights to read, created, update or delete items. (CRUD RIGHTS)
Each access is defined as scope of visible and/or updatable, that can be, by kind of elements:
- No element: No element is visible and updatable.
- Own elements: Only the elements created by the user.
- Elements he is responsible for: Only the elements the user is responsible for.
- Elements of own project: Only the elements of the projects the user/resource is allocated to.
- All elements on all projects: All elements, whatever the project.
Value of Field “Name”
- The value of field “Name” is not the name displayed, but it is a code in the translation table.
- The name displayed at right of the field is the translated name.
- See: Translatable name.
New access mode
- The value of field “Name” must be a significant name and must not contain spaces or special characters.
- Ideally, the value of the field should start with “accessProfile” (to be easily identified in the translation table).
Section: Description
| Field | Description |
|---|---|
| Id | Unique Id for the access mode. |
| Name | Name of the access mode. |
| Read rights | Scope of visible items |
| Create rights | Scope of possibility to create items. |
| Update rights | Scope of updatable items. |
| Delete rights | Scope of deletable items. |
| Sort order | Number to define order of display in lists |
| Closed | Flag to indicate that access mode is archived. |
| Description | Complete description of the access mode. |
* Required field
Access to forms¶
This table is used to define the access to the selected screen for each profile.
Users belonging to one profile can see the corresponding screen if authorized or not.
How to do
- Screens are grouped as seen therefore in the menu.
- Click on checkbox to permit or revoke access to the screen for a profile.
Access to forms screen
Access to reports¶
This screen allows to define report access for each profile.
Users belonging to a profile can see the corresponding report in the report list.
How to do
- Reports are grouped by report categories.
- Click on checkbox to permit or revoke access to the report for a profile.
Access to reports screen
Access to data (project dependant)¶
This screen allows to set element access mode for each profile.
Allows to define scope of visibility and/or updating of data in elements for users and resources.
This screen is only for the elements reliant on a project.
How to do
- For each element, selected the access mode granted to a profile.
Access to data (Project dependant) screen
Access to data (not project dependant)¶
This screen allows to set for each profile, elements access rights.
Allows to grant access rights (read only or write) to users, to data on specific elements.
This screen is only for the elements not reliant on a project.
How to do
- For each element, select the access rights granted to a profile.
Access to data (Not project dependant) screen
Specific access¶
This screen groups specific functionalities options.
Users belonging to a profile can have access to the application specific functions.
Depending on options of functionality, allows to grant access rights, to define data visibility or to enable or disable option.
How to do
- For each option, select the access granted to a profile.
Specific access screen
Section: Access to resource data
This section allows to:
- Defines who will be able to see and update “real work” for other users.
- Defines who can validate weekly work for resource.
- Defines who have access on diary for resources.
- Defines who, as a resource, can subscribe to survey for users.
Note
Validate real work
- In most cases, it is devoted to project leader.
Section: Work and Cost visibility
- This section defines for each profile the scope of visibility of work and cost data.
Section: Assignment management
- This section defines the visibility and the possibility to edit assignments (on activities or else).
Section: Display specific buttons
- This section defines whether some button will be displayed or not.
Display of combo detail button
- This option defines for each profile whether the button
will be displayed or not, facing every combo list box.
- Through this button, it is possible to select an item and create a new item.
- This button may also be hidden depending on access rights (if the user has no read access to corresponding elements).
Access to checklist
- Defines visibility or not to the checklist (if defined).
Access to jobs lists
- Defines visibility or not to the jobs lists (if defined).
Multiple update
- Defines the possibility or not to change one or more criteria for one or more selected rows at a time
Section: Planning access rights
- This section defines access to planning functionality.
Calculate planning
- This option defines for each profile the ability to calculate planning or not.
Access to resource planning of others
- This option defines for each profile the ability to see the resource planning of others.
Change validated data
- This option defines for each profile the ability to change the validated data or not on details area.
Section: Unlock items
- This section defines for each profile the ability to unlock any document or requirement.
- Otherwise, each user can only unlock the documents and requirements locked by himself.
Section: Reports
- This section defines for each profile the ability to change the resource parameter in reports.
Section: Specific update rights
- Defines for each profile the ability to force delete items.
- Defines for each profile the ability to force close items.
- Defines for each profile the ability to update creation information.
- Defines for each profile the ability to mention or not the components on a ticket.
Section: Limit visibilty to resources
- By profil, allows to restrict or not the number of resources displayed, by organizations or own team, on resource lists.
- By profil, allows to restrict or not the number of resources displayed, by organizations or own team, on resource screen.
Section: Limit visibility to organizations
- By profil, allows to restrict or not the number of organizations displayed, by organizations or own organization, on organization lists.
- By profil, allows to restrict or not the number of organizations displayed, by organizations or own organization, on organization screen.
Translatable name¶
For profiles and access modes, the value of field “Name” is translatable.
The field “Name” in screens Profiles and Access modes is not the name displayed, but it is a code in the translation table.
The name displayed at right of the field is the translated name.
The translated name depends on user language selected in User parameters screen.
Note
- If translated name is displayed between [], then the value of field “Name” is not found in the translation table.
Translation table files
- In ProjeQtOr, a translation table file is defined for each available language.
- The files are named “lang.js” and are localized in a directory named with ISO language code.
- For instance: ../tool/i18n/nls/fr/lang.js.
How to modify the translation file?
- You can edit file “lang.js” to add translation of new value or to modify the existing value translation.
- Or, you can download Excel file named “lang.xls”, available on ProjeQtOr site. You can modify the translation tables of all languages and produce files “lang.js”.
