INTR xx_Example of Functional Requirements

 

The main groups of requirements for the Intranet solution are outlined below.
These are sample requirements; the final list will be informed by Certify OS user needs, and by current tech stack https://wmdemo.atlassian.net/wiki/spaces/CER/pages/196182684

 

REQUIREMENT

REQUIREMENT DESCRIPTION

PRIORITY

REQUIREMENT

REQUIREMENT DESCRIPTION

PRIORITY

UX / UI / BRANDING

Custom Layouts

The solution allows customizing page layouts which then can be exported and imported as a zip folder serving as a template

high

Corporate Branding

The intranet should have a clear and modern look associated with Certify OS’ corporate identity. Achieved with apps:

https://marketplace.atlassian.com/apps/1221322/refined-sites-for-confluence-intranets-documentation-kbs?hosting=cloud&tab=overview

https://marketplace.atlassian.com/apps/1216056/refined-toolkit-for-confluence-cloud?tab=overview&hosting=cloud

high

Filtering and Sorting

The solution allows to created custom filters for content lists and sorting by each column value
Recommended app: https://marketplace.atlassian.com/apps/27447/table-filter-charts-spreadsheets-for-confluence?tab=overview&hosting=cloud

MEDIUM

Multi-Language

The solution supports multiple languages and provides language packs to change the language of the user interface in the CRM application.

MEDIUM

WORKFLOWS AND AUTOMATIONS

Automation Rules System-Based Triggers

The solution allows setting custom workflows for automating processes that do not require any direct user action to activate the rule. It is triggered when predefined, specified conditions are met. Examples: time-based reminders, alerts, notifications, etc.

high

CONTENT SECURITY AND ACCESS

Content Classification

The solution achieves information classification for access control and targeted delivery across Intranet pages

high

2 Types of Visibility and Access Configurations

The solution provides two ways to restrict access to content:

  • Complete Invisibility: Content can be made completely invisible to users who do not have permission. These users will not be able to see the content in search results or in the spaces list.

  • Visible but Inaccessible: Content can be restricted so that users can see it exists, but cannot access it. These users will see an "access denied" message when they try to open the content.

high

Role-based Access

The solution allows to setup access to the Intranet pages with a role-based controlled permission configurations.

high

Granular Permissions Configurations

The solution allows for detailed permission configurations. The following action types can be allowed or restricted for individual users or user roles:

  • view and edit

  • comment, delete own comment

  • delete and archive content

  • upload and download attachments

  • export pages and space(s)

  • create blog posts

  • update permissions for other users

  • view space analytics

high