<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Ethical Quandary: Assistant, Blogging, and Logins</title>
	<atom:link href="http://www.contentious.com/2008/07/07/ethical-quandary-assistant-blogging-and-logins/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.contentious.com/2008/07/07/ethical-quandary-assistant-blogging-and-logins/</link>
	<description>Amy Gahran's news and musings on how we communicate in the online age.</description>
	<lastBuildDate>Thu, 09 Feb 2012 16:36:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Amy Gahran</title>
		<link>http://www.contentious.com/2008/07/07/ethical-quandary-assistant-blogging-and-logins/comment-page-1/#comment-1222806</link>
		<dc:creator>Amy Gahran</dc:creator>
		<pubDate>Wed, 09 Jul 2008 16:09:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.contentious.com/2008/07/07/ethical-quandary-assistant-blogging-and-logins/#comment-1222806</guid>
		<description>Thanks for the advice all, especially Janet. I&#039;ll be talking to my client tomorrow, I&#039;ll mention it then. But this will definitely be a thing to keep in mind with future client contracts!

- Amy Gahran</description>
		<content:encoded><![CDATA[<p>Thanks for the advice all, especially Janet. I&#8217;ll be talking to my client tomorrow, I&#8217;ll mention it then. But this will definitely be a thing to keep in mind with future client contracts!</p>
<p>- Amy Gahran</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: doug</title>
		<link>http://www.contentious.com/2008/07/07/ethical-quandary-assistant-blogging-and-logins/comment-page-1/#comment-1222794</link>
		<dc:creator>doug</dc:creator>
		<pubDate>Tue, 08 Jul 2008 03:10:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.contentious.com/2008/07/07/ethical-quandary-assistant-blogging-and-logins/#comment-1222794</guid>
		<description>I would ditto what Janet suggests re: contracts and Amy&#039;s suggestions re: emailing to advise that someone will be helping.

Best of luck!</description>
		<content:encoded><![CDATA[<p>I would ditto what Janet suggests re: contracts and Amy&#8217;s suggestions re: emailing to advise that someone will be helping.</p>
<p>Best of luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janet Attard</title>
		<link>http://www.contentious.com/2008/07/07/ethical-quandary-assistant-blogging-and-logins/comment-page-1/#comment-1222793</link>
		<dc:creator>Janet Attard</dc:creator>
		<pubDate>Mon, 07 Jul 2008 22:30:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.contentious.com/2008/07/07/ethical-quandary-assistant-blogging-and-logins/#comment-1222793</guid>
		<description>All you really need to do is to specify in client contracts that you and your staff will have access to and work on their accounts. 
If the client can easily set up a second login for your company, it would be useful to have a separate login for the assistant - that way you could see who did what, when, if necessary.  But if your assistant is someone you know does a good job and you aren&#039;t a micromanager, there would probably never be a need to see who was the last one to &quot;touch&quot; a page. 

Just be sure that YOU have access to all passwords for assistants, so you could change them if you ever had to let an assistant go.</description>
		<content:encoded><![CDATA[<p>All you really need to do is to specify in client contracts that you and your staff will have access to and work on their accounts.<br />
If the client can easily set up a second login for your company, it would be useful to have a separate login for the assistant &#8211; that way you could see who did what, when, if necessary.  But if your assistant is someone you know does a good job and you aren&#8217;t a micromanager, there would probably never be a need to see who was the last one to &#8220;touch&#8221; a page. </p>
<p>Just be sure that YOU have access to all passwords for assistants, so you could change them if you ever had to let an assistant go.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lara, The Data Digger</title>
		<link>http://www.contentious.com/2008/07/07/ethical-quandary-assistant-blogging-and-logins/comment-page-1/#comment-1222792</link>
		<dc:creator>Lara, The Data Digger</dc:creator>
		<pubDate>Mon, 07 Jul 2008 21:45:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.contentious.com/2008/07/07/ethical-quandary-assistant-blogging-and-logins/#comment-1222792</guid>
		<description>I would like to contribute to your conversation by sharing my thoughts about your concerns.
 * Should I get the client’s permission beforehand before giving my assistant access to the blog back-end? 
Yes.  In my experience when people work on a team for a client, the client is told who is on the team, how to contact them and any other pertinent information.  Full disclosure is in line with &quot;it is better to be safe than sorry.&quot;

 * Should I ask the client to set up a separate login for my assistant, or just give my assistant access to my login for the blog? 
This depends on your comfort level.  After you obtain your client&#039;s permission to have your assistant help with this project,  inquire as to their preference for logging in.

* What questions or concerns are the blog owners likely to have about this, and how might I address them constructively? 
Blog owners want to know their blog will remain consistent, updated according to their expectations and the process will remain seamless and in the background for them.
Assure them you will be thorough in your search for an assistant. Assure them you will be responsible for managing an assistant.  In other words, you are your clients point of contact.  You will disseminate information, assignments and establish deadlines for your assistant. Your client will remain your priority.  

Assistants are team members who contribute positively to the project.</description>
		<content:encoded><![CDATA[<p>I would like to contribute to your conversation by sharing my thoughts about your concerns.<br />
 * Should I get the client’s permission beforehand before giving my assistant access to the blog back-end?<br />
Yes.  In my experience when people work on a team for a client, the client is told who is on the team, how to contact them and any other pertinent information.  Full disclosure is in line with &#8220;it is better to be safe than sorry.&#8221;</p>
<p> * Should I ask the client to set up a separate login for my assistant, or just give my assistant access to my login for the blog?<br />
This depends on your comfort level.  After you obtain your client&#8217;s permission to have your assistant help with this project,  inquire as to their preference for logging in.</p>
<p>* What questions or concerns are the blog owners likely to have about this, and how might I address them constructively?<br />
Blog owners want to know their blog will remain consistent, updated according to their expectations and the process will remain seamless and in the background for them.<br />
Assure them you will be thorough in your search for an assistant. Assure them you will be responsible for managing an assistant.  In other words, you are your clients point of contact.  You will disseminate information, assignments and establish deadlines for your assistant. Your client will remain your priority.  </p>
<p>Assistants are team members who contribute positively to the project.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amy Sample Ward</title>
		<link>http://www.contentious.com/2008/07/07/ethical-quandary-assistant-blogging-and-logins/comment-page-1/#comment-1222791</link>
		<dc:creator>Amy Sample Ward</dc:creator>
		<pubDate>Mon, 07 Jul 2008 21:27:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.contentious.com/2008/07/07/ethical-quandary-assistant-blogging-and-logins/#comment-1222791</guid>
		<description>In a previous job situation, I was kind of what you are describing as an assistant.  Instead of blogs, it was the sending out or management of email campaigns for clients.  The way we handled it was that we sent an email to the client (to the person we normally communicated with, not the ceo or admin or whomever) and said, &quot;here is amy, who is helping me with a lot of the work we do here, including some of the work on your projects. she will be managing some of the email campaign work as well. so, she will have access to *insert platform or tool* and will also serve as another contact if you have questions or need help.&quot; so it was presented as a win win, i have access but am helping them and they now have two people to contact when they need something.

Good luck!</description>
		<content:encoded><![CDATA[<p>In a previous job situation, I was kind of what you are describing as an assistant.  Instead of blogs, it was the sending out or management of email campaigns for clients.  The way we handled it was that we sent an email to the client (to the person we normally communicated with, not the ceo or admin or whomever) and said, &#8220;here is amy, who is helping me with a lot of the work we do here, including some of the work on your projects. she will be managing some of the email campaign work as well. so, she will have access to *insert platform or tool* and will also serve as another contact if you have questions or need help.&#8221; so it was presented as a win win, i have access but am helping them and they now have two people to contact when they need something.</p>
<p>Good luck!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

