Domains/Accounts/Users/Projects...

[Kirk Jantzer <ki...@gmail.com>]

Can someone break down the accounts and users section of CS for me? My
company will be using CS internally, on one windows domain. I have LDAP
enabled currently, and have created a domain in CS that has our network
domain. I have added accounts under that domain that match users on my
team. I notice that each account has a user that is associated with it of
the same name, but also has the ability to add users under that account. Is
this the right way to go, or should I be doing things differently? Also, in
regards to CS usage within our company - I would like to be able to give
logins to other teams - should that be done through accounts or projects
(this is mostly for limiting how many instances they can deploy).

Re: Domains/Accounts/Users/Projects...

[David Nalley <da...@gnsa.us>]

On Thu, Apr 25, 2013 at 1:10 PM, Kirk Jantzer <ki...@gmail.com> wrote:
> Can someone break down the accounts and users section of CS for me? My
> company will be using CS internally, on one windows domain. I have LDAP
> enabled currently, and have created a domain in CS that has our network
> domain. I have added accounts under that domain that match users on my
> team. I notice that each account has a user that is associated with it of
> the same name, but also has the ability to add users under that account. Is
> this the right way to go, or should I be doing things differently? Also, in
> regards to CS usage within our company - I would like to be able to give
> logins to other teams - should that be done through accounts or projects
> (this is mostly for limiting how many instances they can deploy).

So generally you want accounts at the lowest level at which you want
to track usage.
Projects are invaluable, and really how you should hand out access to
other groups. At present all accounts/users that are part of a project
need to be in the same domain - so keep that in mind from a
Domain/projects perspective.

--David