Reports: Permissions
(Network Edition only)
This article applies only to Bundle-Track versions 3.6 and later.
In Network Edition, user access
to individual reports is controlled by User
Roles. Access to the report tree requires the REPORTING role.
Access to specific reports may require other roles as well. Users
attempting to access a report for which they do not have permissions
will encounter Error 534.
Below are some SQL statements that you can run
in ISQL to review the reporting permissions in your enterprise.
Reports by User
select U.LMXUSRLAB, RS.RPTSETDES,
R.RPTNAME, L.LMXROLLAB from LMXUSR U, LMXUSRROL UL, LMXROL L,
RPTSETNOD RN, RPTSET RS, RPTMAS R where U.LMXUSRKEY = UL.LMXUSRKEY
and UL.LMXROLKEY=L.LMXROLKEY and L.LMXROLKEY = RN.LMXROLKEY and
RN.RPTMASKEY = R.RPTMASKEY and RN.RPTSETKEY = RS.RPTSETKEY
and U.LMXUSRLAB='<USERNAME>'
order by U.LMXUSRLAB, RS.RPTSETDES, R.RPTNAME
For all Users, delete the clause in bold.
For just one User, replace <USERNAME> with a valid
User Name.
Reports by Role
select L.LMXROLLAB, RS.RPTSETDES,
R.RPTNAME from LMXROL L, RPTSETNOD RN, RPTSET RS, RPTMAS R where
L.LMXROLKEY = RN.LMXROLKEY and RN.RPTMASKEY = R.RPTMASKEY and
RN.RPTSETKEY = RS.RPTSETKEY
and L.LMXROLLAB='<ROLENAME>'
order by L.LMXROLKEY, RS.RPTSETDES, R.RPTNAME
For all Roles, delete the clause in bold.
For just one Role, replace <ROLENAME> with a valid
Role name.
Roles by User
select U.LMXUSRLAB, R.LMXROLLAB from LMXUSR U, LMXUSRROL UR,
LMXROL R where U.LMXUSRKEY = UR.LMXUSRKEY and UR.LMXROLKEY=R.LMXROLKEY
and U.LMXUSRLAB='<USERNAME>'
order by U.LMXUSRLAB
For all Users, delete the clause in bold.
For just one User, replace <USERNAME> with a valid
User Name.
We welcome your comments at support@bundle-track.com.
If you would like our live assistance, you may hire us at our professional
services rate.
