0% found this document useful (0 votes)
2 views17 pages

Proj

The document outlines a blog-style content publishing platform designed for internal use within an organization, facilitating article publishing, reader engagement, and knowledge sharing. It details user authentication methods, roles and responsibilities of Super Admins, Admins, Editors, Authors, Contributors, Content Moderators, and Readers, as well as the post lifecycle and visibility rules. Additionally, it describes the system's governance, content organization, analytics, and AI/ML integration for moderation and metadata generation.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2 views17 pages

Proj

The document outlines a blog-style content publishing platform designed for internal use within an organization, facilitating article publishing, reader engagement, and knowledge sharing. It details user authentication methods, roles and responsibilities of Super Admins, Admins, Editors, Authors, Contributors, Content Moderators, and Readers, as well as the post lifecycle and visibility rules. Additionally, it describes the system's governance, content organization, analytics, and AI/ML integration for moderation and metadata generation.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Blog-Style Content Publishing Platform

A blog-style platform is required to publish articles internally within the


organization and allow employees to read, interact, and share knowledge.

The platform will support content publishing, reader engagement,


moderation, governance, and controlled distribution across internal
communication channels.

User Authentication

Users can log in using the organization’s existing authentication systems.

Supported login methods:

 Bank SSO login using PF number (PF-based authentication)

 Azure Email ID login using email address

Example Login Flow

Employee

├ PF Login (SSO)

└ Azure Email Login


Access Platform

Super Admin

The Super Admin is responsible for the overall governance and structure
of the platform.

Responsibilities

 Responsible for overall platform governance

 Manages system configuration and master data

 Creates and maintains Channel Master

 Creates and maintains Category Master

 Creates and maintains Sub-Category Master

 Creates and maintains Post Visibility Master

 Defines standard visibility groups


Example Visibility Groups

Group Members

All Entire
Employees organization

IT
IT employees
Department

HR
HR employees
Department

Custom Selected PF
Group numbers

Visibility Rules

Posts may be restricted based on:

 Department based visibility

 Machine IP based visibility

 Custom groups (selected email IDs or PF numbers)

Additional Responsibilities

Super Admin also manages the following system masters:

 Archival Policy Master

 Post Distribution Channel Master

Approved Distribution Platforms

Posts may be distributed through:

 Email

 Microsoft Teams

 SharePoint

 Internal portal

 Mobile application

 WhatsApp (if allowed by organizational policy)

Distribution channels may also be restricted based on Channel,


Category, or Sub-Category.
Admin

The Admin manages users on the platform.

Responsibilities

 Create users

 Manage user accounts

 Assign roles to users

Available Roles

Role

Editor

Author

Contributor

Content
Moderator

Reader

Additional Responsibility

 Deactivate users when required

Example situations:

 Employee leaves the organization

 Employee should no longer access the platform

Admin Example Flow

Admin

├ Create User
├ Assign Role
└ Deactivate User

Post Creation Rule

Every post must follow certain rules before it can be created.

 A post must have at least 2–3 Editors assigned

 A post cannot be created without assigning editors


 All Editors have equal authority over the post

Example

Post
├ Editor 1
├ Editor 2
└ Editor 3

Editor

Editors are responsible for reviewing, approving, and publishing posts.

Editors perform the following actions

 Select Channel

 Select Category

 Select Sub-Category

 Select Visibility Group

 Select Distribution Channels

 Select Archival Policy

Editors can also

 Soft delete posts

 Update posts

 Republish posts

 Schedule publishing

Scheduling Example

Post Created

├ Publish Immediately

└ Publish on Future Date

Post Content Types

Posts may contain:

 Text

 Audio
 Video

 Images

 Interactive polls

 Surveys

Editors can recall a scheduled post before publishing.

Author

Authors are responsible for creating the content.

Responsibilities

 Create posts

 Update posts before publishing

 Submit posts to Editors for approval

 Cannot publish posts directly

Author Workflow Example

Author


Create Draft


Submit to Editors

Contributor

Contributors help Authors improve the content.

 A post may have zero or multiple contributors

Example

Post
├ Author
├ Contributor
└ Contributor

Content Moderator
Content Moderators manage reader behaviour and interactions.

Moderators can

 Block or unblock unruly readers

 Restrict reader interactions

 Delete inappropriate comments

 Block likes or dislikes if required

Moderation works together with AI/ML moderation tools.

Reader

Readers interact with published posts.

Readers can

 View posts

 Comment on posts

 Like posts

 Dislike posts

All comments are checked by AI moderation before appearing.

Readers can also:

 Suggest corrections

 Share posts through distribution channels

 Subscribe to authors

 Subscribe to categories

 Subscribe to distribution channels

Reader Interaction Example

Reader

├ View Post
├ Comment
├ Like / Dislike
└ Suggest Correction

Post Lifecycle
Every post goes through a defined lifecycle.

Draft


Under Review


Approved

├ Scheduled
│ │
│ ▼
│ Published

└────────► Published


