Skip to main content
3-Newcomer
Nov 17, 2026 5:20 AM UTC
Question

Org level Access - Complete Type and Attributes Rights

Hi Everyone,

I have created a user at the Organization level in Windchill. I would like to assign this user complete access to Organization-level types and attributes.

My requirement is that whenever this user creates any object, the object and its associated information should be stored and maintained only at the Organization level, rather than under a Product or Library context.

I am looking for a suitable approach to achieve this requirement in both Windchill 11 and Windchill 12.

Could anyone please suggest the recommended configuration or implementation method?

Regards,
Aj

    1 reply

    joe_morton
    19-Tanzanite
    Nov 17, 2026 4:37 PM UTC

    I’ve never tried that, but here are some thoughts:

    • Typically, Windchill’s permissions flow down. So if you grant access at the Org level, they get that access at the lower levels by default.
    • The most immediate way that comes to mind around that is to add Deny ACLs at the lower levels
    • So you could make a new Group for this specific access, add that user to the group, grant the required access at the Org level, then add Deny ACLs for every Product and Library to prevent the Org access from flowing down. 
    • There’s some immediate challenges with that: you’d want to update your product/library templates to ensure that every new product/library that gets created includes the Deny ACLs. If those get missed, that user will have permissions in that product/library

    Another approach would be to carefully consider what the user needs to create at the Org level. If instead you can manage those objects (for example, a specific document subtype) so they can only be created at the Org level, that would be another way to effectively block the user from creating those in the products/libraries. The same thing applies though, creation rules flow down, so you’d need to block those subtypes in every new product/library.

    For best practice, could this user instead work in a dedicated Library? Why do they need to work at the Org level?

    Translate