Join Toni Saddler-French for an in-depth discussion in this video Create and work with site policies, part of Managing Records in SharePoint.
In addition to applying policies to libraries and to content types to determine how files are handled, you can apply policies to whole sites to have them closed and deleted on a certain schedule. This can be especially helpful if people in your organization tend to run projects, finish the project, but leave the site sitting around. If your team is working with project sites with team mailboxes, the team mailboxes can be closed with their project site. Let's create a site policy in our site collection.
Go to settings and click site settings. And then I'll click site policies. Let's create a policy. I'll call this, project closure and deletion. And the default is to have the site not close or delete itself automatically. I can choose to have it deleted automatically or have it closed and deleted. When a site is closed, it's basically a holding stage before deletion. The site is also not exposed in certain web parts or other places where it might be listed with other sites, like Outlook, or Outlook Web Access or Project Server.
Also like to close and delete sites automatically. So we'll have the closed event happen three years after creation. Most of our projects are usually about a year or two. Now again, when a site is closed, it's just,um, in a holding state before it's deleted. You can determine that a site is read only while it's closed, but that's not the default. I'll have the deletion event happen nine months after the site is closed. That will give plenty of time for people to deal with the site if they still need access to it. I can have an email notification sent to site owners three months in advance of deletion.
I can change this to days or years as well. I'll have a follow up notification sent every 14 days. Sometimes, if takes a few notifications, in case people are still working on projects or something comes up. I will enable owners to postpone iminent delaytion for a month, so that way, if something comes up and they still need to access, they can postpone the delaytion. I could choose to have the site collection read only when it's in the closed state, but I'll leave that unchecked. I'll click okay. Now the policy has been created for the site collection and now I'll show it how to apply it to a site. We'll go back to Inside KinetEco site. And go to site settings and click on site closure and deletion. If site closure was available manually, this option would be not dimmed. Right now site deletion is set to never and there is no site policy applied.
If I click on the drop down I can see the new project closure and deletion policy we created and I can apply it. I'll click okay. So, now the KinetECO site has the site collection policy applied to it. You can also apply the site policy through workflow and you can also have an administrator make it available. When people create their own sites through self-service site creation, the site policy can be a great way to manage the overload of sites in your organization.
- List three benefits of treating content as a record.
- Plan an effective records management strategy by gathering information from stakeholders.
- Organize a Records Center by creating content types.
- Define a multistage policy.
- Use site policies to manage large volumes of SharePoint sites.
- Explain troubleshooting solutions for common problems.