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

TeamSite UI | Customizing view for users

rohitspathak123

Hi,

We are doing a CMS enhancement project (introducing couple of new DCTs). This implementation will be used by only small set of people (say 4). So we want to create a customized TeamSite view for this group of users.
Requirement
- Goal is that the specific set of people should just see only those content or DCTs on which they will work.
- They donot want to see any other DCTs or assets (which is already present in TeamSite)

Our Approach
- Create a new workarea (WEP_WORKAREA)
- Bring in only required assets and DCT from the existing workarea (ALL) to WEP_WORKAREA

Problem
- Since we are not using Cross Branch Browser in our DCTs, so the WEP_WORKAREA has to be updated by Content Author for any asset change that was made in "ALL" workarea
- Sometimes the Content Author might miss to do 'Get Latest' in WEP_WORKAREA

Questions
- Is there any better appraoch?
- Can we live with just one workarea (rather than creating a separate workarea) ?
- Is there any permission settings that we can do on OS level so that the WEP group user will see only content which are related to them ?

Find more posts tagged with

Comments

Faizi

Hi,

We are doing a CMS enhancement project (introducing couple of new DCTs). This implementation will be used by only small set of people (say 4). So we want to create a customized TeamSite view for this group of users.
Requirement
- Goal is that the specific set of people should just see only those content or DCTs on which they will work.
- They donot want to see any other DCTs or assets (which is already present in TeamSite)

Our Approach
- Create a new workarea (WEP_WORKAREA)
- Bring in only required assets and DCT from the existing workarea (ALL) to WEP_WORKAREA

Problem
- Since we are not using Cross Branch Browser in our DCTs, so the WEP_WORKAREA has to be updated by Content Author for any asset change that was made in "ALL" workarea
- Sometimes the Content Author might miss to do 'Get Latest' in WEP_WORKAREA

Questions
- Is there any better appraoch?
- Can we live with just one workarea (rather than creating a separate workarea) ?
- Is there any permission settings that we can do on OS level so that the WEP group user will see only content which are related to them ?

As per my understanding, if the two workareas have dependency on each other then it would be better to be one.
If not then there should be sync both the workareas on certain duration of time by "Get Latest" or using workflow or CLT iwupdate.
Problem with above you have already mentioned (Sometimes the Content Author might miss to do 'Get Latest').
Your requirements can be achieve with single workarea, as per as access of DCTs, you can restrict user on group/role basis with in templating.cfg file. You can also manipulate the privileges of user/group through Administrator tab.

Adam Stoller

...
Our Approach
- Create a new workarea (WEP_WORKAREA)
- Bring in only required assets and DCT from the existing workarea (ALL) to WEP_WORKAREA

This is generally a BAD idea. It goes against the way that TS was designed to work and thus tends to cause lots of problems down the road.

Instead - I suggest you use folder permissions and user-training. Just because the users "don't want to see" something doesn't mean that they are entitled to get their way - sometimes you have to be able to say "no".