Merge pull request #47 from telerik/niliev/keys

update to the md lists and update the time period for preserving logs

portal/get-started-portal.md

@@ -11,6 +11,7 @@ position: 1
 This tutorial describes how to start using the Fiddler Jam Portal if you have access rights corresponding to the [Portal User role]({% slug fj-users %}#portal-users), and the Extension user has shared the log containing a video recording with you through a link.
 
 - First, you will open the customer-provided generated link with a browser.
+
 - Next, you'll access the default private workspace with stored logs and add the submitted log to it thus sharing the recording with other Portal Users on your team.
 
 ## Prerequisites

portal/portal-logs.md

@@ -16,7 +16,7 @@ The access to the log details depends on the link generation options selected by
 * Links generated through the **Share with specific people** option are accessible only for the specified Fiddler Jam Portal users.
 * Links generated with the **password-protection** option are accessible for Fiddler Jam Portal users aware of the password.
 
-Once [an Extension User]({%slug fj-users%}#extension-users) submits recorded traffic, the log uploads to the Fiddler Jam Portal cloud space. The Fiddler Jam Portal keeps any submitted logs in the storage for 30 days. After that period, if the log is not added to [a workspace]({%slug fj-workspaces%}), it will be automatically deleted.
+Once [an Extension User]({%slug fj-users%}#extension-users) submits recorded traffic, the log uploads to the Fiddler Jam Portal cloud space. The Fiddler Jam Portal keeps any submitted logs in the storage for 31 days. After that period, if the log is not added to [a workspace]({%slug fj-workspaces%}), it will be automatically deleted.
 
 In the Fiddler Jam Portal, any [Portal User]({%slug fj-users%}#user-role) with access rights can save, organize, analyze, and work with the provided records.
 
@@ -27,26 +27,37 @@ When the Extension User submits the log, it is automatically uploaded to the Fid
 Fiddler Jam protects the content of the submitted logs through the following rules:
 
 - All logs are captured with applied masking for [any data Fiddler considers is sensitive]({%slug fj-security%}#masking-sensitive-data).
+
 - The submitted log can be opened only by Portal Users who meet the access rights requirements that the Extension User set through [the link generation options]({%slug fj-link-options%})).
-- The submitted log can be added to a workspace by Portal Users with the respective access rights. Any log that is not added to a workspace will be automatically deleted after 30 days.
+
+- The submitted log can be added to a workspace by Portal Users with the respective access rights. Any log that is not added to a workspace will be automatically deleted after 31 days.
 
 To enable a [Portal Viewer]({%slug fj-users%}#viewer-role) to open the submitted log:
 
 1. The Extension User must set the appropriate access rights during the link generation.
-2. The Portal User must add the log to a workspace.
+
+1. The Portal User must add the log to a workspace.
 
 ## Options for Working with Logs
 
 Once a submitted log gets uploaded to the Fiddler Jam Portal, the Portal provides the following options for managing that log:
 
 - [Using and editing the log details](#log-details) such as its title, description, and so on.
+
 - [Investigating the captured data of the requests and responses](#traffic-inspection)—The session data includes the headers and bodies of each HTTP or HTTPS request and response.
+
 - [Inspecting the browser events](#browser-events)—Each log contains the browser events triggered from user interactions with the page during the recording.
+
 - [Inspecting the taken screenshots](#screenshot-inspection)—When the Extension User explicitly enables the screenshot option, a new screenshot is added for each user interaction on a clickable element.
+
 - [Inspecting the screen recording](#screen-recording)—When the Extension User explicitly enables the **Capture video** option, the whole capturing process is output in the **Screen Recording** tab.
+
 - [Analyzing the developer console logs](#console-log-inspection), which is available when the Extension User has selected the **Capture console** option.
+
 - [Running an advanced investigation through the Fiddler Everywhere web-debugging tool]({%slug fj-advanced-analysis%}#fiddler-everywhere-integration).
+
 - [Exporting the captured data as a HAR file]({%slug fj-advanced-analysis%}#export-har).
+
 - [Adding submitted logs to desired organizational workspaces]({%slug fj-workspaces%}#Aadd-submitted-log-to-workspace).
 
 The capture options of the Fiddler Jam Chrome Extension also provide features for you to mask sensitive data, such as cookies and post-data, and disable the browser cache.
@@ -117,6 +128,7 @@ When **Capture screenshots** is explicitly enabled, the log will also contain sc
 To examine a screenshot:
 
 1. From the **Captured Logs** list, select [a **Click** event line](#browser-events). The associated screenshot loads in the **Inspectors** tab as the last property of the event data.
+
 1. Use the **Save** icon to download the screenshot as a PNG file locally.
 
 The following figure demonstrates a captured click action.

portal/portal-menu.md

@@ -22,8 +22,10 @@ Your information and usage statistics enable the Fiddler team to better understa
 To subscribe or unsubscribe from participating in the sharing of usage statistics:
 
 1. Open **Settings** > **Privacy** (accessible from the account icon in the top-right corner).
-2. Check or uncheck the __Automatically send data to help us improve the product__ option depending on whether you want to send usage statistics.
-3. Click __Save__ to apply the changes.
+
+1. Check or uncheck the __Automatically send data to help us improve the product__ option depending on whether you want to send usage statistics.
+
+1. Click __Save__ to apply the changes.
 
 ## My Resources
 

portal/users.md

@@ -23,8 +23,11 @@ Fiddler Jam refers to the end users, who have recorded and submitted logs throug
 All extension users can capture and record logs, and generate Fiddler Jam Portal links where the logs will be stored.
 
 - Extension users are not limited on the number of recorded logs.
+
 - Extension users are not limited on the number of generated links to recorded logs.
-- A recorded log with a generated link will be stored in the Fiddler Jam Portal for 30 days. After that period, the log is automatically deleted.
+
+- A recorded log with a generated link will be stored in the Fiddler Jam Portal for 31 days. After that period, the log is automatically deleted.
+
 - A recorded log with a generated link that is added to a workspace by a [Portal User](#user-role) will be stored in the Fiddler Jam Portal until a Portal user explicitly removes it.
 
 ## Portal Users
@@ -34,7 +37,9 @@ Even though the Fiddler Jam login accepts custom credentials or Google authentic
 Depending on the user assigned role, the Fiddler Jam portal provides different access levels:
 
 - Unregistered users won't be able to open the Fiddler Jam Portal or load generated Fiddler Jam links.
+
 - Fiddler Jam Portal seats with the Viewer role can only watch logs that are [added to a workspace]({%slug fj-workspaces%}#add-submitted-log-to-workspace). If a Viewer opens a public link, the page that will open will inform the user that the links need to be added to the account workspace.
+
 - Fiddler Jam Portal seats with the User role can open public logs, create and manage workspaces, and manage, add, and remove logs from workspaces.
 
 ### User Role
@@ -46,9 +51,13 @@ A User can view and maintain submitted logs and workspace logs based on the Fidd
 The User seat comes with the following advantages and limitations:
 
 - Users can access all logs that are added to the account workspace. Password-protected logs can only be accessed from users who know the password.
+
 - Users can access logs that are not added to a workspace.
+
 - Users can edit and remove logs that are added to the workspace.
+
 - Users can add shared logs to a workspace. Logs added to a workspace will be accessible to all Viewers.
+
 - Logs [shared with specific people (based on the registered email)]({%slug fj-link-options%}#share-with-specific-people) can be accessed from all Portal users with access to the workspace.
 
 ### Viewer Role
@@ -58,5 +67,7 @@ All subscription plans provide unlimited seats for the Viewer role.
 The Viewer seat comes with the following advantages and limitations:
 
 - Viewers can access all logs that are added to the workspace of the organization. Password-protected logs can only be accessed from a Viewer who knows the password.
+
 - Viewers can't access logs that are not added to a workspace.
+
 - Viewers can't edit and remove logs that are added to the workspace.

portal/workspaces.md

@@ -32,7 +32,7 @@ To rename the default workspace, a Portal User has to:
 
 Any log submitted by an [Extension User]({%slug fj-users%}##extension-users) is initially accessible based on [the predefined link generation options]({%slug fj-link-options%}).
 
-When a Portal User with access rights first opens the submitted link, it won't be part of any workspace. Submitted logs that are not added to a workspace will expire within 30 days. Logs added to an organizational workspace won't expire and can only be removed by the organization users.
+When a Portal User with access rights first opens the submitted link, it won't be part of any workspace. Submitted logs that are not added to a workspace will expire within 31 days. Logs added to an organizational workspace won't expire and can only be removed by the organization users.
 
 A Portal User can add the submitted log to the workspace in the following way: