WC Site Administrator Permissions

[TomU]

Is there any compelling reason that the Site Administrator should not be added to the list of Organization Administrators in Windchill? Currently ours is not. The Site Admin can still get to everything, by searching, but can't "see" anything by browsing. That account is "not a member of any product" (or libraries).

Tom Uminn
Engineering Systems Analyst
trans-matic Mfg.
616-820-2499
-<">mailto:->

[ZacharyAlexande]

Hi Tom,

As you stated, the one of the main reasons not to add Site Admins to the
Org Admins is to prevent them from browsing. Although Site Admins can find
things by searching, it hides things from them that they do not know they
are looking for. This can be advantageous if you have a third-party doing
Site Administration or have other restrictions on data access.

Thanks,
Zack


Zachary D. Alexander
Operations Manager - RAPiDS
ProductSpace Solutions Inc.
Phone: 630-495-2999 Ex. 8104
Cell: 630-460-4905

[BenLoosli]

However, if you are like most smaller installations, one head has many hats and it does help to have the site administrator account also a member of the organization administrator group.

Thank you,

Ben H. Loosli
USEC, INC.

[RussPratt]

In a small system, it can make sense to have site admins be members of org admin group. However, I want to caution you that this can create significant problems if that user is not VERY CAREFULL when performing administrative actions. An Org Admin, who is not a Site Admin, can never "damage" the site level settings if he makes a mistake in understanding which context he is working in. However, a Site Admin, who is working as an Org Admin, does not have that protection. I have seen many cases where site level settings and configurations have been inadvertently overwritten by a user who is both SIte and Org Admin. I strongly recommend against this, unless you are willing to be very, very careful and also willing to tackle the difficult recovery issues when Mr. Murphy strikes.

Russ

[MikeFoster]

Hi Tom,

I've forgotten the details so maybe someone can remind me but if the site admin is also a member of an organization they then lose some crucial permissions related to ProjectLink (and maybe MPMLink).

Mike Foster
ATK

[clawrenz-2]

On this Topic,

While reading the Windchill Dataloading Guide I noticed this paragraph.

When creating product, project, library, or program containers, use an account that has creator permission for that container, but do not use the default administrator account (for example, wcadmin). This guideline applies to the account you use to perform the operation and any XML elements that associate an account with the container, such as <csvcreator> or <csvuser>. Because the default administrator account is a member of so many container teams, the membership lookup for that account takes too long and causes the method server to start very slowly or time out. For the same reason, do not add the default administrator account as a team member of the container.


Best Regards,
Carsten Lawrenz
Kalypso
Delivering on the Promise of Innovation
m. 415.378.6374
[cid:image001.png@01CDCBDB.3A8C1DF0][cid:image003.png@01CDCBDB.3A8C1DF0]<[cid:image007.png@01CDCBDB.3A8C1DF0]<http: www.facebook.com=" kalypsolp=">[cid:image009.png@01CDCBDB.3A8C1DF0]<http: twitter.com=" kalypsolp=">[cid:image011.png@01CDCBDB.3A8C1DF0]<http: www.linkedin.com=" company=" kalypso=">[cid:image013.png@01CDCBDB.3A8C1DF0]<http: www.youtube.com=" user=" kalypso...