I don't want 100 different SharePoint sites. How to create private teams w/o a new site?
Guys. WTF. I've inherited a problem where a company of 50 people has 100 sharepoint sites - because users created different Teams for different projects, and Microsoft makes it incredibly opaque what this actually means. Now we have 100 SharePoint sites, many of which are unused, but all of which appear in the list of sites in 365AC. The structure we WANT is 1 Sharepoint site for our 1 org, but multiple locations within that site, and multiple groups for multiple projects. I THOUGHT what could work was converting the excess Teams into Private Channels. But I have now learned that private channels ALSO create SharePoint sites, because _______. Most confusingly, all of these sharepoint 'sites' DO exist within our main SharePoint website - they're just pages (but not 'pages') pretending to be a fresh sharepoint website. This confuses the **** out of people, the way they've redefined what a 'site' is, what a 'team' is, etc. This is genuinely hot garbage, and it's suddenly clear to me why people always push back on using SharePoint over OneDrive. Recommendations for... not having this disaster? Making a structure that is intuitive and doesn't redefine what a site and page are, and allows you to have private locations for management or projects, but DOESN'T create a 'site' within the main 'site', with it's OWN 'documents', and it's own 'Notebook' (which isn't a document) and it's own 'Conversations' (which are NOT conversations), and it's own 'pages'? I don't work with dumb people - these are very technical people. But even our main SharePoint guy is mystified by these interactions. Does it make more sense in another language? If anyone at Microsoft is reading - the english term 'site', comes from the word 'website', which generally refers to a distinct web service with a distinct domain name. These contained different webPAGES.. When websites started existing off a shared domain name, like company1.sharepoint.com and company2.sharepoint.com - this confused people, but they put up with it, because it was relatively easy to explain the tech behind this - having websites under a single site, that wasn't too hard to understand. But what SharePoint seems to do, is extend this practice into absolute hysteria, where a particular webPAGE of a webSITE is ALSO a site, but also is a TEAM, or COULD be a CHANNEL. OR it could be a PAGE - WHO knows? If it's a TEAM, that TEAM could have CONVERSATIONS, which aren't actually Team Conversations - they're EMAILS. But this is fine, because all CONVERSATIONS of a TEAM done in TEAMS are actually stored as EMAILS so really those, CONVERSATIONS should be CONVERSATIONS... So why aren't these conversations in Teams between a Team that are stored as Emails not showing in the Conversations which show emails within that Team? aefggaddadsfasd
SharePoint Template Gallery
Hey everyone, I'm running into an issue with the new SharePoint site page template gallery. Some of my templates are showing up consistently, while others appear intermittently — even though all the metadata is identical across them. I've been troubleshooting but can't pinpoint what's causing the inconsistency. For context: I have over 100 templates in the gallery. A template I just created is displaying fine, but one I made last week isn't showing up at all, so I don't think it's a template count issue. Any insights would be really appreciated!
SharePoint Template Creation - fail
we have our main intranet site - the default sharepoint url for our company and then we have various other sites, for collaboration, teams, projects etc. We can make templates for pages and news posts etc in all sites.... except our main site. anyone know a reason as to why? i raised a MS ticket, and they say it is because SharePoint modern sites cannot do this. However all our sites are modern, so why does it work on all, except our main intranet site?Collapsible section icon alignment no longer respected – recent SharePoint change?
Hi all, I’m looking to validate whether others are seeing a recent change to collapsible sections on modern SharePoint pages. Across multiple communication sites in our environment, the expand/collapse icon is no longer rendering inline with the section heading, despite the settings being configured correctly (e.g. alignment set to “Right”). Instead, the icon is now: appearing below the heading defaulting to the left-hand side ignoring the alignment setting in the section properties This change appears to have happened “overnight” and is consistent across all sites we’ve checked, not just a single page or site. Impact We rely heavily on collapsible sections for: knowledge guides FAQ-style content onboarding materials The current behaviour is: increasing vertical spacing unnecessarily reducing scan-ability of pages creating inconsistency between existing and newly rendered content It’s also causing confusion for content authors, as the settings no longer reflect what is displayed. Questions Is anyone else seeing the same behaviour across their tenant? Has this been confirmed as a design change vs a bug? Has anyone found a workaround or mitigation approach? I have already raised this and upvoted it on the Microsoft Feedback Portal and would encourage everyone to do the same if they are experiencing this issue. I'd rather not have to change the design across multiple SharePoint site - an enormous amount of work. Thanks!
How to hide the Modify this view and Create View as per users available in groups
Hi All, I have classic view of SharePoint in list/libraries. I have group(for Managers). I just want want to show and hide the Create View/Modify View/Modify this view depends on users available in group. If user available in group(for Managers) then they can do anything like Create View/Modify View/Modify this view but if user is not a part of the group(for Managers) then they can not modify any Public views but the can create Personal view. Is there any way how I can achieve this functionality?Updated design for collapsible sections SharePoint
We're seeing an updated design for collapsible sections in SharePoint as of today. The control arrow for the section now appears either over ("Left") or under ("Right") the header. Is this intentional? If it's not intentional - I presume that the arrow should appear either to the left or right of the header, not over or under and this may be fixed soon. If it's intentional - please change this so that we have the option that it is actually to the left or right of the header! The extra space that is showing right now ruins the look of the design, and it's confusing which arrow belongs to which header.Webpart "See All" ASPX link Not displaying List of News for Read-Only Users
We have an extremely simple Sharepoint site in M365 Sharepoint that we created a very simple News webpart, list form, 1 item, from news posted to this site only. The idea being people come and see the most recent news post, they click "See All" to view more if they desire. Visitors can see this link and go and view the article, along with any other news article posted to this site if they have the direct link, but only people with Edit or higher access are able to click the "See All" link and get a list of more news articles. People with regular Visitor/Read access see the title of the list but the page is otherwise empty like it's failing to return query results. We've chopped up the URL since it's aspx and have at least figured out the point of failure is in the : &serverRelativeUrl part of the link. If they chop off link before that variable, they can get an (albeit unformatted) list of the news articles. I am absolutely not a Sharepoint guru. We've inspected the permissions on the Site Library, we've reindexed the site, we've even experimented with different usergroups, nothing seems to change this behavior. Can anyone explain what's happening here and how to fix it or is this just busted behavior in Sharepoint Webpart command link?Bulk cleanup of content / documents in SharePoint
Hi, We currently have a few SharePoint sites that have old content / documents in document libraries. These are outdated and some are more than 5 years old. To delete these, we currently need to go to each document library / page (and its subfolders), sort by the date created / modified and then manually delete, which would take some time. Is there a way to bulk delete older content/ documents based on date, either within SharePoint admin or a third party program? (e.g. maybe run a query on a site to list any older content and then check off which page / document to delete). Jason
SharePoint News Email “Content too large” issue – size limit clarification
Hi, We are currently trying to send a SharePoint News post via email and encountering the following error: “The contents of this page are too big to send in email.” We performed testing to understand the limitation and observed the following: Full newsletter (~5.29 MB) → ❌ Error Pages 1–12 (~3.11 MB) → ❌ Error Pages 1–11 (~2.80 MB) → ✅ Works Slight increase (~2.90 MB) → ❌ Error again ✅ Based on testing: Practical threshold seems around ~2.7–2.8 MB Above this, email rendering fails ❓ Questions: Is there a documented maximum size limit for SharePoint News email content? Is the limit based on: Total content size after rendering? Image count/size? Can this limit be configured or increased? What are the recommended best practices for image-heavy newsletters? ✅ Current understanding: It appears that the limitation is due to HTML email rendering size rather than just file size Any clarification or official guidance would be appreciated. Thanks.
