cpanel awstats and mail access

[7thDsites]

Hi All,

My question is:

we're the "ghost host" for a client that's reselling the hosting without reseller privledges and one of the people that he's providing the hosting to wants/needs access to the mail functions and awstats in the cpanel - the problem is that we do not want the end user to have overall cpanel access - only access to the mail icon and the stats. The end user knows nothing about hosting which is partly why we don't want them messing around in the cpanel area.

what i was thinking is that perhaps we could simply give the end user deep links into the stats and the mail which of course he would be prompted for the username and pass, which would be that of the cpanel, but likely if we gave them deep links they wouldn't be able to figure out how to access the regular path of /cpanel. hope that makes sense.

Does the above sound feasible and or would there be another solution?

Thanks in advance for any assistance,

Best,
J

 

[cPanelDavidG]

Hi All,

My question is:

we're the "ghost host" for a client that's reselling the hosting without reseller privledges and one of the people that he's providing the hosting to wants/needs access to the mail functions and awstats in the cpanel - the problem is that we do not want the end user to have overall cpanel access - only access to the mail icon and the stats. The end user knows nothing about hosting which is partly why we don't want them messing around in the cpanel area.

what i was thinking is that perhaps we could simply give the end user deep links into the stats and the mail which of course he would be prompted for the username and pass, which would be that of the cpanel, but likely if we gave them deep links they wouldn't be able to figure out how to access the regular path of /cpanel. hope that makes sense.

Does the above sound feasible and or would there be another solution?

Thanks in advance for any assistance,

Best,
J

Why not create a feature list (WHM -> Packages -> Feature Manager) with only the functionality you desire them to have, assign that list to a package and then assign that package to this particular user?

This will give them access the features you want them to have but not the features you don't want them to have access to. Note, you may want to set up a stricter feature list for your other users in case they happen to stumble upon the cPanel interface one day.