adminpack.pub About

Workflow · A working process

Publishing team operations

Own your accounts, pick a platform for your format, write down handoffs, and onboard and offboard cleanly. For news, newsletters and presses.

Jump to a section

Overview

Outcome
Every account the publisher depends on is owned by the organization, has a named owner and a backup, and can be handed over in an afternoon; new people get what they need on day one and departing people lose access the day they leave.
Who it is for
For small teams publishing news sites, newsletters, magazines or books. Steps marked news-specific apply to newsrooms; the account, access and onboarding steps apply to every format. Discount programs mentioned have their own eligibility rules.
Before you start
  • An organization-owned email domain, so accounts are not tied to personal addresses.
  • A list of the tools you pay for or depend on, even if it starts as a spreadsheet.
  • A decision about who administers accounts (usually the operations lead) and who is their backup.

Skip to the workflow steps

Start with ownership, not tools

The most expensive operations failure for a small publisher is losing control of an account: a domain registered to a founder’s personal email, a newsletter list only one freelancer can log into, social accounts recovered to a phone number that left with someone. Fixing ownership costs a few hours. Recovering an account you no longer control can take weeks.

The access register is the backbone. It doubles as your onboarding and offboarding checklist and as your renewal calendar.

The order to secure things

Work from what takes the publication offline to what is merely inconvenient:

  1. Domain registrar and DNS.
  2. Hosting and the publishing platform.
  3. Email and the document suite.
  4. Payment and newsletter platforms, since they hold readers’ data and money.
  5. Social accounts, chat, design and scheduling tools.

For each, confirm an organization login, two admins and two-factor authentication.

Small habits that pay off

  • Organize shared drives by function, not by person, so files survive departures.
  • Move decisions out of chat and into documents.
  • Keep the publishing workflow to one page, so anyone can see where a piece is stuck and who to ask.
  • When someone leaves, rotate any shared passwords they could see, the same day.
  • Nonprofit programs for workspace, chat, design and social tools each have their own eligibility rules. Slack’s, for example, excludes some organization types. Check before you plan around one.

Only the platform choice splits by format; the Variations section covers news sites, newsletters and presses. Everything else applies to all three.

The workflow

  1. Inventory every account

    Responsible: Operations lead

    List every service the team uses: domain registrar, hosting, publishing platform, email, chat, file storage, social accounts, payment and newsletter tools. For each, record the admin, the backup admin, the billing owner, the login email and the renewal date.

    Inputs
    Card and bank statements; Staff knowledge
    Outputs
    Access register
  2. Move ownership to the organization

    Responsible: Operations lead

    Change any account registered to a personal email to an organization address or shared admin mailbox, and add a second admin. Domain, hosting and the publishing platform come first, since losing them takes the site down.

    Inputs
    Access register
    Outputs
    Organization-owned accounts with two admins each
  3. Store credentials in a team password manager

    Responsible: Operations lead

    Use an organization password manager account, with shared vaults by function and recovery held by two people. Turn on two-factor authentication everywhere it is offered and store recovery codes in the manager.

    Inputs
    Access register
    Outputs
    Shared vaults; Two-factor enabled; Recovery procedure
    Resources
    1Password for Journalists
  4. Choose the publishing platform by format

    Responsible: Publisher or editor

    Choose the platform that matches what you publish. A news site with sections, bylines, memberships and ad placements has different needs from a newsletter or a press catalog. News-specific: a newsroom may consider Newspack, which is built for news organizations.

    Inputs
    Format; Revenue model; Budget
    Outputs
    Platform decision with owner and exit notes
    Resources
    Newspack
  5. Set up email, files and chat

    Responsible: Operations lead

    Run email, calendars and documents in one suite, such as Google Workspace or the suite you already have. Use team chat, such as Slack, for daily coordination, with channels for the editorial calendar, production and operations.

    Inputs
    Staff list
    Outputs
    Workspace accounts; Shared drives by function; Chat channels
    Resources
    Google Workspace for Nonprofits, Slack, Slack for Nonprofits
  6. Define the publishing handoffs

    Responsible: Editor

    Write down who moves a piece from draft to edit to publish to distribution, where each handoff happens, and what is checked at each stage. Keep it to one page.

    Inputs
    Current workflow
    Outputs
    One-page publishing workflow
  7. Add design and social scheduling if neededOptional

    Responsible: Audience or design lead

    Optional. Add a design tool such as Canva for templates and a scheduler such as Buffer for social posts, with the organization as account owner.

    Inputs
    Brand assets
    Outputs
    Shared templates; Scheduled social queue
    Resources
    Canva for Nonprofits, Buffer for Nonprofits
  8. Run onboarding and offboarding from the register

    Responsible: Operations lead

    Use the access register as the checklist: grant only the accounts a role needs on arrival, and remove every one on departure, transferring ownership of files, posts and scheduled items first.

    Inputs
    Access register; Role description
    Outputs
    Completed onboarding or offboarding checklist

