Features

Website Content Review: Team Permissions and Publishing Handover

Define team access, review bilingual product changes, assign publishers and hand over website maintenance with a change register, a fictional example and seven

When several people maintain a business website, assign owners for each site, product and language. Have the relevant people review proposed changes, then let a named publisher apply them and check the public pages. Account permissions control access; a review checklist establishes whether the content is correct. A small team can begin with a change register. Teams requiring enforced approval should specify separate candidate versions, approval states and publication permissions in their development scope.

This guide is for marketing staff, product specialists, translators and contractors working together. See the multi-site product data guide for shared product ownership and the maintenance checklist for routine editing. This article focuses on access, review handover and publication responsibility.

1. Define access by site and task

Before creating accounts, list the sites, content types, languages and actions each person needs. Product specialists confirm specifications, marketing prepares page copy, translators check English terminology, and the publisher handles release. One person may hold several responsibilities. Every change needs a reviewer, an operator and a substitute.

ResponsibilityHandover materialAcceptance focus
Product ownerModel, specification evidence, file revisionValues, units and conditions agree
Content editorProposed copy, title and linksCorrect site, record and scope
Language reviewerEnglish differences and terminology evidenceMatching models, specifications and files
PublisherApprovals, original values and release checklistPublic pages match approved content

These responsibilities are an example team arrangement. Turning them into separate system permissions requires checking current roles, endpoints and implementation scope. Site authorization controls cross-site access. Restrictions by category, language, field or individual product require separate verification. Menu screenshots show visible entry points; endpoint results establish whether access controls work.

2. Establish what saving a record does

Test saving a new page and an already published page separately. Saving changes to published copy, English translations, SEO fields or file links may make the new values publicly available immediately. CatchCMS currently updates content records directly. Keep proposed changes in a controlled document or isolated staging environment until the owner approves writing them to the production record. See the staging checklist.

If editors must submit changes while the old version stays online until approval, the project needs a separate candidate version and an approval-to-publication process. Acceptance should cover direct update requests, status changes and MCP operations so that every write path enforces the same rules. Asking editors to consult an owner before saving is a manual process control.

Urgent corrections still need a target URL, original and proposed values, evidence and an operator. For misleading content, the owner decides whether to correct it immediately, temporarily withdraw it or retain verified sections, recording affected languages and files.

3. Use one change register for review and handover

  1. Identify the object: site, content ID, public URL, model, language and requester.
  2. Preserve evidence: original values, proposed values, source revision and the location of supporting files. Keep contracts and customer material in controlled storage.
  3. Review separately: the product owner checks specifications, the language reviewer checks English and PDFs, and marketing checks titles, explanations and enquiry links.
  4. Schedule execution: name the publisher, release window, substitute and recovery owner. Have one person write each record during that window.
  5. Read again before writing: compare the current record with the reviewed original. Merge and obtain fresh confirmation when another person has changed it.
  6. Verify publication: read back the saved record and open the Chinese and English URLs. Record results, exceptions and the person taking over.

Suggested manual states include materials needed, business review, language review, ready to apply and verified, each with a name and timestamp. Later changes can invalidate earlier approval for affected fields, which should return to review. The register and notification arrangements form the team process. Built-in approval flows, review history and automatic reminders require project-specific confirmation.

4. Deliver languages and files as a set

Track Chinese, English, specification tables, image captions and downloads in the same change record. Mark each item as retained, changed or awaiting material. For specification changes, check units, conditions, revision and PDF page references. For English wording changes, confirm the model and meaning. Existing English overrides need explicit updates, and the public result after a base-language change should be checked.

CatchCMS multilingual values use base content and translation overrides. Missing translations and explicit empty values need to be interpreted according to the field rules. Before clearing a value, decide whether the intended result is an empty value, removal of an override or replacement text. Translatable business fields depend on the current model configuration. See the bilingual content checklist.

When one language awaits confirmation, the owner can narrow the release scope and record its owner and follow-up date. For significant changes to safety conditions, market applicability or availability, confirm the required message for every language before arranging release order and temporary notices.

5. A fictional multi-person handover

Fictional example: an equipment company revises the PX-240 maintenance guidance from “every 12 months” to “inspect every 6 months under the specified operating conditions.” The product owner supplies page 8 of the R4 manual. Marketing prepares Chinese, the translator prepares English and the R4 PDF, and the publisher schedules Wednesday. Review the entire sentence and its evidence because both interval and conditions change.

Before writing, the publisher discovers a colleague has added “contact technical support for coastal operating conditions.” The publisher pauses this write, merges the note into the candidate copy and obtains fresh product-owner approval. Only approved fields are submitted, preserving the existing URL, actual publication date and unrelated fields. Public checks cover the new interval in both languages, operating conditions, R4 download and the enquiry link for that model.

The evidence is one record containing target URLs, original and final values, R4 support, two reviewers’ confirmations, saved-value readback, bilingual page results and a recovery owner. Automatic conflict detection, full version history and one-click rollback require separate implementation. See the item-by-item recovery checklist for AI batch corrections.

6. Seven access and handover acceptance checks

  • Use approved test accounts to verify allowed-site reads and writes and rejection of unauthorized-site access through admin pages and management endpoints. Record roles and results.
  • Test read, create, update, delete and status operations individually. Where editing and publishing must be enforced separately, test requests that bypass the interface.
  • Test saving published records. For a manual process, confirm that proposed changes stay in a controlled document or isolated environment. For project-developed approval features, verify that the candidate version stays separate from the live version as specified.
  • Simulate sequential edits on a controlled test record. The second person should identify differences after rereading and obtain renewed approval.
  • Check public bilingual copy, specifications, files, titles, descriptions, language switches and enquiry links, including mobile readability.
  • During staff or contractor departure, revoke old tokens, adjust accounts and site access, test old sessions and tokens individually, and name the new owner.
  • Keep one recovery rehearsal for an incorrect publication: identify usable originals and later valid changes, verify restored public pages and obtain the successor’s sign-off.

Run destructive permission tests, concurrent-edit trials and recovery exercises within an approved testing scope. Record expected and actual outcomes, evidence, owner and recheck date for each item, then confirm release arrangements with outstanding issues visible.

7. CatchCMS scope and frequently asked questions

CatchCMS supports content management within site scope. MCP operations inherit the admin account’s identity and permissions; access tokens support expiry and revocation. Teams can use existing roles and operation permissions to organize maintenance. Language- or field-level restrictions, independent drafts, multi-person approval, concurrency protection and review history require individual project confirmation. See the MCP access guide and multi-site management.

Does a three-person team need an approval system immediately?

Decide whether the system must enforce approval before publication. A small team with infrequent updates and one accountable publisher can use controlled candidate documents and a change register. Multiple contractors or high-risk material may justify enforced approval and separate versions in the implementation scope.

Can an editor account be restricted to English?

Verify language-level access specifically. Site authorization, action permissions and language restrictions need separate acceptance. Specify allowed languages, request parameters and rejected operations, covering both the admin interface and MCP.

What should a departing contractor hand over?

Transfer pending releases, supporting material, current public URLs, exceptions and recovery records. Adjust account authorization, revoke old tokens and test access outcomes. Have the successor complete one controlled update with public readback before accepting maintenance responsibility.

Prepare site counts, languages, editor numbers, update frequency and the steps requiring enforced control, then use project enquiries to confirm delivery scope. Contentful’s roles and workflow explanation also illustrates why editing rights, publication rights and workflow steps need separate definitions; it serves here as a general process reference.