SharePoint Maven

Need a simple office or events calendar in SharePoint?

You can create one directly from the Calendar template:

1⃣ Open your SharePoint site and select New > List.
2⃣ Choose the Calendar template.
3⃣ Name your calendar and select Create.
4⃣ Add events from either the Calendar view or the Grid view.

SharePoint automatically adds Start and End date columns, and you can add more columns or color code the calendar to fit your needs.

Read the full article here:
https://sharepointmaven.com/how-to-create-a-calendar-using-sharepoint-lists/

SharePoint dashboards used to mean limited chart options or a separate Power BI setup.

Now, Copilot can create an interactive HTML dashboard from a SharePoint list or Excel file with a few specific prompts.

Create your list, add your data, tell Copilot what you want to see, and then refine the dashboard's colors, charts, filters, and layout.

The dashboard can even update as your data changes, provided you include that instruction in your prompt.

Read more: https://sharepointmaven.com/create-html-dashboards-in-sharepoint-with-copilot/

Creating a SharePoint page or news post can start with a simple prompt.

From your SharePoint site homepage, select New, choose Page with AI, and then decide whether you want to create a Page or a News Post. Describe what you want to create, add the tone and length you prefer, and let Copilot generate a starting point.

You can also use built in Copilot templates, which combine prompts with fill in the blank sections to help you create content such as a welcome post for a new employee.

The content is created as a private draft, so you can review and edit it before sharing it with your site members.

Learn how to create SharePoint Pages and News Posts with Copilot AI: https://sharepointmaven.com/how-to-create-sharepoint-pages-and-news-posts-with-copilot-ai/

There is more than one way to build an FAQ in SharePoint and Microsoft 365, and the right choice depends on where your content lives and how you want people to use it.

You can create an FAQ with:

🔷 Collapsible Sections in SharePoint
🔷 A Microsoft List with Question and Answer columns
🔷 Site Pages grouped by a Question column
🔷 The Q&A component in Loop
🔷 Collapsible Headings in Loop
🔷 The FAQ Web Part, which uses Copilot to generate content from selected files

See how each option works and choose the best fit for your organization: https://sharepointmaven.com/6-ways-to-create-faq-in-sharepoint-and-microsoft-365/

Loop pages are designed to make collaboration easy, but sometimes you don't want everyone with edit access making changes.

Microsoft Loop now gives you the ability to lock a page and make it read only, which can be helpful once the content is finalized or when you simply want to prevent accidental edits.

Here's how it works:

✔ Open the Loop page and click the three dots in the upper right corner.
✔ Turn on the "Lock page" toggle.
✔ Once the page is locked, users can no longer edit the text, change the styling, or rename the page.

There are a few things worth knowing.

Anyone with Edit permission to the workspace or the page can lock or unlock it. This isn't like checking out a document in SharePoint, where one person controls it. If you lock a Loop page, another editor can unlock it.

While a page is locked, users also can't view its Version History or delete the page.

So, think of this feature less as a security measure and more as a simple way to protect finished content from accidental changes while still keeping it available to the team.

I explain the feature and show exactly where to find it here: https://sharepointmaven.com/lock-and-unlock-pages-in-loop/

Company policies, forms, and templates have a bit of a unique challenge in SharePoint. Employees need easy access to the final versions, while only a select group should be able to edit and update them.

There are a few ways to structure this, and each comes with its own pros and cons:

📌 Use a single library with folders
📌 Use a single library with metadata
📌 Keep editable and final versions on separate sites

The third option is the approach I recommend most often. Policies can be drafted, reviewed, and updated within private department sites, while approved versions are copied to a Communication Site or Intranet where everyone can access them as read only documents.

This keeps works in progress separate from published policies, while departments can still manage their own review and approval processes.

I walk through all three options, including where each one works well and where you can run into problems: https://sharepointmaven.com/best-practices-for-organizing-company-policies-in-sharepoint/