Archived

Workflow

1. Author creates Draft

2. Author submits post for review

3. Editors review the post

4. Post becomes Published or Scheduled

5. Post is archived automatically based on archival policy

Post Version Control

Every update creates a new version of the post.

Example

Versio
Description
n

V1 Initial post

Updated after
V2
correction

V3 Latest version

Readers always see only the latest approved version.


AI / ML Content Review

AI automatically scans posts and comments for issues.

AI checks for

 Offensive language

 Sensitive information

 Policy violations

Moderation Flow

Reader Comment


AI Moderation


Content Moderator


Comment Published

Editors make the final publishing decision.

Audit Logging

The system records all important activities.

Logged activities include

 Post creation

 Post updates

 Publishing

 Deletion

 Visibility changes

 Moderation actions

 Role assignments

Example Log Entry


User Action Time Post

Editor Published 10:45 Post


1 Post AM #345

Content Structure

Posts are organized in a hierarchical structure.

Channel


Category


Sub-Category


Post

Example

Technology & IT

└ Cyber Security

└ Security Alerts

└ Post

Post Structure

Post
├ Editor 1
├ Editor 2
├ Editor 3
├ Author
├ Contributor
└ Contributor

Post Visibility

Visibility is controlled by predefined rules.


Possible Visibility Types

 Department

 Internal Network

 Custom Groups

 Organization-wide

Example

Post Visible To

IT
Cyber Security Alert
Department

HR
HR Policy Update
Employees

Company All
Announcement Employees

Content Organization

Posts can be organized by:

 Date

 Topic

 Category

Important posts can be Featured or Pinned for better visibility.

Personalization

Users may have personalized experiences.

Features

 Personal dashboards

 Subscriptions to authors

 Subscriptions to categories

 Subscriptions to distribution channels

Example Dashboard
My Dashboard
├ Recent Posts
├ Subscribed Authors
├ Trending Posts
└ Notifications

Analytics & Insights

The platform tracks engagement metrics.

Metrics include

 Post views

 Comments

 Shares

Example Analytics

View Commen
Post
s ts

Security
540 18
Alert

HR Policy 320 12

The system may also perform sentiment analysis on reader feedback.

Master Data Examples

Channel Master

Channel
Channel Name
ID

Corporate
CH001
Communication

CH002 Technology & IT

HR & Employee
CH003
Engagement

CH004 Risk & Compliance

CH005 Knowledge Sharing


Category Master

Category Channel

General Corporate
Announcements Communication

IT Infrastructure Technology & IT

Cyber Security Technology & IT

HR & Employee
HR Policies
Engagement

Sub-Category Master

Sub-Category Category

Server IT
Maintenance Infrastructure

IT
Network Updates
Infrastructure

Cyber
Security Alerts
Security

Archival Policy Master

Archive
Policy
After

Short Term 30 days

Medium Term 90 days

Long Term 1 year

Permanent
Never
Knowledge

Distribution Channel Master


Channel Platform

Email Corporate email

Teams Microsoft Teams

SharePoin
SharePoint portal
t

Portal Internal intranet

Mobile Mobile
App notifications

WhatsAp Approved
p messaging

Example Post Configuration

Example when an Editor creates a post:

Field Value

Channel Technology & IT

Category Cyber Security

SubCategor
Security Alerts
y

Cyber Security
Visibility
Team

Archival Medium Term (90


Policy days)

Distribution Email + Teams

Governance Flow

Super Admin


Create Masters
(Channel / Category / Visibility / Distribution)

Admin


Create Users & Assign Roles

Editors


Create & Publish Posts

Content Moderators


Moderate Comments

Readers


Read / Comment / Interact

System Flow

Author / Contributor


Draft Post


Editors Review


Publish Post


Distribution Channels
(Email / Teams / Portal)


Readers


AI Moderation + Moderators
AIML Chat
Author writes blog


Editors approve blog


Blog Published


Metadata + Keywords Extracted


Content Chunked


Embeddings Generated (Azure OpenAI)


Stored in Azure AI Search Vector Index


Employee asks question


Vector Search retrieves blog content


Azure OpenAI generates answer


Answer returned to user

Blog Platform


Blog Published


Metadata + Keywords


Content Chunking


Embedding Generation

(Azure OpenAI)


Azure AI Search Index


AI Chat Assistant

(Azure OpenAI)


Employee Question Answered
Metadata Generation

When the blog is published, the system extracts metadata.

Example metadata object:

{
post_id: "1001",
title: "Cyber Security Alert",
channel: "Technology & IT",
category: "Cyber Security",
subcategory: "Security Alerts",
author: "John Doe",
editors: ["Editor1","Editor2"],
contributors: ["Contributor1"],
keywords: ["ransomware","malware","phishing"],
visibility_group: "IT Department",
publish_date: "2025-03-10"
}

Keywords can be:

 manually added by the Author

 automatically extracted by AI

Example keywords:

ransomware
malware
phishing
email security
cyber attack

You might also like