cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - You can subscribe to a forum, label or individual post and receive email notifications when someone posts a new topic or reply. Learn more! X

Users & Organizations

dgschaefer
21-Topaz II

Users & Organizations

Well, we got WC10 installed with not a small amount of hand holding from
our TriStar rep. Now I need to set up my users and projects and I have
a question on how to proceed.



In my mind, the configuration that will be best for our company will be
to have each of our clients set up as an org in WC and each client
project set up as a product within that org. This will allow us to
manage client specific libraries, which is important to providing
clients with data that appears as though it was generated in house. We
manage that now with server folders.



So we'd have something like this in WC:



Site

Design Central (default org)

Internal library

Client 1

Client 1 library

Client 1, Project 1

Client 1, Project 2

Client 2

Client 2 library

Client 2, Project 1

Client 2, Project 2



What I don't know about is users. I want my users to have the same
access level across all clients (orgs), so my thought was making them
unaffiliated at the site level rather than tied to an org. Can I then
give them access to multiple orgs (clients)? I created a site level
use, but it seemed as though I was unable to 'see' them in the default
org, but it is very likely that I was missing something.



The TriStar rep suggested for our trial simply leaving everything within
the default org (Design Central) since we are only going to run a single
project. I'm open to that if creating orgs is going to get us bogged
down; however I'd like to have as close to an accurate simulation of our
eventual configuration as possible.



Thoughts? Alternatives?


Thanks,



Doug Schaefer
--
Doug Schaefer | Experienced Mechanical Design Engineer
LinkedIn
1 REPLY 1

There should be a checkbox when you create or edit the the organization to share users and also allow it to be a subscriber or to container products,libraries,or projects.

You can set the organization to whichever they are principally associated while creating user, but define them at site and do not select domains. This should take care of things. To give everyone at least view/read access, add the organization to the guest role on a team. I do not like the guest or members roles, so I define my own to retain full control of system, but that may be too advanced for your requirements.


Sent from my Verizon Wireless BlackBerry
Top Tags