EE: Team & Channel Data Retention Policies

Target release

Q4 2020

Epic

https://mattermost.atlassian.net/browse/MM-28837

Edition

E20

Document status

1%

Document owner

@Katie Wiersgalla

Designer

@Michael Gamble (Deactivated)

Tech lead

@Scott Bishel

Technical writers

@Justine Geffen (Deactivated)

QA

@Rohitesh Gupta (Deactivated)

OKR

Improve Team/Channel Administration

Request (CR)

N/A

Request (other)

 

Design Spec

Figma Design, Simple Click Prototype, Hybrid Dropdown Prototype

Technical Spec

https://mattermost.atlassian.net/wiki/spaces/EN/pages/1171947751

Test Plan

 

Objective

Allow system admins to set custom retention policies for messages and files for specific teams and channels.

Background

Our current data retention policies only allow setting retention of files and messages at the global level (see docs). Enterprises (ProductBoard insights) need more granular control of specific teams and channels. Many channels are being used for automated monitoring, which does not require long retention, where channels with collaboration or incident response, require longer retention.

In addition, some users are partitioned into groups that are deemed “regulated” who have different retention requirements than those considered “normal”.

Furthermore, some customers use a channel for automated monitoring or short-term project communications and want resources (messages and files) pinned to the channel to be retained even if the retention policy removes non-pinned information.

Competitively, Slack offers:

MS Teams offers:

Success metrics

Goal

Metric

Goal

Metric

 

 

 

 

User Scenarios

  • System admin can set retention policies for files and messages on a specific team, overriding the system global retention policies.

  • System admin can set retention policies for files and messages on a specific channel, overriding the system global retention policy and any team specific retention policies.

  • System admins can set system-wide retention policies on direct and group messages.

  • End-users are able to understand when data is deleted based on data retention policies.

  • Nice to haves:

    • the ability to exclude pinned posts from data retention policies

    • the ability for channel and team admins to set data retention policies

    • the ability for members to set their own retention schedules for GMs and DMs.

Assumptions

Phases & Milestones

Dec2019Jan2020FebMarAprMayJun5.22 CF5.20 CF
Design
Develop
QA
Launch

iOS App

Android

Areas Touched

  • Permissions

  • System Console UI (Channel Configuration page and permissions)

  • Chat UI when messages and files are deleted

Requirements

Requirement

User Story

Importance

Phase

Jira Issue

Notes

Requirement

User Story

Importance

Phase

Jira Issue

Notes

1

System admin can set retention policies for files and messages on a specific team, overriding the system global retention policies.

 

HIGH

 

 

 

2

System admin can set retention policies for files and messages on a specific channel, overriding the system global retention policy and any team specific retention policies.

 

 

 

 

 

3

System admins can set system-wide retention policies on direct and group messages

 

 

 

 

 

4

End-users are able to understand when data is deleted based on data retention policies

Previous user story: https://mattermost.atlassian.net/browse/MM-10551

 

 

 

 

Open Questions

Question

Answer

Date Answered

Question

Answer

Date Answered

Should we show time in UTC or local time for the admin user?

We will use UTC time and created a ticket to see if we want to make a holistic change across the system console UI (Jira ticket)

1/20/201

How to handle the scheduling component converting days to years?

Brainstorm meeting to be scheduled.

 

Future Iterations

  • Adding data retention policies to the channel management page

  •  

 

Risks:

  • UI in system console being accessible to jr roles who should/should not have access.