Variations

News site (news-specific)

When: You publish news on a site with sections, bylines, memberships or donations, and advertising.

Newspack is open-source WordPress software built for news organizations, including reader-revenue and newsletter features. The software is free to run on your own hosting if someone can maintain WordPress; Newspack also sells a managed service if you would rather pay for hosting and support.

See: Newspack

Newsletter-first publisher

When: Your main product is an email newsletter, with a light website.

Choose a newsletter platform that handles subscriptions, payments and an archive site together. The news-specific content management system (CMS) steps do not apply. Keep the subscriber list exportable, and record who owns the payment connection.

Independent press or magazine

When: You publish books or issues and sell through a store or distributors.

A catalog site with a store matters more than a news CMS. The news-specific steps do not apply; the access, password manager, workspace and onboarding steps do. Track distributor and printer portals in the access register like any other account.

Password manager for individuals

When: You are a freelance or independent journalist rather than an organization.

1Password for Journalists is a program for individual journalists. Organization accounts are a different product with different terms; a team should not rely on individual accounts for shared credentials.

See: 1Password for Journalists

Exceptions and decisions

  • An account that only a former staff member can reach: use the vendor's documented account-recovery process with proof of organization ownership, and add a second admin immediately afterward.
  • A contractor who needs short-term access: give them their own login with an end date, never a shared staff password.
  • Social accounts registered to a personal phone number: move recovery to an organization number or a shared admin before the person leaves.
  • A tool paid for on a personal card: move billing to an organization card and record the change in the access register.

Offboarding at Harbor Street Review

Fictional example. Names and figures are invented for illustration.

An invented staff member, the audience editor, leaves Harbor Street Review, an invented small literary magazine. The operations lead works through the access register on their last day.

Offboarding checklist, fictional departure
AccountActionTransferred toDone
Email and documentsSuspend login; transfer drive filesManaging editorYes
Team chatDeactivate; archive private channels they ownedOperations leadYes
Newsletter platformRemove admin role; reassign scheduled sendsEditorYes
Social schedulerRemove user; reassign queued postsEditorYes
Password managerRemove from vaults; rotate shared social passwordsOperations leadYes
Design toolRemove from team; keep templates in team folderManaging editorYes
  • Rotating shared passwords matters even when the person leaves on good terms; it confirms the register is complete.

Completion checklist

  • Every account in the register has an organization login, a named admin and a backup admin.
  • Domain, hosting and publishing platform each have at least two admins and two-factor authentication.
  • The password manager has a tested recovery procedure held by two people.
  • The publishing workflow fits on one page and the team has read it.
  • The last departure was offboarded the same day, with ownership transferred.

Sources

  1. Apply for the Slack for Nonprofits discount, Slack. Checked October 14, 2026. Supports: Slack's nonprofit discount excludes several organization types, including organizations that attempt to influence public opinion.
  2. Newspack, Newspack. Checked October 14, 2026. Supports: Newspack is designed exclusively for news organizations. Newspack is built on WordPress and developed and hosted by WordPress.com.
  3. About Newspack, Newspack. Checked November 11, 2026. Supports: Newspack is part of Automattic, built on WordPress and developed and hosted by WordPress.com.

By Jonathan Keen. Content updated November 11, 2026 · first published October 14, 2026.

Disclosure: No commercial relationship: AdminPack receives nothing from the companies named on this page. Links are ordinary links. See the editorial policy.

Something out of date? Suggest a correction. Know a tool or program I should cover? Suggest a tool or program.