We just rolled out SP2013 and our communications staff is interested in giving our CEO a voice through the social features. But he’s a busy guy and we don’t want to bother him with the need to post content himself (unless he wants to; I’m talking more of the planned communications and whatnot).
Is there a way to give another user limited access or the ability to “speak” as another user in SharePoint for this type of situation? We just don’t want to put C-level folks through the pain-in-the-butt steps of having to actually do the posting.
Or are we just better off having our communications folks being the accounts that everyone follows instead of the CEO?
That would require impersonation, which means the CEO’s credentials would need to be given out or stored somewhere for use. A safer and more practical approach might be to allow other users to create content that the CEO then publishes. Perhaps something like this:
- List with columns that correspond to the input required to make a social post.
- List workflow (2013) that starts manually and makes a social post via REST.
The other users will create the content on that list. The CEO will need to periodically check that list for items requiring publish. When the workflow is added to the list, it will add a column with the workflow’s status to the default view. Just make a separate view for the CEO that filters out completed workflows. Since the workflow will run as the CEO, the social post will be made as the CEO.Â