Application Manager

The Application Manager enables system administrators to efficiently manage site applications and access controls. It provides functionalities for adding, organizing, and configuring applications and sections, and assigning permissions to users and groups across the system.

Sections and Applications Management

Section: A grouping of multiple applications under a heading in the top navigation bar. Applications within a section appear as a drop-down list under the section header.

Adding a Section

1. From the main menu, navigate to the Admin Tools. 
2. Click Application Manager. 
3. Click the Add New drop-down menu.
4. Select Add Section.
5. Fill in the following fields:
   • Section Name: Enter the name of what you want the section drop-down to be. 
   • Description: Enter a description for the section, if desired.
     
   • Settings. You have the following settings to leverage. 
     
     Disable Application:
     This setting lets you deactivate the application, removing it from the top navigation menu. When disabled, the application is hidden from users but remains in the system and can be re-enabled at any time.
     
     

     Turn on Mobile Version:
     This option enables the mobile-optimized version of the application, ensuring a better user experience on mobile devices. When activated, the application will be accessible via mobile interfaces.

     
     
   • Permissions Tab: Click the Permissions tab to determine which groups or users can see the new section. 
6. Click Save New.

Adding an Application

1. Go to the Add New dropdown menu.
2. Select Add Application.
   
3. Specify the application type (e.g., Dashboard, Resource Manager, Workspace).
4. Complete the following General fields:
   • Title: The official name or designation of the application, module, or field as it appears in the user interface. To give users a clear and recognizable name for the element being configured or managed. If configuring a new form or section, the Title might be “New Employee Onboarding”.
   • Label Name: The text next to a form field or control within the application. Use this to help users understand what type of data or input is expected in that field. A label name might be “First Name” for a text entry field in a user profile form.

   • Description: A longer explanation or help text that provides additional context or instructions about the field, form, or module. This is to assist users in understanding how to use a field or what kind of input is required. Often shown as a tooltip or below the field. Example: “Enter the employee’s legal first name as it appears on official documents.”
     

Settings

Settings will vary depending on the application type you select. The following is meant as a general overview using the Project List type.

1. Settings: Configuration options that control the behavior, visibility, formatting, validation, or other properties of the field or component. Use this to customize how the field or module functions within the application environment.
   • Create Button Text: The customizable text that appears on the button used to initiate the creation of a new project. Use this to align the button label with the organization’s terminology or workflow context, enhancing clarity for users. For example, instead of the default “Create Project,” you might use “Start Campaign” or “Launch Initiative,” depending on your team's naming conventions.
   • Project Type Text: The label used to identify or categorize the type of project being created or managed.Purpose: To clarify what kind of project is being selected or created, allowing customization to reflect business-specific classifications.
     Example: You could rename this to “Campaign Type,” “Workstream Category,” or “Engagement Type” to better suit your team's use case.
   • Rename Project: This setting or label allows users to change the name of an existing project after it has been created. This allows editing the project title as project scopes evolve or naming corrections are needed. An example might be “Rename Project,” but you can change it to something like “Update Title” or “Edit Project Name” to suit your organization's tone or terminology.
     
   • Rename Pipeline Project: This option allows customization of the label or command used for renaming projects that are part of a pipeline workflow. Use this to match your team’s terminology and provide a clear action label for renaming pipeline-specific projects. For example, you could change it from “Rename Pipeline Project” to “Edit Opportunity Name” or “Update Stage Title,” depending on how pipeline projects are used in your organization.
   • Select View Types: This lets administrators choose which layout or interface views are available for users managing projects in this section. Use this to control the display options for section data, enabling users to work in the format that best fits their role or workflow. For example, you might enable the Kanban and List views for task tracking, but disable Gantt if it’s irrelevant to your team.
   • Enable Doc Export: This toggles the ability for users to export project data into downloadable documents (e.g., PDF, Word). This supports reporting, sharing, or offline access by allowing users to export key project information. Enabling this might allow users to generate a project summary document for stakeholder presentations.
   • Show Pipeline Projects View: This enables or disables the display of the Pipeline Projects View within the selected application section. It helps to determine whether users can see and access pipeline-style views (typically used for opportunity tracking, stage-based workflows, etc.). If your team doesn’t use pipeline-based project tracking, you might disable this view to streamline the interface.
   • Select the Types of Projects that can be created in this section. This allows administrators to define which project templates or types are available for creation within a specific section or workspace. This helps to ensure users create appropriate project types in the proper context, maintain consistency, and reduce clutter. In the Marketing section, you may only allow “Campaign,” “Creative Brief,” and “Content Production” project types.
2. Click Save.

Permissions and User Access

Click the Permissions tab to assign, View, Edit, or Admin permissions to individual users or groups.

Note:

Super Admin and System Admin roles have unrestricted access to all modules regardless of specific permissions. 

Access to creating new workboxes in the Files area can be restricted based on user permissions. Users with View access can see the Files area, but only users with Admin access can create new workboxes.

Additionally, in the Reports section, you can customize the header of Excel exports by appending a logo and tailored messaging or verbiage.

Nested Permission Groups

When groups with access to a specific section or area are displayed, any nested (child) groups within a parent group are also shown.

For example, if a parent group is assigned access to the Projects section, all nested (child) groups within that parent will be displayed when creating a new project. Users can individually assign the project to either the parent group or any of its nested groups.

This functionality ensures that access and assignment options reflect the whole hierarchy of groups, providing greater flexibility and control over project visibility and ownership.