Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
File menu access
tmsy
TS 6.0 Win2K
In my Y: drive, I've set the file access permissions as follows:
1. De-selected checkbox for "Allow inheritable permissions from parent to propagate to this object"
2. Administrator has full control, user group has modify access
3. Enabled "Reset permissions on all child objects".
4. Turned off read-only bits on the site content
In my upload workarea, I have an htdocs folder containing my site content. In the htdocs folder, I can access all File menu options but if I navigate to any sub-folder, the only options available are "Versions" and "Properties". Everything else is greyed out. I'm not sure what is going on. Could it be some permissions propagating down somehow, from TeamSite level and/or OS level?
Also, does anyone have any references to file/folder access and permission documentation?
Thanks.
Find more posts tagged with
Comments
Migrateduser
How are you uploading these files? If it's a task of some sort, who owns the task? What does either the OS or TeamSite say about the ownership of those files? How are you logged in to TeamSite?
Dave
Current Environment(s):
(1) TS 6.5 on W2K3
(2) TS 6.1 SP1 on W2K3
By the way, I miss Unix terribly.
tmsy
I uploaded the files directly into the Y: drive.
It's not a task.
Ownership of the files is inherited from the parent directory's settings, which is basically full control for the administrator and access for a select group of users.
I'm logged in as the administrator in a master role.
Migrateduser
Very strange, I agree... when you click on PROPERTIES in TS on one of these files, what does it say about ownership and other settings? Similarly, when you right click and get PROPERTIES in Windows, what does it say?
Current Environment(s):
(1) TS 6.5 on W2K3
(2) TS 6.1 SP1 on W2K3
By the way, I miss Unix terribly.
tmsy
In TS:
- owner is Administrator
- group is none
- permissions: Administrators have full control, group A has change, group B has read
In OS:
- Administrators have full control
- group A has modify
- group B has read and execute
tmsy
Figured it out - the read-only bits on the sub-folders were not turned off (but they were turned off for all files).