Fair point. Thanks a lot for you input. Len
-----Original Message----- From: Kristoffer Sheather @ CloudCentral [mailto:[email protected]] Sent: 15 April 2013 11:22 To: [email protected] Subject: RE: Domain and Account organisation IMHO these are questions that only you are going to be able to answer. Firstly you need to decide how you want your business to operate, then to map that to the technical implementation, not the other way around. The answer is that you need to look at your business first, document the requirements, then implement and test the technical solution. There is no easy answer. Regards, Kristoffer Sheather Cloud Central Scale Your Data Center In The Cloud Phone: 1300 144 007 | Mobile: +61 414 573 130 | Email: [email protected] LinkedIn: | Skype: kristoffer.sheather | Twitter: http://twitter.com/kristofferjon ---------------------------------------- From: "Len Bellemore" <[email protected]> Sent: Monday, April 15, 2013 7:59 PM To: "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Subject: RE: Domain and Account organisation OK. I was also thinking about the Accounts structure under my domain. >From what I understand, I can have a normal "user" account and a >"Domain-Admin" account. Each account can of course have users under it. Should I be creating two accounts per customer? One with Users (including the customer users) and one with Domain-Admins (with my company's engineers and maybe the Admin from among the customer's userbase?) Cheers Len -----Original Message----- From: Kristoffer Sheather @ CloudCentral [mailto:[email protected]] Sent: 15 April 2013 10:21 To: [email protected] Subject: re: Domain and Account organisation Domains are simply a way to structure groups of accounts and other domains. How you map this to your business & customer requirements is completely up to you. For ultimate flexibility, I recommend creating a domain for each customer account, then create an account within that domain. That provides you the flexibility of being able to create a sub-domain under the domain if you ever need to. Regards, Kristoffer Sheather Cloud Central Scale Your Data Center In The Cloud Phone: 1300 144 007 | Mobile: +61 414 573 130 | Email: [email protected] LinkedIn: | Skype: kristoffer.sheather | Twitter: http://twitter.com/kristofferjon ---------------------------------------- From: "Len Bellemore" <[email protected]> Sent: Monday, April 15, 2013 7:18 PM To: "[email protected]" <[email protected]> Subject: Domain and Account organisation Hi Guys, I've got a question about how to organise my Domain and Accounts I've got two types of customers. Managed and Non-Managed. Managed customers pay for monitoring and proactive administration of vms. They also get us to create VMs for them from time to time. Non-Managed customers are completely self-service. I'm not sure if the managed / non-managed things is relevent in this case, but I thought I'd mention it anyway. My thinking thus far is to create a domain per customer, an account per customer (or more accounts if there are departments within that company) and then users under each account. It was also suggested to me to create a domain for Managed and one for Non-Managed and then start creating sub-domains under those. At the moment I can't really understand 100% what domains are used for - same goes for the domain-admin. Could anyone explain it in simple terms? Thanks Len
