Modern Workplace management with Enterprise Mobility + Security- part 3

In my second post, I started with identity and client apps/cloud services as part of the workplace and their Layer of Controls within EM+S. In this post, I would like to discuss data/content and devices. Don’t forget, It is the combination of Layers of Control which make the EM+S solution powerful. Also, I’m purely discussing the Enterprise Mobility + Security Layers of Control. Within Windows you will find more controls and the same for O365. These last area’s aren’t my expertise but do investigate the controls in these products.

Data/content:

The Layer of Control EM+S has to offer regarding data/content is Azure Information Protection. With AIP you can Label, classify and protect data/content, and make sure only the right people can open and modify content. You also can track usage of your document and revoke access if needed. I wrote a more detailed post on AIP which you can read here. A great additional layer on top of MAM policies on the Office apps or Windows Information Protection. AIP is one of the great tools regarding the coming GDPR.

 

Device management:

Last layer of control EM+S has to offer when you look at the device level is Intune. Intune offers a platform to manage all your devices whether those are Apple, Microsoft or Android devices. Sometimes you hear that this is “modern device management vs legacy device management”: lightly managed/Intune/AAD/policies vs fully managed/SCCM/AD/GPO’s

I’m aware that some customers require more features than what Intune has to offer today. SCCM can do a lot more on the Windows platform than Intune. Legacy Win32 app distribution is one of them, especially complex multi .MSI chain distribution. Hopefully, in that case, the focus will be on modernizing the app landscape so customers can make the full move to modern workplace management. Again, I’m aware that changing applications isn’t easy. My personal opinion if the switch to Intune is challenging; move as many users from the legacy way to the modern way and stick to SCCM for the devices which need it. However, keep on modernizing your apps! Read more about legacy apps and modernizing management here.

I believe Intune, on the device management side of things, has more than enough to offer today. Recently I was browsing in Intune to see which settings I could configure for Windows 10 and IOS devices. I realized that I only would set a couple of them: a password, Windows Update, enable Windows Defender and probably a Wi-Fi profile.

Besides the fact it is a lot of work to lock down devices (remember creating Windows images, turning off many features, use specific user settings solutions to disable even more settings, slower machines and unhappy users), with just a couple of very reasonable settings (and I truly hope everybody has configured those- on corporate and personal devices), I have the feeling it will be easier to make BYOD users enroll their  personal devices into a corporate management solution, because your Exchange policy might require an enrollment. With that, you have some control over the device (you can wipe corporate data) and the user can use its know Office apps.

Hopefully you have a better picture of what EM+S has to offer. To me, it offers Layers of Control, which are additional, on top of each other and not one or the other. Time has changed and purely focusing and protecting the device isn’t the way forward anymore. Identities are leaving your perimeter as is data. When you support that, enable that in a user friendly and secure matter, users will be empowered and be productive.

 

 

 

Modern workplace management with Enterprise Mobility + Security- part 2

In this series of 3 posts I discuss what I see as the modern way of workplace management. In the first post I defined the workplace. Now I would like to start with identity and also add the Enterprise Mobility + Security products of Microsoft in the mix.

Identity:

Since network boundaries are disappearing, identity is the most important part of today’s workplace management. In the past, the Local Area Network was the perimeter to secure. Firewalls, the local network boundary, that was the place to secure. With the adoption of cloud services and also content sharing externally, the original perimeter is being extended to the outside world. The LAN perimeter is fading. What’s there to secure is the identity.

First of all, how do you make it easy for users to access cloud services, preferably with Single Sign On, so using the on-premise’s credential? You extend Active Directory to the cloud and what is a better place to do that than to extend it to Azure. And again, yes I’m prejudiced but 1 of the big advantages is the fact that Microsoft collects a lot of information regarding logons (around 350 billion authentications), logon behaviour, suspicious logons, botnet networks, breaches at major public services (yes Linkedin is one of them, years ago). Microsoft is using that information to make their services better and thus making the services better which customers use. Check out Brad Anderson on Youtube talking about Microsoft Intelligent Security Graph.

With identity becoming very important, you would like to know who is accessing your services, and when it seems to be the right person, you would like to have some reassurance sometimes. Maybe a couple of steps further, you would like to risk assess a person and use that rating or profile to enforce specific policies.

The first Layer of Control is regarding identity. Some of the controls are:

  1. Multi Factor Authentication: an extra layer of security on top of a password. MFA is an Azure cloud service which is very easy to adopt. MFA can be turned on per user, so every time when that user wants to access services via Azure, that user will hit MFA. More granular, it also can be turned on per specific app. This is possible in combination with conditional access. When MFA is turned on, AD/AAD doesn’t accept your domain password anymore but expects a second factor. This can be a text with a code, a phone call where the user needs to push the # key or the use of the Microsoft Authenticator app on a device. It does work with cloud services but also with your on premises environment and even with 3rd party hardware tokens. More details can be found here. Just turning on Azure MFA provides a higher level of identity protection. Be aware that in order to be able to use MFA, you need to enable “Modern Authentication” in your Azure environment on Exchange and Skype for Business. Also be aware that not all clients understand Modern Authentication/MFA, like Apple Mail, Thunderbird and older Office apps. More details on modern authentication and Microsoft clients can be found here,
  2. Azure AD Identity Protection: to put it (too) simply, Azure Active Directory Identity Protection is a cloud based layer of control which helps you detect potential identity vulnerabilities and can define automated actions for those. More details can be found here. On an Azure level, Microsoft can see which identities are trying to log on, from which IP address, location and for example compare that to the last logon (remember the Intelligent Security Graph). Based on many variables a user risk level/profile or sign-in level/profile can be calculated. As a result, for example, a user logging on in the morning in Los Angeles and 3 hours later from an IP address in Madrid can be calculated as a high risk and the last login could be blocked or the user could hit MFA. In this case a very important tool comes around to put an extra layer of control on securing the identity:
  3. Conditional Access: with CA, it is possible to setup policies with several conditions with controls. You can combine the layers of control (identity, trusted/untrusted IP’s, device compliance, MFA and user risk) to grant or block access to cloud services.                                                                                                               Conditional Access is defined as: “When this happens, then do this”. The first part is the Condition Statement and the second part the Controls . An example of a statement: “All users, accessing Exchange Online, from all platforms, using browser and desktop apps, are granted on compliant (Intune managed) devices and when they use MFA. Another example is: “all users, accessing Sharepoint Online, from Windows devices, from all networks except trusted IP’s, using both browser, mobile and desktop apps, are granted when using MFA. Combing the layers of control is very powerful where you can setup a great balance between user friendliness and security.

Client apps/cloud services:

The second Layer of Controls are controls for client apps and cloud services. The first control you have here is the pre-built App Based Conditional Access policy for Exchange Online and Sharepoint Online. With these controls you can force users to use specific Intune manageable apps like the Outlook app to access your Exchange environment. Yes, this is tied to the mobile Android and IOS apps. Again, you can force users to use Outlook by enabling MFA, since Outlook knows about Modern Authentication/MFA. And why would you like to do this, you ask. Very good question but read on about another great feature and I will wrap up an give you my thoughts.

Another great tool to secure your apps and cloud services is Mobile Application Management, provided by Intune on the Microsoft Office apps- desktop and mobile versions. This is a very cool feature and pretty unique. Users can keep on using their well known Office apps like Word, Excel and Powerpoint and you as the organization are able to secure these apps and data inside them. Read here for more details on the MAM features within the Office apps on Android and IOS. Also know that these MAM policies can be configured for the desktop Office apps as well. Windows 10 creators Update (1703) and Office 2016, app versions 1705 and above. Essentially, with MAM you can protect your Office apps on Windows, Android and IOS. An example of what you can do with MAM is that you can deny copy data in Word and paste it in a personal app on your device.  Or, that a PIN is required when opening the apps. This way you prevent data leakage.

Why do I think the client apps/cloud services Layer of Control is such a big deal? Well, Exchange/email is a good example. Within many organization, users are handed a corporate laptop/desktop. That device has a very locked down image, where a lot of settings/features are disabled, I cannot install anything and in a lot of cases the user experience is poor. Within those same companies, you can take any (mobile) device, any browser and any email client and connect to the company’s Exchange environment and download the inbox/create an .OST or use OWA. User experience wise, great! Security wise, maybe not so great!. Data and information we send via email, many times, is very sensitive and I’m sure you don’t want it to be cached on a device with no Layer of Control.

This case of Exchange also is keeping me busy: how would I let my users connect to my Exchange environment (assuming I would have a company and employees). Well for sure I would like to have some sort of control. At least I would like to enforce the Outlook app, and set a PIN on it (maybe even a PIN regardless if there is a device PIN in place). I would disable copy/past from the Outlook app to other, not managed apps, like the device’s notes app. And also, maybe I would add conditional access to the mix to enforce MFA when there is a high risk user profile or the user is at home. Maybe, nowadays, I must consider email as that sensitive that I require an enrollment of the device in Intune. Maybe I would like to have the “corporate data wipe” control in case something bad happens. Of course, I still would like to have the MAM policies in place.

I’m aware this won’t fully protect me against intentional data leakage or fraud. I doubt it if there is a set of tools protecting you against it. Think about the simple camera in your phone. However, the identity layer of control and client apps/cloud services layer of control is a very good start and most likely more than what a lot of customers currently have.

Next, Modern workplace management with Enterprise Mobility + Security- part 3

Modern workplace management with Enterprise Mobility + Security- part 1

How to do (modern) workplace management is a continuous question which keeps me busy. It is a great topic to think about and to try to figure out how you can make workplace management easier and give the user a better experience.

New technologies arrive, old ones disappear, new insights, new use cases, new devices, new cloud services etc. The “workplace” is evolving and it should, but that means you need to evolve with it to support the change. Trying to put the new world inside the old management framework, isn’t the right thing to do. Users will be unhappy because you can’t provide them with features they have at home. I’m fully aware that stepping out of the known management framework isn’t easy. It requires change of mindset and that’s always uncomfortable. So, let’s be open minded together and see if new possibilities can work in your organization. This post, for sure, isn’t meant to tell you this is the only right way of doing things. I’m prejudiced, of course, because I do work for Microsoft, but I also like this topic.

One thing I have learned though, is that there isn’t a 1 size fits all solution. I wish, but the fact is, in a lot of organizations, there are some (small groups) which require something special. However, don’t let those specials be leading in the decisions you make around workplace management. Treat them as an exception.

So, let’s define a workplace because you can make that definition a lot bigger when you include the actual office space for example, or the area at home where you work. That I won’t touch, although, it is a very part of the workplace. In my definition, the workplace consists of:

  1. Identity,
  2. Client apps and cloud services,
  3. Content/data,
  4. Devices,

The order above isn’t randomly chosen by me. In my opinion identity is the most important part of the workplace today followed by client apps/cloud services and data. To me, numbers 2 and 3 are equal. The devices however don’t have the same importance to me anymore what it used to have in terms of management. To manage and secure modern workplace, you need layers of control. With layers, think about Azure Active Directory, conditional access, Identity Protection, Mobile Application Management, Mobile Device Management, rights management and access management on data, data labeling and classification etc. I know I’m prejudiced but I believe Microsoft Enterprise Mobility + Security platform is the integrated platform to realize this modern management by providing you the layers of controls for management, security and also gives a great end user experience.

Next, Modern workplace management with Enterprise Mobility + Security- part 2

Don’t let legacy apps block you from Windows 10 modern management.

Windows device management is changing enormously and possibilities are huge. One of the reasons is because Windows 10 is completely different than its predecessors, and is considered to be more of a mobile Operating System. Also, the broader devices environment is changing as we all know. You most likely have seen the “old vs new management style” of Windows devices in organizations. The old school consists of:

  • Corporate owned devices, most of them Windows desktops, Active Directory joined, Group Policies, SCCM managed, on-premises, locked down, business only purpose,

The new school consists of:

  • A mix of corporate and personal devices (Choose your Own/Bring Your Own), a mix of Windows/IOS/Android devices, Azure AD joined (where possible or necessary), managed via an Enterprise Mobility Management solution, on- and off-premises, more open/light way management, mix of business and personal use.

EMM vendors see a huge opportunity for their products to play a big part in Windows management within organizations, and they are right in doing so in my opinion. With EMM you can check all the boxes of the new way of management: 1 platform for managing different flavours of devices, corporate and personal owned, light way management, most times offered as a SaaS service etc. Bottom line, less device management, more app and data management for different kind of devices.

So, what’s keeping you from going to the bright side, the new school, the modern way of management? Many customers are using or investigating EMM products for the traditional mobile device- and application management, many customers are looking at content/data security but some customers are hesitant to use EMM for the Windows desktop/laptop devices, even though the world is changing, as mentioned before. Maybe they would like to use it but apparently there is a blocker (besides that change always is scary : ) That blocker, in my opinion is : legacy Windows apps.

