About Privileges

"Privileges" are permissions tokens that can be granted to user profiles (a type of group) in the [User Privileges] page. Privileges control all important transactions in ]project-open[ and form the core of the ]po[ permission system.

The page below lists all available privileges, together with their module, package, status and their meaning.

 

 

Companies & Offices

  • Add companies (intranet-core):
    Who is allowed to create new companies in the system? Usually this should be restricted to "Sales" and "Senior Managers".
     
  • Add offices (intranet-core):
    Should be the same as "add companies". "Offices" are part of a company usually, representing the physical office location of the company.
     
  • Edit companies all (intranet-core):
    Privilege to edit all companies in the system, independently of other restrictions.
     
  • Edit internal offices (intranet-core):
    The "internal office" is the location of the "internal company" which represents the organization using ]po[.
     
  • View companies (intranet-core):
    The general permission to see companies in general. A user still needs to be member of the company or enjoy the "view companies all" privilege in order to gain access. Users without "view companies" privilege will not see any company in the system.
     
  • View companies all (intranet-core):
    Privilege to see all companies in the system, independent of other restrictions (being a member of the company).
     
  • View company contacts (intranet-core):
    Privilege to see the customer's contacts of the company.
     
  • View company details (intranet-core - Obsolete):
    Obsolete, should be granted to "Employees".
     
  • View internal offices (intranet-core - Obsolete):
    Obsolete, should be granted to "Employees".
     
  • View offices (intranet-core):
    Generic permission to view office (further restricted by membership of the office). Without this privilege the user won't see any office.
     
  • View offices all (intranet-core):
    Privilege to see all offices in the system, independently of other restrictions.
     
  • View crm tracking ([intranet-crm-tracking] - Non-product):
    Who is allowed to see CRM tracking information? This privilege is not part of the vanilla ]po[ product
     

 

Finance

  • Add budget (intranet-core):
    Privilege to set the project budget in the "project base data". The user also needs write permissions on the project ("edit projects all", or being the PM of the specific project) in order to set the budget
     
  • Add budget hours (intranet-core):
    Similar to "add budget", except that budget hours refer to the budget in terms of numbers of hours, instead of money.
     
  • View budget (intranet-core):
    Similar to "add budget", except that this is the read permission.
     
  • View budget hours (intranet-core):
    Simiar to "view budget", except that this is for the budget hours, instead of money.
     
  • Add costs (intranet-cost):
    Permission to add cost items in general. Should be same as "Add finance"
     
  • Add finance (intranet-cost):
    Generic permission to enter any financial or cost items (further restricted by other permissions). Should be the same as "Add costs".
     
  • Fi read all (intranet-cost):
    Parent privilege for all other "fi read *" privileges (a user will receive all other privileges if this has been granted). The "fi xxx yyy" privilege family allows the administrator to determine which user profiles are allowed to read or write certain types of financial objects. This is rarely used in ]po[, but allows to build workflows for the management of financial documents (Sales creates quotes, while Accounting creates the corresponding invoices etc.).
     
  • Fi read bills (intranet-cost):
    Please see "fi read all". Provider bills represent invoices received from external providers.
     
  • Fi read delivery notes (intranet-cost):
    Please see "fi read all". A Delivery Note is a financial document sent to a customer before sending the actual invoice. Delivery notes are not used by the profit & loss calculation in ]po[.
     
  • Fi read expense bundles (intranet-cost):
    Please see "fi read all". Expense Bundles are grouped travel expenses, please see the expense package documentation for details.
     
  • Fi read expense items (intranet-cost):
    Please see "fi read all". Expense Items represent individual receipts including taxi or restaurant bills.
     
  • Fi read expense reports (intranet-cost - Obsolete):
    Please see "fi read all". This privilege should no be present in your system.
     
  • Fi read interco invoices (intranet-cost):
    Please see "fi read all". Interco Invoices are financial documents exchanged between multiple divisions of a single company.
     
  • Fi read interco quotes (intranet-cost):
    Please see "fi read interco quotes". Interco Quotes are financial documents exchanged between multiple divisions of a single company.
     
  • Fi read invoices (intranet-cost):
    Please see "fi read all". Invoices are sent to a customer after the end of a project in order to request payment.
     
  • Fi read pos (intranet-cost):
    Please see "fi read all". Purchase Orders (PO's) are sent to external providers at the beginning of a project in order to ask them to provide services.
     
  • Fi read quotes (intranet-cost):
    Please see "fi read all". Quotes are sent to a customer to inform about the approximate price of a project.
     
  • Fi read repeatings (intranet-cost):
    Please see "fi read all". Repeating costs represent employee salaries and other periodic cost items. However, these items are currently not used in ]po[.
     
  • Fi read timesheets (intranet-cost):
    Please see "fi read all". "Timesheets" refer to timesheet costs.
     
  • Fi view internal rates (intranet-cost - Obsolete(?)):
    Determines if a user can see an employee's internal rates. The privilege is currently used in several reports, but is not (yet, as of 2014-04-15) used to control the visibility of the "hourly cost" field in the employee's portlet.
     
  • Fi write bills (intranet-cost):
    Please see "fi read bills".
     
  • Fi write all (intranet-cost):
    Please see "fi read all". Parent privilege for all other "fi write *" privileges
     
  • Fi write delivery notes (intranet-cost):
    Please see "fi read delivery notes".
     
  • Fi write expense bundles (intranet-cost):
    Please see "fi read expense bundles".
     
  • Fi write expense items (intranet-cost):
    Please see "fi read expense items".
     
  • Fi write expense reports (intranet-cost - Obsolete):
    Obsolete
     
  • Fi write interco quotes (intranet-cost):
    Please see "fi read interco quotes".
     
  • Fi write interco invoices (intranet-cost):
    Please see "fi read interco invoices".
     
  • Fi write invoices (intranet-cost):
    Please see "fi read invoices".
     
  • Fi write pos (intranet-cost):
    Please see "fi read pos".
     
  • Fi write quotes (intranet-cost):
    Please see "fi read quotes".
     
  • Fi write repeatings (intranet-cost):
    Please see "fi read repeatings".
     
  • Fi write timesheets (intranet-cost):
    Please see "fi read timesheets". Writing timesheet costs actually doesn't make sense (because timesheet costs are created automatically from logged hours), so changes of this privilege will not have any effect.
     
  • View costs (intranet-cost):
    Should be the same as "view finance"
     
  • View finance (intranet-cost):
    Generic permission to enter into the finance module. Should be the same as "view costs".
     
  • Edit projects dept (intranet-cost-center):
    Edit Department Projects - used for enterprise "cost center permissions"
     
  • View projects dept (intranet-cost-center):
    View Department Projects - used for enterprise "cost center permissions"
     
  • Add expense bundle (intranet-expenses):
    Privilege to create new expense bundles. This can be granted to all users in the system, who also are allowed to "add expenses" because of the self-service features of the intranet-expenses package.
     
  • Add expense invoice (intranet-expenses - Obsolete):
    Obsolete
     
  • Add expenses (intranet-expenses):
    Privilege to create new expense items (representing taxi or restaurant bills etc).
     
  • Edit bundled expense items (intranet-expenses):
    Privilege allowing a user to modify expense bundles even after submitting them. This is an exceptional situation. The privilege can be useful for HR staff to fix errors in expense bundles.
     
  • View expenses (intranet-expenses):
    a user is able to view the expenses of projects they are associated with
     
  • View expenses all (intranet-expenses):
    a user is able to view the expenses of all projects on the system regardless of whether or not they a member of the project
     
  • Add invoices (intranet-invoices):
    Privilege allowing a user to create "financial documents" of any type. The "fi write xxx" privilege family controls the types of financial documents that can be created. Without "add invoices" no document can be created.
     
  • View invoices (intranet-invoices):
    refers to the generic financial document type family which includes purchase orders, quotes, bills...
     
  • Add payments (intranet-payments):
    Privilege to add payment items in general. The user also needs to have write permission on the finanancial document (invoice or provider bill).
     
  • View payments (intranet-payments):
    Privilege to see payments. The user also needs to have read permission on the finanancial document (invoice or provider bill).
     

ITSM

  • Add conf items (intranet-confdb):
    Privilege to add additional configuration items to the ConfDB.
     
  • View conf items (intranet-confdb):
    Base privilege for reading configuration items. Without this privilege a user will not be able to see any ConfItem, even if he is owner or member of a conf item.
     
  • View conf items all (intranet-confdb):
    Privilege to see all configuration items independently of other restrictions.
     
  • Add tickets (intranet-helpdesk):
    Privilege to create new helpdesk tickets of various types. You can grant this privilege to all users, because ticket creation is controlled by SLAs using a strong self-service mechanism.
     
  • Add tickets for customers (intranet-helpdesk):
    Privilege for helpdesk staff to create helpdesk tickets in the name of customers.
     
  • Edit ticket status (intranet-helpdesk):
    Privilege to edit the status of a ticket, even if it is controlled by a workflow.
     
  • View tickets all (intranet-helpdesk):
    Privilege to read all tickets, independenly on other restrictions.
     

Projects

  • Add baselines (intranet-baseline):
    Privilege to create new [project baselines] (approved versions of a project plan).
     
  • Del baselines (intranet-baseline):
    Privilege to delete [baselines]. This privilege is normally reserved for administrators in order to delete accidentally created baselines.
     
  • Add projects (intranet-core):
    Privilege to create new projects. This is usually reserved to project managers or members of the steering committee, because projects can't be deleted afterwards (only set to status "deleted", but not completely removed from the database).
     
  • Edit project basedata (intranet-core):
    Specific privilege for editing the project name, start- and end date and other core data. Normally, Project Managers are allowed to do this, but sometimes PMs should not be able to modify project parameters once they are defined.
     
  • Edit project status (intranet-core):
    Privilege to allow users to edit the status of a project event though it is under workflow control.
     
  • Edit projects all (intranet-core):
    Privilege to modify all projects, independenly on other restrictions.
     
  • View project members (intranet-core - Obsolete):
    Obsolete
     
  • View projects all (intranet-core):
    Privilege to read all projects, independenly on other restrictions.
     
  • View projects history (intranet-core):
    Privilege to allow an unprivileged user (typically customer or freelancer) to see their projects that have already been closed.
     
  • View gantt proj detail (intranet-ganttproject - Obsolete):
    Obsolete
     
  • Add timesheet tasks (intranet-timesheet2-tasks):
    Privilege to allow a user with write permission on a project to add a new timesheet task.
     
  • Edit timesheet task completion (intranet-timesheet2-tasks):
    Privilege that determines if a user has the right to update the %completed of a timesheet tasks to which he is assigned as a normal member.
    The "Tasks" tab of a project uses this privilege in order to show an input field for the %completed field in tasks where the user is assigned. In the same way the /intranet-timesheet2-tasks/www/task-action.tcl page recognizes the privilege to allow for task updates.
    In the future, the timesheet entry page will allow time logging users to update the same field.
     
  • Edit timesheet task estimates (intranet-timesheet2-tasks):
    Privilege that determines if a user with write permission on a project should be able to edit estimated and billable hours for timesheet tasks. Currently (2013-12-03) this privilege only applies to the Web GUI, while users can modify the estimates by uploading a MS-Project plan into the project.
     
  • View reports all (intranet-reporting):
    Allows a user to see all reports and all [reporting indicators] in the system.
     
  • view timesheet task billables (intranet-timesheet2-tasks - Obsolete):
    Will be replaced with "view timesheet task estimates".
     
  • view timesheet task estimates (intranet-timesheet2-tasks):
    Privilege that determines if a user has the right to read the estimated time per timesheet task.
     

System

  • Admin categories (intranet-core - Obsolete):
    Not used anymore
     
  • Admin (acs-kernel):
    The "parent" of all privileges - Used internally by the system only
     
  • Annotate (acs-kernel):
    Generic system privilege - used internally by ]po[ on a per-object base.
     
  • Create (acs-kernel):
    Generic system privilege - used internally by ]po[ on a per-object base.
     
  • Delete (acs-kernel):
    Generic system privilege - used internally by ]po[ on a per-object base.
     
  • Read (acs-kernel):
    Generic system privilege - used internally by ]po[ on a per-object base.
     
  • View (acs-kernel):
    Generic system privilege - used internally by ]po[ on a per-object base.
     
  • Write (acs-kernel):
    Generic system privilege - used internally by ]po[ on a per-object base.
     
  • Read private data (intranet-core - Obsolete):
    Used in package acs-tcl, but not used anymore
     
  • Require manual login (intranet-core):
    Used by "auto-login" functionality - Allows to specify that certain profiles (i.e. Accounting, Senior Managers) are not allowed to use auto-login for security reasons.
     
  • Add materials (intranet-material):
    Materials are normally only managed by system administrators, so these privileges don't really apply, unless a company needs to maintain frequently changing materials
     
  • View materials (intranet-material):
    Please see "add materials".
     
  • Add reports (intranet-reporting):
    Privilege that allows non-administrators to create new reports and reporting indicators.
     
  • Wf cancel case (intranet-workflow):
    Privilege to override normal workflow operations. Canceling a WF case frees the case, so that other users can take it on. Normally, only system administrators should perform this action.
     
  • Wf reassign tasks (intranet-workflow):
    Please see "wf cancel case". Reassigning a case means adding additional potential assignees to a WF case, that in turn will have the right to start and execute the case.
     
  • Wf suspend case (intranet-workflow - Obsolete):
    Please see "wf cancel case". Suspending a case is currently not used.
     

Timesheet & Absences

  • Add absences (intranet-timesheet2):
    Permission (no obligation here) to log absences such as vacations, travel time etc. This may also make sense for freelancers, as to indicate their availability.Add hours all
     
  • Add absences for group (intranet-timesheet2):
    Allows HR or other privileged users to create bank holidays that are valid for entire groups. Together with the future (2013-12-03) extension of groups per office, this privilege allows administrative users to maintain a holiday calendar across multiple countries or regions with heterogenous bank holidays.
     
  • Add hours (intranet-timesheet2):
    Permission (and obligation!) to log hours. You normally allow this only for employees and people on your company's payroll
     
  • Add hours all (intranet-timesheet2):
    Allows users to log hours for other users. This is useful in cases where administrative staff logs the hours for employees.
     
  • Add hours direct reports (intranet-timesheet2):
    Privilege to all users to add hours in the name of their direct reports. Direct reports are users that have the current user as "supervisor", or the members of the department of a department's manager.
     
  • Add hours for subordinates (intranet-timesheet2 - Obsolete):
    Renamed to "Add hours direct reports"
     
  • Edit absence status (intranet-timesheet2):
    Privilege that allows users to edit the status of an absence even though it is controlled by a workflow.
     
  • Edit hours all (intranet-timesheet2):
    Privilege to allow modification of all logged hours in the system
     
  • View absences (intranet-timesheet2 - Incomplete):
    Privilege to allow users to read absences. Without this privilege a user won't see any absence.
     
  • View absences all (intranet-timesheet2):
    Privilege to allow users to see the absences of all users in the system. This is useful for HR, Accounting and administrative staff.
     
  • View absences direct reports (intranet-timesheet2):
    Privilege to see the absences of a user's direct reports. Direct reports are users that have the current user as "supervisor", or the members of the department of a department's manager.
     
  • View hours all (intranet-timesheet2):
    Privilege to allow users to see the logged timesheet hours of all users in the system.
     
  • View timesheet tasks (intranet-timesheet2-tasks):
    Privilege to allow users to see timesheet tasks. Without this privilege a user won't see any timesheet tasks.
     
  • View timesheet tasks all (intranet-timesheet2-tasks - Incomplete?):
    Privilege to allow users to see all timesheet tasks in the system.
     
  • View timesheet conf all (intranet-timesheet2-workflow):
    Privilege to allow users to see all timesheet confirmation objects in the system. These objects are used by the timesheet workflow to confirm user time sheets.
     

Translation

  • Add freelance rfqs (intranet-freelance-rfqs):
    Privilege to allow the creation of new RFQs.
     
  • Add trans rfqs (intranet-freelance-rfqs - Obsolete):
    Replaced by "add freelance rfqs".
     
  • View freelance rfqs (intranet-freelance-rfqs):
    Privilege to allow read permission to all RFQs in the system.
     
  • View trans rfqs ([intranet-rfqs]):
    Privilege to allow read permission to RFQs in the system.
     
  • View trans rfqs all ([intranet_rfqs]):
    Privilege to allow read permission to all RFQs in the system.
     
  • View trans project detail (intranet-translation - Obsolete):
    Obsolete
     
  • View trans task matrix (intranet-translation):
    Privilege to see the matrix of translation tasks
     
  • View trans task status (intranet-translation - Obsolete):
    Obsolete
     
  • View trans tasks (intranet-translation):
    Privilege to see translation tasks
     
  • Add trans quality (intranet-trans-quality):
    Privilege to add translation quality reports
     
  • View trans quality (intranet-trans-quality):
    Privilege to see translation quality reports for projects where the user has read permission.
     

Users

  • Add users (intranet-core):
    Generic permission to add users. The profile of the users to be created are limited by "User Matrix" permissions
     
  • View user regs (intranet-core):
    View User Registrations in the "Admin" page
     
  • View users (intranet-core):
    Generic read permission on users. Without this privilege the user won't see any other users in the system.
     
  • Add freelance skillconfs (intranet-freelance):
    adding a new configuration for a freelancer
     
  • Add freelance skills (intranet-freelance):
    Privilege to add skills to a user. The user also will need write permission on the target user, as defined by the "user matrix".
     
  • View freelance skillconfs (intranet-freelance - Obsolete(?)):
    Obsolete
     
  • View freelance skills (intranet-freelance):
    General read permission on skills. Without this privilege, a user won't see any skill information in the system.
     
  • View hr (intranet-hr):
    Generic permission to view and edit HR information
     

 

Event Management

  • Add events ([intranet-events]):
    Privilege to add new events.
     
  • Edit events all ([intranet-events]):
    Privilege to edit all events, independently of other restrictions.
     
  • View events all ([intranet-events]):
    Privilege to see all events, independently of other restrictions.
     

 

 

Collaboration

  • Cal item create (calendar - Obsolete):
    Calendar permissions
     
  • Cal item delete (calendar - Obsolete):
    Calendar permissions
     
  • Cal item invite (calendar - Obsolete):
    Calendar permissions
     
  • Cal item read (calendar - Obsolete):
    Calendar permissions
     
  • Cal item write (calendar - Obsolete):
    Calendar permissions
     
  • Calendar Admin (calendar - Obsolete):
    Calendar permissions
     
  • Calendar create (calendar - Obsolete):
    Calendar permissions
     
  • Calendar delete (calendar - Obsolete):
    Calendar permissions
     
  • Calendar on (calendar - Obsolete):
    Calendar permissions
     
  • Calendar read (calendar - Obsolete):
    Calendar permissions
     
  • Calendar show (calendar - Obsolete):
    Calendar permissions
     
  • Calendar write (calendar - Obsolete):
    Calendar permissions
     
  • Category admin ([categories] - Obsolete):
    Permissions on OpenACS category trees (not the same as ]po[ categories): OpenACS categories are only used in XoWiki where changes are performed by an administrator
     
  • Category tree grant permissions ([categories] - Obsolete):
    See Category admin
     
  • Category tree read ([categories] - Obsolete):
    See Category admin
     
  • Category tree write ([categories] - Obsolete):
    See Category admin
     
  • Chat ban (chat - Obsolete):
    Chat room permissions - this packages is currently not used as part of ]po[.
     
  • Chat moderator (chat - Obsolete):
    Chat room permissions
     
  • Chat moderator revoke (chat - Obsolete):
    Chat room permissions
     
  • Chat read (chat - Obsolete):
    Chat room permissions
     
  • Chat room admin (chat - Obsolete):
    Chat room permissions
     
  • Chat room create (chat - Obsolete):
    Chat room permissions
     
  • Chat room delete (chat - Obsolete):
    Chat room permissions
     
  • Chat room edit (chat - Obsolete):
    Chat room permissions
     
  • Chat room view (chat - Obsolete):
    Chat room permissions
     
  • Chat transcript create (chat - Obsolete):
    Chat room permissions
     
  • Chat transcript delete (chat - Obsolete):
    Chat room permissions
     
  • Chat transcript edit (chat - Obsolete):
    Chat room permissions
     
  • Chat transcript view (chat - Obsolete):
    Chat room permissions
     
  • Chat user (chat - Obsolete):
    Chat room permissions
     
  • Chat user ban (chat - Obsolete):
    Chat room permissions
     
  • Chat user grant (chat - Obsolete):
    Chat room permissions
     
  • Chat user revoke (chat - Obsolete):
    Chat room permissions
     
  • Chat user unban (chat - Obsolete):
    Chat room permissions
     
  • Chat write (chat - Obsolete):
    Chat room permissions
     
  • Cm admin ([cms] - Obsolete):
    Content Management permissions - this packages is currently not used as part of ]po[.
     
  • Cm examine ([cms] - Obsolete):
    Content Management permissions
     
  • Cm item worflow ([cms] - Obsolete):
    Content Management permissions
     
  • Cm perm ([cms] - Obsolete):
    Content Management permissions
     
  • Cm perm admin ([cms] - Obsolete):
    Content Management permissions
     
  • Cm read ([cms] - Obsolete):
    Content Management permissions
     
  • Cm relate ([cms] - Obsolete):
    Content Management permissions
     
  • Cm root ([cms] - Obsolete):
    Content Management permissions
     
  • Cm write ([cms] - Obsolete):
    Content Management permissions
     
  • General comments create ([general-comments]):
    The "general-comments" package allows users to add comments to XoWiki pages.
     
  • Fs root admin (intranet-filestorage):
    Parent of "fs root *" privileges (admin inclues read, write and view privileges)
     
  • Fs root read (intranet-filestorage):
    Is the user allowed to read the root of a intranet-filestorage folder by default?
     
  • Fs root view (intranet-filestorage):
    Is the user allowed to view the root of a intranet-filestorage folder by default? "View" means to be able to see the elements of the FS, but not to access the contents of the elements.
     
  • Fs root write (intranet-filestorage):
    Is the user allowed to write the root of a intranet-filestorage folder by default?
     
  • View filestorage sales (intranet-filestorage - Obsolete):
    The "sales file storage" is a special file storage associated with projects that may be hosted by an extra secure server. This ]po[ features is not actively supported anymore.
     
  • Add topic assignee (intranet-forum):
    Please see "add topic client"
     
  • Add topic client (intranet-forum):
    Is the user allowed to create a discussion topic with visibility for a customer? The "intranet-filestorage" (please see package description) allows for discussions that cross organizational boundaries. You can control how providers, in-house staff and customer communicate with each other.
     
  • Add topic group (intranet-forum):
    Please see "add topic client". "Group" refers to the member of the project.
     
  • Add topic noncli (intranet-forum):
    Please see "add topic client". "Noncli" refers to in-house staff + providers.
     
  • Add topic pm (intranet-forum):
    Please see "add topic client". "PM" refers to the project manager - everybody should have this privilege, because the PM can play the role of a moderator.
     
  • Add topic public (intranet-forum):
    Please see "add topic client". "Public" refers to the entire system. Only the Administrators have this permission, as the message
     
  • Add topic staff (intranet-forum):
    Please see "add topic client"
     
  • View topics (intranet-forum):
    Generic permission to view topics (further restricted by topic scope)
     
  • View topics all (intranet-forum):
    Privilege to read all topics in the system (override other restrictions)
     
  • Add ideas (intranet-idea-management):
    Privilege to add new ideas.
     
  • Edit idea status (intranet-idea-management):
    Users normally should not modify the status of ideas controlled by a workflow, because it is the WF that modifies the status.
     
  • View ideas all (intranet-idea-management):
    Privilege to see all ideas in the system, regardless of other restrictions
     
  • View notes (intranet-notes):
    Privilege to see notes (i.e. URLs, emails or names added to an object). Notes is a tutorial package, allowing developers to learn about ]po[ development.
     
  • Search intranet (intranet-search-pg):
    General permission to search the Intranet. All returned hits are further filtered according to the users permissions.
     
  • Survsimp admin survey (intranet-simple-survey):
    Simple Survey allows to build custom "forms" with survey questions. "Admin" is the parent of all other privileges. Usually "survey admins" are granted this privilege which includes all the other ones.
     
  • Survsimp create survey (intranet-simple-survey):
    Please see "survsimp admin survey".
     
  • Survsimp create question (intranet-simple-survey):
    Please see "survsimp admin survey".
     
  • Survsimp delete question (intranet-simple-survey):
    Please see "survsimp admin survey".
     
  • Survsimp delete survey (intranet-simple-survey):
    Please see "survsimp admin survey".
     
  • Survsimp modify question (intranet-simple-survey):
    Please see "survsimp admin survey".
     
  • Survsimp modify survey (intranet-simple-survey):
    Please see "survsimp admin survey".
     
  • Survsimp take survey (intranet-simple-survey):
    Please see "survsimp admin survey". You can gant this privilege to everybody (profile: "registered users" in general.
     
  Contact Us
  Project Open Business Solutions S.L.

Calle Aprestadora 19, 12o-2a

E-08907 Hospitalet de Llobregat (Barcelona)

 Tel Europe: +34 932 202 088
 Tel US: +1 415 429 5995
 Mail: info@project-open.com