Skip to content
  • There are no suggestions because the search field is empty.

Content & Release Management Overview

Organizing, providing, and managing resources to users in your Centercode site

The Content/Release management page in Centercode allows admins to create, organize, and maintain resources essential to their testing initiatives. This page provides tools to add new resources, modify existing ones, assign access permissions, and track engagement through views and status indicators. With options to notify users, clone, or archive resources, this interface ensures efficient management of test materials and documentation throughout the project.  

Accessing Content and Releases

For Community-level Content:

  1. Click the Community logo in the top-left navigation menu
  2. Click Community management 
  3. Select Content

For Project-level Content and Releases:

  1. From within your project, click the Management menu 
  2. Select Content or Releases


Note: "Resource" is a placeholder term used to refer to content and/or releases.
  1. Add resource: Click to create and add a new resource to the project.
  2. Add a resource type: Define a new resource type to categorize similar resources.
  3. View archive: Access previously archived resources for review, permanent removal, or restoration.
  4. Modify this resource type: Edit settings and attributes for the selected resource type.
    1. Make accessible in project search: Enable this resource type to appear in project-wide search results.
    2. Show on project home: Display this resource on the project homepage.
    3. Show in project menu: Add this resource type to the project’s navigation menu for quick access.
    4. Only allow one active piece of content at a time: Restrict this resource type to a single active resource at any given time.
    5. Only allow one active notice at a time: Ensure only one active notice is visible to users at a time.
    6. Allow users to add reactions: Enable reactions to let users interact with resource.
    7. Visual style: Customize the appearance and formatting of this resource type (separated by date, table format, single page format, or numbered list)
    8. Team access: Define which team members can view, edit, or manage this resource type.
  5. New resource: A newly added resource under the selected resource type.
  6. Archive resource type: Remove the resource type from active view by sending it to the archive.
  7. Modify resource: Edit the details, content, or attributes of an existing resource.
  8. View resource: Open and review the selected resource's content and details.
  9. Notify users: Send notifications to users regarding updates or changes to this resource. Learn more Notify and Remind
  10. Clone resource: Duplicate an existing resource for reuse or modification.
  11. Archive resource: Remove the selected resource from active use and store it in the archive.
  12. Resource status: Displays whether the resource is live, incomplete, or expired.
  13. Resource views: Shows the number of times the resource has been accessed.
  14. Resource view access: Manage and assign team permissions to view the resource.

Saving your changes to a Release

When you create or modify a Release, you have two ways to commit what you've entered. Both save your work identically. The difference is only where you land afterward.

  • Save progress: saves your changes and keeps you on the Release form. Use this when you're partway through a longer edit and want to keep working, or when you want to be sure your work is stored before you attach a file or step away.
  • Submit: saves your changes and returns you to the Content and Release list.

Neither button controls whether testers can see the Release. Visibility is governed by the resource's status and its Team Access settings, so saving with either control never publishes something you weren't ready to share.

💡 Ted Tip: I use Save progress as a habit on any Release I'm building out with several files or a long description. It costs nothing, and it means a browser refresh or a timed-out session doesn't take the whole entry with it. I save Submit for the moment I'm genuinely finished and want to get back to the list.

What do the status icons mean?

Live Customer Team Access : A full green circle indicates that your resource is published, and at least one particpant or applicant level team has submit/view access

Live Internal Team Access : A half full green circle indicates that your resource is published, at least one admin or support team has view/submit access, and NO participant or applicant level teams have view/submitt access

Live No Access : An empty green circle indicates that your resource is published, and NO teams have view/submit access

Incomplete Resource : A full blue circle indicates that your resource is not yet published

Expired Customer Access : A full red circle indicates that your resource is published, a participant or applicant level team is set to have view/submit access, but that the resource has an expiration date that has already passed

Resource status icon notes

  • Status icons exist for all relevant resources (Content, Tasks, etc).
  • The filled nature of each bulb indicates the general type of user who has access to it.
  • Full bulbs are publicly accessible (meaning 1 or more Participants or Applicants have access)
  • Half-full bulbs are internally accessible (meaning 1 or more Administrators or Internal Teams have access).
  • Empty bulbs are not accessible by anyone (outside of the administrative interface).

Requirements

  • Manage content role (Community and Project)
  • Manage releases role (Project)

Notes

  • Save progress and Submit store your changes the same way. Neither one leaves the Release in a draft state that the other completes.
  • Whether testers can see a Release is controlled by its status and Team Access, not by which save control you used.

  • If you would like to restore or permanently remove a resource navigate to the resource archive, hover, and select the Restore or Remove icon option for the desired resource.