Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Restricting templatedata access for business users
System
Sorry if this is a dumb question...but I've searched the forums, read the manuals...and still can't find a good answer.
Does the average user need access to the entire /templatedata directory or just the /data directory? I'm asking because we have some "ambitious" business users who have been "hacking" our tpls and making unauthorized changes to our branding.
Unfortunately, TeamSite was implemented with the Professional UI in 2000 and we haven't been able to move to the Standard UI where the user wouldn't "see" the /templatedata directory and be tempted. We are very traditional in our use in that we have our authors go through the /htdocs directory to their generated file (all html) in order to edit their dcr...so they have to have access to the /data directory under /templatedata in order to save their data.
Directory structure in the workareas:
/htdocs
/templatedata
/data
/presentation
datacapture.cfg
Is there an easy way to restrict authors from accessing the /presentation directory and the datacapture.cfg in /templatedata so that they can't change the branding of the site without affecting their ability to save the dcr or generate the output file? I know we could go into each directory and set the Windows permissions...but is there a better way?
We are currently on TeamSite 6.5 (SP3) - but moving to TeamSite 6.7.2 in 2 months.
Thanks for any opinions or suggestions.
Melody
Find more posts tagged with
Comments
nipper
You have a problem.
I did a presentation at GearUp that covered this (among other things). 1st you cannot restrict read access. They must have it. You can change the permissions on the dcr and tpl to prevent users from changing the files.
However I tend to use a different approach, my dcr is basically an inline statement that builds up the dct on the fly and prints out the XML required. The tpl is basically the same thing, but uses an iw_include to include the *real* tpl.
This allows me to easily share DCTs and TPLs across many branches. Since the files are located elsewhere, users cannot find and change them.
Wil should have posted the GearUp 2008 slides somewhere, you may want to look for it.
HTH
Andy
dsrow grid hierarchy.rptdesign
Migrateduser
Thanks for the response.
This answered my question and gave me next steps.