You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Chris Howe (JIRA)" <ji...@apache.org> on 2007/01/11 06:15:27 UTC
[jira] Updated: (OFBIZ-118) Roles and Security for Display of data.
[ https://issues.apache.org/jira/browse/OFBIZ-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Howe updated OFBIZ-118:
-----------------------------
Description:
There is a need to be able to block viewing info except that info that may pertain to that login (partyID)
The is not taking into consideration Admin or Managers levels.
for instance you have employees who should not be able to see each others profiles, payroll information, and/or time sheets, as a few examples.
another area, if an communication event is set to private, no one but the party ID associated with the email address should be able to see them.
So this is a discussion about how to best implement this.
was:
There is a need to be able to block viewing info except that info that may pertain to that login (partyID)
The is not taking into consideration Admin or Managers levels.
for instance you have employees who should not be able to see each others profiles, payroll information, and/or time sheets, as a few examples.
another area, if an communication event is set to private, no one but the party ID associated with the email address should be able to see them.
So this is a discussion about how to best implement this.
Are the concerns for this issue sufficiently addressed inside OFBIZ-609 and related?
> Roles and Security for Display of data.
> ---------------------------------------
>
> Key: OFBIZ-118
> URL: https://issues.apache.org/jira/browse/OFBIZ-118
> Project: Apache OFBiz (The Open for Business Project)
> Issue Type: Improvement
> Components: accounting, content, ecommerce, humanres, manufacturing, marketing, order, party, product, workeffort
> Affects Versions: SVN trunk
> Reporter: BJ Freeman
>
> There is a need to be able to block viewing info except that info that may pertain to that login (partyID)
> The is not taking into consideration Admin or Managers levels.
> for instance you have employees who should not be able to see each others profiles, payroll information, and/or time sheets, as a few examples.
> another area, if an communication event is set to private, no one but the party ID associated with the email address should be able to see them.
> So this is a discussion about how to best implement this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira