We have now covered almost all of the
settings in SharePoint Online, but there
are just a few more small ones which are
important, but simply not big enough for
them to have their own section. The things
that are left to configure are mostly on
and off switches from the admin center, so
let's take a look at them in detail. First
of all, to show or hide app tiles. By
default, the OneDrive and SharePoint app
tiles appear in the app launcher and on
the Office 365 portal. If your
subscription doesn't include one of those
services or you don't want users using one
of them, you can hide the app tile for it.
Hiding those services doesn't remove them
for users, and if users have saved the
addresses of the service, they will still
be able to access it. Next up, to enable
or disable Delve. Delve is powered by the
Office Graph and shows users the most
relevant content based on who they work
with and what they're working on. The
information in Delve is tailored to each
user, but Delve does not change
permissions, and users would only see what
they already have access to. The big scare
and why some companies want to turn it off
is that users might see documents they
have access to, but they didn't know
existed. Now let's talk about Information
Rights Management, or IRM. After enabling
IRM settings at the tenant level, site
owners can IRM-protect their SharePoint
list and document libraries. When people
download files in an IRM-enabled list or
library, the files are encrypted so that
only authorized people can view them.
Typical restrictions that you can put in
place include making a file read only,
disabling the copying of text, preventing
people from saving a local copy, and
preventing people from printing the file.
Next up, you can control whether site
collection administrators can use the
connect to a New Office 365 Group command
on the Settings menu to connect the
classic team site to new Office 365
Groups. Another option that we have is to
enable or disable comments on site pages.
You can enable or disable it at the tenant
level, but if you don't want to control it
at the tenant level, you can also do it at
the site level by using the Set-SPOSite
PowerShell cmdlet and the
CommentsOnSitePagesDisabled PowerShell parameter.