nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Content Ownership

GodBlessMe

Can a Master or an Administrator change the content ownership for an html page in a workarea?
Thanks.

Find more posts tagged with

Comments

Adam Stoller

If by content ownership you mean file ownership - then this is not a TeamSite role-related function - this is a fileystem access issue.

A system administrator (root, Administrator, and/or similar) could go to the file in question and do a chown / cacls on the file in question. Alternatively, the submit.cfg file could be setup so that when the file is submitted it receives the appropriate ACLs as configured.

There is no provision for doing this within the GUI, though you could create custom menu items that run CGI scripts that could do this, but that might entail some unsavory / unsecure processes.

--fish
(Interwoven Senior Technical Consultant)

GodBlessMe

By Content Ownership what I meant was like the ownership we have for workareas, can we have different users own different files within a workarea? If we can have , is it possible to change with the Teamsite GUI?
Thanks.

Adam Stoller

File ownership is handled at the OS-level.

You can have different files and directories owned by different people within a workarea, but that ownership, once submitted, will be consistant across all workareas for that branch.

The TeamSite GUI does not provide any OOTB interface for doing this - but the TeamSite administrative configuration file, submit.cfg, allows this to be controlled at submit-time (read the appropriate section in the TeamSite Administrator's Guide for more details)

If you have a setup like this:

/default/main/branch1/WORKAREA/wa1/
- file1
- file2
- subdir
  - file3
/default/main/branch1/WORKAREA/wa2/
- file1
- file2
- subdir
  - file3
/default/main/branch2/WORKAREA/wa1/
- file1
- file2
- subdir
  - file3

There are 4 items within branch1 that can have distinct ACLs associated with them.
There are 4 items within branch2 that can have distinct ACLs associated with them.

The same item within two different workareas on branch1 must have the same ACLs. You cannot [preserve over time] /default/main/branch1/WORKAREA/wa1/file1 with an owner of "me" and /default/main/branch1/WORKAREA/wa2/file1 with an owner of "you" - just won't work. Once the file is submitted to STAGING, and the workareas are synced up with Get Latest, you are dealing with a single file that is virtually existing in two workareas - but there is only one file and it only has one owner.

Does that help?

--fish
(Interwoven Senior Technical Consultant)

GodBlessMe

Its clear now fish....
Thanks