Social media governance: account ownership, archiving, and handoff

Reference article · 5 min read

Agency social media accounts tend to start informally: one opened for an event, another for emergency notices, a third when a platform changes its features. Within a few years an agency holds accounts that no one can fully list, including at least one that a single employee can log into. The obligations attached to them match those for email and any other agency record.

Governance here is records and asset management applied to channels a third party operates. Three questions carry most of the weight: who may open an account, how content is preserved, and what happens when the person running it leaves.

Ownership, inventory, and credentials

An account created to conduct public business belongs to the agency, not to the staffer who set it up. Put that in policy, have employees acknowledge it when granted posting access, and back it with controls.

• Register accounts to agency identities. Use a role-based mailbox or distribution list as the email of record, never a personal or individual work address.
• Avoid personal recovery paths. Recovery numbers and multifactor codes tied to an employee's phone make the agency dependent on that employee.
• Use platform business tooling where it exists. Where the page is separate from the personal logins that administer it, removing a departing administrator becomes routine.
• Keep one register. Record platform, handle, public purpose, owning division, primary and backup administrators, email of record, and archiving status. Every account needs a backup administrator.
• Hold credentials centrally. Keep them in the agency password manager with access by role, and treat sharing a password outside it as a policy violation.

Review the register annually at minimum, confirming that each administrator still works for the agency and that archiving covers every channel. A platform search on the agency's own name usually turns up an account nobody knew about.

Approving a new channel

Treat a new account as a service request. A short intake form is enough: purpose, audience, owning division, primary and backup posters, how comments will be monitored and how quickly, how content will be archived, and what would retire the account. Approval should involve communications, records, and IT security.

Fair reasons to decline include no staffing to monitor comments when the public expects an answer, duplication of an existing channel, and an inability to archive the platform. Accessibility belongs in intake as well: federal rulemaking has tied state and local government web content to a recognized accessibility standard on timelines that vary by entity, so confirm current requirements with counsel.

Archiving posts, comments, and messages

Most states treat content created or received in the conduct of public business as a record regardless of medium. Retention comes from schedules issued by the state archives or records authority; social media may fall under a general schedule or under the schedule for the program it supports.

• Capture more than your own posts. Public comments, replies, direct messages, and the account's edits and deletions form part of the record.
• Record moderation actions. Log hidden and deleted comments and blocked users with timestamp and reason, because those decisions can be challenged later.
• Do not rely on screenshots. Manual capture misses threads and metadata, and fails during high-volume events.
• Plan for disposition. Deleting a post on the platform does not dispose of the record. Destruction happens on schedule, with documentation.
• Test production, not just capture. Run a realistic records request through the archive: keyword and date search, redaction, and export.

Departures, handoff, and dormant accounts

Add social media to the offboarding checklist next to the badge and the laptop. On a departure, rotate credentials, remove the person from every administrator role, and verify that the email of record and recovery contacts point at agency identities. The incoming staffer also needs the content calendar, scheduled posts, and open constituent questions.

Dormant accounts deserve a decision rather than drift. If a channel is no longer staffed, preserve the archive, post a notice directing followers to the channel that remains, then either retire the account or keep the handle claimed and locked against impersonation. Deleting an account outright can destroy records still inside their retention period.

Accounts run by elected officials

Elected officials often run accounts that mix campaign material, personal commentary, and official business. Courts have examined when such activity amounts to government action, asking whether the official had authority to speak for the government and appeared to be exercising it. When an account functions as an official channel, blocking constituents or deleting their comments can raise First Amendment questions, and this area continues to develop. Have counsel advise on specific accounts, offer officials an agency-administered account with clear labeling, and settle what happens to it at the end of a term.

What to ask vendors and require in the contract

• Which content types are captured natively, including comments, direct messages, edits, and deletions, and what happens when a platform changes its data access.
• How capture gaps are detected and reported to the agency.
• Whether the agency can export the complete archive in an open format at any time, including at contract end, without an added fee.
• Whether search, legal hold, redaction, and export are available to staff directly rather than through a support ticket.
• How pricing scales as accounts and volume grow.

In the contract, state that the agency owns the archived data, require export on termination and deletion of vendor-held copies afterward, and require notice of material changes in platform coverage. A workable starting order is inventory, then policy and intake, then archiving, then offboarding. HQT's work in this area covers records and archiving integrations, systems engineering, and technology advisory support for state and local government.

Frequently asked questions