Skip to main content

Configurable and Non-Configurable Items in Cognota

Written by Asia Ali

Configurable in Cognota

  • Platform Currency: Administrators can configure the platform currency to match the organization's preferred currency for managing project budget.

  • Users: Administrators have the ability to manage user accounts, including adding and deactivating, and removing admin permissions.

  • Team/Organization Structure: Administrators can define and adjust the team or organization structure within Cognota to reflect the company's hierarchy and reporting lines.

  • Learning Request Portal Name and Landing Page: Customization options are available for naming the learning request portal and designing its landing page to align with the organization's branding and messaging.

  • Request Forms: Administrators can create and customize request forms to collect specific information from users when submitting learning requests.

  • Project Processes: Cognota allows administrators to configure project processes, defining workflows and stages that projects must progress through from initiation to completion.

  • Project Templates: Administrators can create and customize project templates, pre-defining project structures or key requirements to streamline project setup and management.

  • Task Bundles: Cognota offers the ability to create and manage task bundles, grouping related tasks together for efficient assignment and tracking.

  • Custom Fields for Project Templates: Administrators can add custom fields to project templates to capture additional project-specific information as needed.

Non-Configurable in Cognota (System Fields)

System fields are built into Cognota. You can't rename or remove them. Fields marked * are required.

Project Templates

  • Template Overview tab (information about the template itself):
    Title*, Template Creator (filled in automatically), Description*, Template Owner (defaults to the creator), Assigned Teams

  • Build Template tab, Project Sections (fields on every project created from the template): Project Name*, Business Unit, Description, Project Category, Start Date*, Target Completion Date*, Target Launch Date, Status, Priority, Health

  • Any field below the system fields, added with Add more fields, is a custom field.

Request Forms

  • Form Details tab (settings for the form itself):
    Active (on/off toggle), Name* (up to 255 characters), Description*, Business Units*, Request Type*, Default Request Owner* (defaults to the form creator)

  • Form Builder tab, Request Details page:
    These default fields can't be removed from any form, because a request can't be created without them. Their settings are limited.

  • Default Fields (visible to requesters): Request Title*, Requesters*, Business Unit*, Description

  • Default Internal Use Fields (visible only to learning team users): Owners*, Reviewers, Business Reviewers, Internal Priority* (defaults to Medium)

Any other question on a request form was added by your team. Admins and Power Users can edit it in the form's Form Builder tab, even after the form is live.

Exceptions

Project Category: Project Category is a system field on projects, but the Cognota team can change its dropdown options for you on the backend. Contact support to request a change.

Business Unit: The Business Unit dropdown pulls its options from the business teams configured in your account. To add, rename, or remove an option, update your teams in your Settings > Teams. You can't edit the dropdown directly.

How to tell if a field can be edited

  • On a project: If a field isn't in the project system field list above, it's a custom field. To confirm, go to Settings > Configurations > Fields. If it's listed there, admins and power users can rename it and edit its options. Changes apply automatically to all new and existing projects that use the field.

  • On a request form: If a field isn't in the request form system field list above, it's a question your team added. Edit it in Request Forms, in that form's Form Builder tab. Request form fields are never custom fields, so they don't appear in Settings > Configurations > Fields.

Did this answer your question?