Features request:

• Space Channels (Pro) - it would be nice to streamline posts into Channels created by Admin where users can submit subject specific posts. Currently we have everything in one long conversation and it is hard to track subjects.

  Note: in addition it might be really difficult for the user to be aware of what was already shared (especially all the valuable knowledge and cases) if there is no automatic mark: "Read already" (case where the user already saw that post for 2..4 sec).

  In our case we could have Channels like: General Conversation (default), Feature Request, Bug Fixes so for a new joiner it is easy to focus on specific subject not on everything etc.

• Ability for Admin/Manager to submit a shortcode (Pro) into the post/comment etc so the user could see a mini fForm/fBooking callendar/etc inside that post/PM chat - and user could fill and submit data directly from post.

  Admin/Manager could also configure what shortcodes can be inserted in advance so it could be selected from drop-down list once the admin click icon: Insert...

  When a shortcode is added to the post the fForm could be even visible below the post (same as survey) so more space could be visible for that fForm on the screen.

• Add to the post/comment kebab icon option (visible for Admin/Manager) called: Add to Tasks - in case fBoard integration is configured.

  Example: if someone is requesting any action in the Post and it requires any additional action from the Admin/Manager/Teacher "To Do" then the post/comment content could be added to the fBoard fast.

  In this case the post content would go to a task in the fBoard.

  Once the task is being completed in fBoards then the Admin could click the link to that post and back to it and manually reply to that Post with the outcome. It could be also automated: when the Task is marked as completed in fBoards an automatic reply/comment would be posted in fCommunity with the last comment from the fBoard).

• Limiting historical data storage (by default: 12 months back - in Free couldn't be changed).

  Admin could specify how long the data from posts, comments, chats and their attachments are stored in WP DB. Once a month this task would run and remove content >12 months back.

  In Pro Admin/Manager could change and specify the period.

  Data related to courses module would be stored as long as WP Admin will delete it.

  For Public view and not logged users and/or free users the Preview Historical Data could be limited to 1 month back (so if the user is not Paid then he cannot see all historical content although the historical data is stored for longed period) etc.

• User Sensitive Data label (Pro?) for post/comments.

  Since the user might wanted to remove his data form the fCommunity (only) due to some personal information provided in the posts we could enable possibility for marking posts/comments with User Sensitive Data label.

  User Sensitive Data labels can be visible only to the user (and Admins) - nobody else can see them (there is no need for it).

  By default all posts have Public label but users could select it during posts/comments creation/edition. In that way if the user requests his account deletion from fCommunity only those posts/comments with User Sensitive User Data label would be removed.

  Users would have limits in using Usee Sensitive Data label (max 1 per day) so they will be aware that they need to publish only Public content (not the sensitive one) and the user is aware that the content (other than User Sensitive Data) will remain once the user will request his data to be removed from the fCommunity.

  In this way the Admin will be complied with the GDPR when user data deletion is requested.