Legacy Windows app can be difficult to manage. Most times they are 32-bit also or even worse, 16 bits, you deal with manual patches, difficult configs, multiple MSI’s etc. Tools like SCCM can be used to deploy those apps, just fine. Another way, maybe even additionally to SCCM, to optimize the desktop and/or app management, customers have been moving/looking at Server Based Computing and VDI. With those platforms you make management better, easier and maybe more efficient for some use cases. However, you don’t deal with the real problem: the apps themselves.

EMM tools are for light way/light touch device and app management. They cannot do all the fancy things SCCM can (MSI chaining, prioritizing order of install, pre- and post scripts), and they shouldn’t. The new way of management is just different. Take a good look at your legacy apps. There are may options nowadays: app vendors also have SaaS services, or a hybrid solution like Office365, or, change your apps/vendors and go for a competitor. I’m aware it isn’t easy but I remember a customer who mentioned an app, used by 5 users, 16-bit, no new versions, hard to manage and keeping them from upgrading their standard OS. An incredibly expensive app. Rip off that band aid, go through the first pain and in the end, life will be better. Seek the solution where the problem is. Maybe switching to a modern approach is a great moment to evaluate your app landscape. I am a firm believer in the modern management way with physical mobile devices managed by EMM. I believe that way will save a lot of management time and cost (imaging-apps-user setting solutions) and will increase user experience. SBC and VDI are great solutions to specific use cases but can be slowing you down in modernizing your apps and in worst case, keeping you from moving to Windows 10 and modern management.

Azure Information Protection- part 4: the AIP Viewer-client

In part 3, I discussed the end user side of Azure Information Protection: How can users classify and label document by using the Microsoft Office apps. To get the ribbon inside the office apps, as mentioned before, you need to install the AIP client on your Windows device. Besides the ribbon, the client also is a full client app to label content and share it with externals. It also is a viewer for other (than Office) supported formats, like a protected .pdf file (which will be a .ppdf file). You can check here which file formats are supported with the AIP client-viewer, for protection and classification.

So, what is the flow of sharing a classified and protected document with an external (or internals who weren’t part of the users in the RMS template)? Remember, a classified and protected (with RMS) document can only be shared with internal users, within your organisation, out of the box- set in the RMS template. Sometimes you want to share a document with someone outside your org. The AIP Viewer/client has shell integration, so the only thing you need to do is to right-click on your document and clic
k on “Classify and protect”.

 

The AIP Viewer/client will open you you will see the same labels as in the ribbons of your Office apps. Here you can change the classification of a document (when setting a lower classification, optionally with a justification) and you can check “Protect with custom permissions” . Then it will be possible to select permissions: like Viewer- View Only, Reviewer- View/Edit, Co-Author and Co-Owner. You set these permissions for groups of user, which you can add manually. Optionally, you can set an expiration date. After applying the settings, you can send the document to new internal users and external users, you have added.

From that moment on, you will be able to track the document. At the top of the Viewer, you see “Track and Revoke”. When you click on that button, your browser will open and you will see an overview of your document: when was it shared with others, the list of users it was shared with, who viewed, denied access, expiration date etc. There also is a timeline of activities and a map with geo locations of your viewers. At the button, in black, you see the Revoke Access button. This way, you can monitor the usage of your document and take action when needed.

 

 

There are no ribbons in, for example Adobe Reader. However, you can still label and protect .pdf files if you want. Again, the AIP Viewer/client supports several file formats. Just right-click on a .pdf file and click on “Classify and protect”.  You can now label your .pdf file or label + protect it. Meta data and optionally protection is being added to the file. With pdf files, you can see the AIP logo being added in the icon, as shown in the picture.

With the Azure Information Protection Viewer/client, users can now easily share content with others, but in a very controlled way. They intentionally need to take steps to do so. Even if a person you have shared a document with shouldn’t be allowed to view that document anymore, the user can quickly revoke access to the document.

 

Azure Information Protection- part 3: the end user with the Office apps

I have written a couple of posts around Azure Information Protection- what the solution is and the admin side of the solution. In this post, I would like to discuss the end user side of Azure Information Protection. What do end users see and how can they use classification, labeling and share documents? Luckily, it is very simple from an end user perspective, and that is a great thing!

