Skip to Content
HelpProjectsContent Editor

Content Editor

In ScopeStack, there are two primary workflows for adding services to projects:

  1. Standard content that is defined in settings.
  2. Custom content that is created on a per-project basis.

Standard Content

Defining in Settings

Standard content lets you pre-define all aspects of a service so it’s fast and convenient to build and scope your projects.

Adding to a Project

When you add standard content to a project, it’s effectively copied into the project. Later changes made to the service in settings won’t affect copies already in a project. After it’s been added, you can update parameters like Service Descriptions and Language Field information on a per-project basis.

  • Changes made to language in a project are localized to that project.
  • If you duplicate a project, the service in the source project is used as the basis for duplication, including any language updates made there.
  • If you change standard content in Settings, those changes won’t update existing projects’ versions of that content. When the content is added to a new project after the update, the changes will be reflected in that new project.

Custom Content

Building in a Project

Custom content can be defined on a per-project basis. All attributes are editable within the project and can be changed at any time.

If you duplicate a project that contains custom services, the custom services carry over into the duplicated project.

Text Editor

Rich text fields throughout ScopeStack — including Service Descriptions, Language fields, Executive Summary, and Terms & Conditions — use a streamlined text editor with a single unified toolbar.

On this screen: A rich text editor shows a single unified toolbar at the top containing formatting buttons: Bold, Italic, and other inline style controls, plus Bulleted List and Numbered List buttons. The text editing area appears below the toolbar. Common keyboard shortcuts (such as Cmd+B for bold) work within the editor.

Formatting options include:

  • Bold, italic, and other inline styles
  • Bulleted and numbered lists
  • Common keyboard shortcuts (for example, Ctrl+B or Cmd+B for bold)

For fields that accept raw HTML, an HTML textarea is available below the visual editor. The textarea is resizable so you can work comfortably with longer markup.

On this screen: Below the visual rich text editor, a raw HTML textarea is visible for fields that accept HTML input. A resize handle in the bottom-right corner of the textarea allows the user to drag it taller or shorter to accommodate longer markup comfortably.

Merge fields in service content

Service Descriptions and Subservice language fields support dynamic merge fields. You can insert project-specific data by wrapping the field name in double curly braces inside the editor:

{{client_name}} — the client's name
{{service_name}} — the service name
{{subservice_name}} — the subservice name (subservices only)
{{quantity}} — the quantity of the service or subservice
{{extended_hours}} — total calculated hours based on quantity
{{business_unit_name}} — business unit name
{{service_location_name}} — service location name
{{service_location_address}} — service location address
{{service_location_remote?}} — whether the location is remote

These fields are resolved at document generation time and pull live values from the project.

Last updated on
AttachmentsTravel & Expense