SHAREABLE IDEAS FOR ADDING NEW, DEVELOPING CONTENTS AND FEATURES TO ZENDESK SELL PLATFORM - SECURITY ASPECTS FOR ADMIN'S PERSONAL REPOSITORY
Dear "Sell Community" members and moderators,
I am a new user who acquired a paid version through license provision, by choosing the TEAM PLAN for one seated admin.
Overall, I experienced the SELL features for a while (by also looking at the API conditions and extending the parameters of the software for job-related tasks by adding new API-based elements) and I have to say it is quite straightforward and relatively easy to use for CXM and building efficient, constant relational bonding between the vendor/seller/agent and their customers' basin or procurement area.
Moreover, I already had the pleasure to talk with community managers and speak with a moderator of the platform via video chatting, and I got some useful answers and observations for understanding the structuring of the SELL app and where it is aiming at.
That said, I thought to provide some ideas worth sharing, hopefully, in order to see and test - obviously among the members and devs of the app - whether the company might think to implement some "external, additional content" that is not strictly driven by statistical approach or customers' handling approaches, instead pointing to cybersecurity aspects: in other words, adding defined, sequential coding that can ensure a strong form of security proofing (possibly, looking at cyberimmunity methodology).
Hence, I studied some articles for setting up a fictional coding (by looking at definitions and examples) and, up to now, I was reflecting about the format of the "MANAGE REPOSITORY" element that can be accessed by the licensed admin. For this reason, I have written some explanatory definitions of the project which may be considered to test for you, followed by fictional codification. Each explained step of the project is given first as defined theory and then developed through codings.
That said, this is the first part of the plan I am aiming at for the SELL app. The key objective is to keep all development under one purchased license, although I suspect for the "public repository" creation there could be need of adding a second paying admin. However, I would like to understand whether my codes are enough performing: I tried to build up an understandable structure but I imagine the encoders are full of errors. That said, for the ones who could be interested, I would like to receive some feedback and see where to improve: of course, it is a kind of reasoning I do if and only if my "PERSONAL MANAGE REPOSITORY" reflections are good enough to achieve this initial datum of extended cybersecurity.
HERE THE FULL DOWNLOADABLE CODING (last attached phrase) I CAME UP WITH - Version 1.0 ENG and hopefully already fully formed for the ideas I try to trasmit to you.
Thanks in advance for addressing my post and looking at what I have until now. If positively examined, I plan to go on and extend to new topics.