I have mentioned it before; AIP starts with the creation of a document. When a user is creating a document, either a default classification/label has been applied by AIP (based on a company’s policy) or a user classifies/labels the document (also based on the company’s policy around document classification). From that moment on, optionally encryption applies with access control, a user policy and tracking+revocation possibilities.

 

After installing the AIP plug in on a user’s Windows system ( which you can download for free from here), when a user opens Word, Powerpoint, Outlook of Excel, the user will see a new ribbon in the Office app’s interface with the labels. If the automatic default label policy is applied, one of the labels will be grey, thus applied. On the left in the ribbon, you also can see which label is applied.

Which label to chose from all depends on the classification/labeling policy of documents within an organization. Needless to say you need to train/educate your users about the labels and what they stand for. Within the user interface, when a user hoovers over the labels, a textbox pops up with a description of that specific label. Companies can put in their description of liking. Also an open door but don’t use too many labels and add a clear description so users will understand easily which label to pick with different kind of content.

I discussed automatic classification and recommended classification in the post on the admin side of AIP. So, what’s the flow there and how does it look from an end user? Let’s say all documents with the word “draft” need to be classified internal or confidential. A user created a Word document, is typing away and somewhere is the word “draft”. Now the user wants to save the file on its machine (and it doesn’t matter where the user wants to save it). After picking the location and hitting save, the user will be prompted to change the classification of the document, with a reason (wording is up to the company’s policy). The user can change the classification of the document or dismiss the recommendation. Remember, AIP isn’t to prevent intentional behavior or fraud. In this case, the user will be made aware of the situation and can decide, after thinking about it, to change the classification or not. Also, you have the option to enforce the policy automatically, so users don’t have a recommendation. After changing the classification, the user will see the marking, set my the companies policy in the back end of AIP.

In the above case, meta data has been added to the document. When you right-click the document and open the properties, you will see and extra tab called “custom” where you can see the meta data. Besides meta data, the document, in this case, also has RMS attached to it. A users most likely doesn’t know about this and in my opinion, shouldn’t know this. The user classifies the document and based on the classification, the document gets encrypted, has specific access control and user policies attached.

