Organizations and Users
Jan 27, 2012
06:08 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Jan 27, 2012
06:08 PM
Organizations and Users
Can a user be associated to more than one Organization in PDMLink?
In reading up on setting up Windchill and thinking about how to
structure our data, I was thinking that I'd use 'organizations' to
represent our clients and 'products' within those organizations to
represent each project. However, I can't tell if I can assign a user to
more than one organization. It looks like no, but I'm not sure.
Alternatively, could users be assigned to site context and then assigned
directly to 'products' within 'organizations'?
As you can imagine, each user may work on any project for any client, so
I need the freedom to assign them to anything.
Doug Schaefer
In reading up on setting up Windchill and thinking about how to
structure our data, I was thinking that I'd use 'organizations' to
represent our clients and 'products' within those organizations to
represent each project. However, I can't tell if I can assign a user to
more than one organization. It looks like no, but I'm not sure.
Alternatively, could users be assigned to site context and then assigned
directly to 'products' within 'organizations'?
As you can imagine, each user may work on any project for any client, so
I need the freedom to assign them to anything.
Doug Schaefer
Labels:
- Labels:
-
Other
2 REPLIES 2
Jan 28, 2012
09:40 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Jan 28, 2012
09:40 AM
The organization can represent the customer and it can represent who the
employee or contractor works for. Provided these users are not creating the
projects, products, or libraries themselves, yes you should be able to use
them provided that you make sure the property to expose users of that
organization (checkbox on UI when creating an organization) is checked. If
these users do need to create projects, products, or libraries in other
organizations, then that is an access control rule. Typically this also
mean you set their domain of user to site/unaffiliated which happens by
default when you leave that field blank on a new user screen.
I use multi organization in my setup. It offers a lot of flexibility.
employee or contractor works for. Provided these users are not creating the
projects, products, or libraries themselves, yes you should be able to use
them provided that you make sure the property to expose users of that
organization (checkbox on UI when creating an organization) is checked. If
these users do need to create projects, products, or libraries in other
organizations, then that is an access control rule. Typically this also
mean you set their domain of user to site/unaffiliated which happens by
default when you leave that field blank on a new user screen.
I use multi organization in my setup. It offers a lot of flexibility.
Jan 30, 2012
12:32 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Jan 30, 2012
12:32 PM
One caution about multiple organizations.
If you expect to be able to move a file from one org to another, you will have to define your lifecycles at the site level not the org level. If they are defined at the org level you will not be able to move files across the org boundary.
David Haigh
If you expect to be able to move a file from one org to another, you will have to define your lifecycles at the site level not the org level. If they are defined at the org level you will not be able to move files across the org boundary.
David Haigh
