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; } } }

Restrict access to a directory?

System

Hi Devnetters -
Seems like a question that would've been asked before, but initial searches haven't found anything:

Having jumped from TeamSite 6.1 to 6.7.1 (both on Solaris), we've got a lot of catching up to do on roles / group administration. Here's the question:

If I set up a workarea and give access to a group to that workarea, can I further restrict access to a directory within the workarea to a subset / subgroup of the group sharing the workarea?

I'd rather do this using just the TS Admin functions.

Wally Box
Nike, Inc.

Find more posts tagged with

Comments

Adam Stoller

Hi Devnetters -
Seems like a question that would've been asked before, but initial searches haven't found anything:

Having jumped from TeamSite 6.1 to 6.7.1 (both on Solaris), we've got a lot of catching up to do on roles / group administration. Here's the question:

If I set up a workarea and give access to a group to that workarea, can I further restrict access to a directory within the workarea to a subset / subgroup of the group sharing the workarea?

I'd rather do this using just the TS Admin functions.

Wally Box
Nike, Inc.

Once you're within the workarea - OS level functions for permission setting take place - except possibly when dealing with TS groups though I don't see any mention of utilities for such in the CLT manual.

You might be able to set owner and/or group on files and/or directories via the Properties view within the TS GUI - though you'd probably have to be logged in with either a power-user or a Master user account... haven't tried.

I usually just go to the file system view and use chown / chgrp

Migrateduser

Thanks Fish -

I haven't trusted the command line view into the repository for a good while. It used to be (on 6.1 or 5.5) that I could repeatedly execute an ls -la command and get different results from one time to the next.

Now, we're on 6.7.1 on Solaris and everyone belongs to one OS level group (called iwglobal) and then we use TeamSite groups via the gui Admin to set up additional access / restriction.

So now, if we go into the command line, everything belongs to the iwglobal group. This actually has made user / group admin a lot easier, but any chown-ing is pretty much useless.

That's why I qualified my question to ask if this could be done via the Admin with roles, etc. I'm sure we could restrict access programatically via workflow or with a second branch, but I'd rather push that restriction back up to the directory level if possible.

Cheers,
Wally Box
Nike, Inc.