Because of the specific classification/label and the attached RMS template, the user cannot just send the document to people outside the organization (RMS templates apply to users/groups inside the organization/(Azure) Active Directory/Azure tenant. If, by accident, a user would send the document to someone outside the organization (or maybe a user inside the organisation who wasn’t in the RMS template user/groups list), that recipient of the document couldn’t authenticate to open the document. With Echange Online and the Data Loss Prevention tools, you even can set rules on the AIP classifications/labels. Exchange Online and AIP work together.

AIP is easy to use for end users. Success depends on a clear, easy to understand company policy around classifying and labeling content and education of the users. Awareness how to handle content is one of the major benefits when using AIP. It is fair to say it can prevent user mistakes till a certain level but it won’t help you when someone intentionally is trying to get around the system.

My next post will be about the AIP client and sharing documents externally.

Azure Information Protection- part 2: Admin portal

In this blog, I would like to show and explain to you the back end side/admin side of Azure Information Protection. What does it look like, what can you configure, which options do you have. As I mentioned before in part 1, setting up/configuring and using Azure Information Protection is quite easy. Defining the corporate data policy will require some thinking.

Azure Information Protection (AIP) can be found in the Azure Portal and can be added to your dashboard. From there it is very easy to jump to AIP and start configuring.

First item you will see is the policy. In my screenshot you see a policy called “Global” and applies to all users in my tenant. I can add multiple policies and apply those to different groups within my tenant/organisation. So, different groups can have different classifications and labels. In my opinion, keep things simple.

So, everything I will talk about after this, all settings apply to my policy “Global”.

The next part in the AIP portal are the labels. Default labels are defined but you can radjust them- different names, colors and descriptions but also add more labels and sub labels. These labels are what users will see as a ribbon in the Windows Office apps- Excel, Outlook, Powerpoint and Word (I will deiscuss the end user part in another post). Basically, these labels represent your content policy. You translate that policy in labels.

Below the label section, you find some more settings; the title end users see in the ribbon and the tooltip. Also, if all documents and emails must have a label; in other words, is it required for users to classify documents and email or not. A pretty good setting if you want to enforce classification. Another great setting to start using classifying content is the setting to have a default label applied for documents and emails. This means that e new email or a new document automatically will have a classification- in my case; “General”. Users will be able to change the label. You can configure that in the case of a lower label/remove label by a user, a justification needs to be entered by that user. This is being logged in Azure so you can trace all this. Removing a label can be done, but a user always will do this on purpose/with a reason and never by accident.

As I mentioned before, you can name the labels as you want. The description part is pretty important. This description is shown to end users when they hoover over the labels in the Office apps. Good descriptions will help users use the right labels and thus protect the right documents and emails.

Optionally you can attach a Microsoft Right Management Service template to a label. You have to configure this template in the RMS portal . I will discuss the options in RMS in a different post but to summarize it; with an RMS template you can define with which users/groups  the document with that specific label can be shared and what these users/groups can do with that document/email, among other settings.

You also can configure visual settings with your labels like:

  • header/footer text,
  • color,
  • font,
  • watermark,
  • alignment.

 

 

One of the best settings are saved for last: automatic labeling/recommendations. Within AIP, you can define 1 or multiple conditions within a label. When a document/email matches that condition you can either automatically apply that label to the document/email or visually show the user a recommendation with a reason.

In my example, a user will see a recommendation to classify/label the document/email as Confidential- Internal Recipients, when a document contains the word “draft”. You can define custom conditions, like phrases. You can set it to exactly matching or match as expression. There also are built in conditions like IBAN and Swift. In this case, you can automate/enforce classification based on what you believe is important, and you can take human error out of it.

Hopefully this post gives you a general understanding of what you can do on the admin side with AIP.

 

Azure Information Protection- part 1: Document+email protection overview

In one of my earlier post, I wrote about VDI and if the concept is dead. One of my points was that VDI was/is used for content security reasons. Place all your desktops virtually in a central data center, and automatically, the assumption is that content will be protected as well. I have heard this use case many times but I believe there is a better approach to deal with content protection: truly protect your content; your documents and emails. Besides true protection, make your users aware what kind of content they are dealing with. Make them think twice before they send content to others, for example.

Azure Information Protection is a cloud-based solution that helps you to classify, label
and protect documents and emails. This can be done automatically (rules set by administrators), manually (by users) or both- where users are given recommendations. Optionally you can monitor and respond which means you can track & trace content and revoke access.

By using labels you add classifications to files and emails. This is done by adding metadata in clear text to files and email headers.

So, there are 3 components to Azure Information Protection:

  1. Classification/labeling: as an organisation you must think about your content- documents/emails first. There needs to be a organisation wide policy on how to classify/label content. Call it sensitivity levels, like: Personal, General, Confidential etc. You need to describe which content will get what classification/label. This policy will be implemented in Azure Information Protection. I sometimes call this the awareness phase: as an organisation, you need to think documents/emails, get aware of the sensitivity and translate that to labels. As a user, because of the policy, you will become aware of the guidelines set by the organisation how to handle specific content, and become more aware of its sensitivity. Besides coming up with classifications/labels, as an organisation you also need to think about the results/consequences within a classification/label. Is there a result within a label? Does a label require protection? That’s component 2,
  2. Protection: if you decide/agree as an organisation that a specific classification/label needs protection, you will need to define what kind of protection; encryption, access control, expiration data etc. That’s a second policy you need to think about. Do realize that not all classifications/labels will get protection in most cases, as far as I see it. So, as an example: documents with a label “General” aren’t protected and can be send to everyone, opened by everyone. etc. Documents labeled as “Confidential” might have a protection policy- only shared internally, only viewed and not edited, etc. When there is a protection policy in place, attached to a classification/label, users can track&trace the document and optionally revoke access to it. Component 3,
  3. Monitor and Respond: when a document is classified/labeled and protected, a user can monitor the usage of that document when he/she shares it. Via the Azure Information Protection client, a user can monitor who has opened the document and from where. That user also can revoke access to that document.

The beauty of Azure Information Protection is that it can classify/label and protect data no matter where the documents are; file shares, OneDrive, Sharepoint etc. It is very intuitive and easy to use for users through buttons. I will cover what Azure Information Protection looks like from an admin perspective, from a user perspective and use cases in different, coming posts. Stay tuned. If you want to know more/read more, click here.