{"id":3054,"date":"2026-11-19T11:03:59","date_gmt":"2026-11-19T09:03:59","guid":{"rendered":"https:\/\/www.kaarne.fi\/superstore\/?p=3054"},"modified":"2026-11-19T11:05:13","modified_gmt":"2026-11-19T09:05:13","slug":"who-should-be-able-to-comment-on-a-staging-website","status":"publish","type":"post","link":"https:\/\/www.kaarne.fi\/superstore\/articles\/who-should-be-able-to-comment-on-a-staging-website\/","title":{"rendered":"Who Should Be Able to Comment on a Staging Website?"},"content":{"rendered":"<p>A reviewer needs to point out an incorrect delivery statement on a staging page. Giving them an administrator account would make the invitation easy to send, but it would also answer many access questions nobody has asked. Begin with the task they need to complete.<\/p>\n<h2>Separate viewing, feedback and changing the site<\/h2>\n<p>Consider a fictional small web team inviting an offer owner, an external copy reviewer and a technical maintainer to inspect a draft. The offer owner needs to judge facts. The reviewer needs to report wording problems. The maintainer needs to implement approved changes. Those tasks do not automatically require the same access.<\/p>\n<p>Make a short matrix before choosing accounts or links. Use columns for the material visible, permitted action, identity requirement, access owner and review end point. Add a separate row if someone genuinely needs to edit content; do not hide editing inside the word \u201creview.\u201d<\/p>\n<h2>Write the requirements in ordinary language<\/h2>\n<p>For this team&#8217;s draft, the matrix might say:<\/p>\n<ul>\n<li><strong>Offer owner:<\/strong> view the named draft and leave factual findings; no need to change site configuration.<\/li>\n<li><strong>External reviewer:<\/strong> view the agreed campaign material and submit wording comments; no need to browse unrelated private pages.<\/li>\n<li><strong>Maintainer:<\/strong> edit the agreed content or configuration through their existing authorised process.<\/li>\n<li><strong>Review coordinator:<\/strong> invite participants, track findings and arrange removal of access when the review ends.<\/li>\n<\/ul>\n<p>These are requirements to evaluate, not claims that a particular plugin or WordPress role implements every boundary. A role label is only useful when the actual permissions match the intended task.<\/p>\n<h2>Check the controls at each layer<\/h2>\n<p>Staging access can involve hosting controls, WordPress accounts and a feedback service&#8217;s own permissions. Establish which layer permits viewing the page and which permits submitting or managing feedback. Do not assume a feedback invitation also restricts the website, or that being signed in to WordPress grants access to a separate service.<\/p>\n<p><a href=\"https:\/\/wordpress.org\/documentation\/article\/roles-and-capabilities\/\" target=\"_blank\" rel=\"noopener\">WordPress&#8217;s official roles documentation<\/a> describes roles as sets of capabilities that can be modified. Its default Subscriber is not a dedicated website-review role, and Editor can manage and publish other users&#8217; posts. Verify the configured capabilities and the feedback system&#8217;s documented requirements instead of assigning a familiar role by its name.<\/p>\n<h2>Inspect the participant&#8217;s route with harmless material<\/h2>\n<p>Use a representative test account or invitation, with authorisation, to try the intended actions. Can that participant see the named page, submit a finding and return to the relevant discussion? Check the boundaries too: can they reach unrelated material or perform changes that are outside the brief?<\/p>\n<p>Record the result for the actual environment and account used. A successful test establishes those observations, not a general security certification. If a required boundary cannot be met, choose another supported review arrangement or adjust the material being exposed before sending real draft content.<\/p>\n<h2>Give the review an end<\/h2>\n<p>Name who will remove or change access, and what event triggers that action. Consider the website account, hosting access and feedback invitation separately when they are separate controls. Preserve decisions and useful findings through the agreed project record without assuming that removing an account necessarily deletes its comments.<\/p>\n<p>Recheck access when a participant&#8217;s job changes or another page enters the review. The original matrix should help you notice that the invitation&#8217;s scope has expanded. It should not become a permanent justification for permissions nobody still needs.<\/p>\n<p>Start with what each participant needs to do and what material they need to see. Use that map when checking the actual access controls of a website feedback tool.<\/p>\n<p>For the work around access, read about <a href=\"https:\/\/www.kaarne.fi\/superstore\/articles\/give-each-campaign-reviewer-a-question-they-can-answer\/\">assigning clear review questions<\/a> and <a href=\"https:\/\/www.kaarne.fi\/superstore\/articles\/give-the-next-web-coordinator-a-map-of-open-decisions\/\">handing unresolved page decisions to the next coordinator<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Viewing a draft, commenting on it and changing the website are different jobs. Use a participant matrix before choosing roles or invitations.<\/p>\n","protected":false},"author":1,"featured_media":3090,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_hide_featured_image":false,"_jetpack_featured_image_duplicate_dismissed":0,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[35],"tags":[],"class_list":["post-3054","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai-digital-tools"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/www.kaarne.fi\/superstore\/wp-content\/uploads\/sites\/7\/2026\/11\/np-09-01.webp","_links":{"self":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3054","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/comments?post=3054"}],"version-history":[{"count":7,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3054\/revisions"}],"predecessor-version":[{"id":3196,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3054\/revisions\/3196"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/media\/3090"}],"wp:attachment":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/media?parent=3054"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/categories?post=3054"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/tags?post=3054"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}