If you whre the site webmaster

How much access should the site owner have.

[mack]

when you build sites for a client and use a web hosting company for domain names and hosting, do you allow your clients access to the hosting companys control pannel?

[Susanne]

This is a very good question Mack. I am involved in a sensitive situation where one of the employees of the client is "a little dodgy". Imagine the scenario if you are handling a fairly large site and you can't really keep track of every single page. The client and x number of employees have access to the server and can upload as they please even if they have been told not to touch anything.

There are situations where an employee or even a former emplyee might try to sabotage a site. I know it sounds crazy but I am right in the middle of such a potential scenario. In other cases it is simply a matter of ignorance on the employee's side when he or she has done something with good intentions that causes damage to the site.

Of course these examples are exceptions but I think it should be stated clearly in contracts who should have access to servers. Fewer people is better. There should also be a description of things that the client is NOT allowed to do. Let's say a client decides to start linking to other sites left, right and centre without even knowing the danger of doing that. Or the client starts changing page titles and alt tags without understanding the consequences.
Would be interesting to hear other webmasters' experiences regarding these things.

[jackofalltrades]

Im fairly new to the whole game, but Id say that it should be made clear to the client from the start that its a delicate process and really shouldnt be messed around with.

You could tell the client that all changes be made thru you (i offer to make small changes for free - eg, adding a new page or some links, etc - but major changes will incur a fee).

On the other hand, offer to train the client or his staff in the process of maintaining the site and updating it (including issues of security, etc). Obviously charge more this service.

Or leave them to it. You do the site and get paid for it. Its really out of your hands after that! :)

[Birdman]

I think they should have access, since they did pay for the site but they must be forewarned of the possible damage that could be done and the cost to fix it won't be cheap. After all, stats are often accessed through the cpanel and the client needs to see how thier site perfoms.

[chris_f]

Whenever I build sites I take control of the entire project. Only I will have access to the hosting control panel and I will know the FTP details. I do, however, build my client a content management system so that they can add pages, alter content and delete pages. Every change that make is recorded and a backup is stored. Therefore, if something is changed I can easily revert it back.

I give my clients a control panel by which they can contact me and issue any requests. I tell them that all minor works will be completed within 24 hours unless I give them prior notice (for when I go on holiday). They seem to be ok with that because I usually respond quickly. All this is provided free of charge. I haven't come across an unsatisfied client yet.

Chris

[Nick_W]

I outsource the hosting (like you all do I expect) but do not charge the client for it. The hosting company has a direct relationship with the client is is naturally responsible for all hosting needs.

This is because I'm a firm beleiver in the principle of 'horses for courses': I don't take responsibility for stuff I have no expert knowledge in.

But, I tell my clients that they should never need to contact the hosting company and that anything they need: Ask me first.

And that anything they decide to do with their hosting account is entirely at their own risk.

The Hosting company like it this way too. I'm the technical contact, so they deal with someone with at least a working knowledge of how a server works ;)

Nick

[mack]

In general all I would be doing was building the website and aranging the hosting and domain name for them. My main concern is that I belive the temptation to play around with the control pannel woudl be very high. Obviously i woudl inform the client that I use a webhosting company, but I am still not sure if allowing them to be able to access the pannel is a good idea. One wee alteration to dns for example could bring the entire site down.

[Nick_W]

Who cares?

If they mess it up, you get paid to fix it right ;) And they certainly won't mess with it agian....

Nick