Forum Widgets
Latest Discussions
Users unable to determine who has access to document library due to security groups
Greetings, Maybe I went about this the wrong way. Looking for advice on either the proper way we should be moving forward on this or any other comments or insight we should be considering. This is for SharePoint online via Microsoft 365 Business license. Scenario: 1. SharePoint Document Library per department (Each Document Library exists in its own SharePoint site), essentially being used as a company drive. 2. Some users should only officially have access to specific folders in some of the document library. 3. If say a person in accounting has access to some specific folders, and either they are replaced or a new accounting user comes in.... should be able to reference the access the existing person has in order to give the same access to the new user. 4. Common Request: Give UserB the same folder access as UserA. 5. Some users should have access to the entire document libraries while other users only have access to specific subfolders. Current Implementation: 1. In Entra, created Security Groups that tied to specific folders. -- For Example for the accounting folder, only management has access to the entire folder but the accounting staff only have access to specific folders. So like there is a FiscalYear2024 folder, so I created a security group called sec-Accounting-FiscalYear2024 and assigned the members that should only have access to that folder and not the rest of the library. -- My thought behind this was if a new user was replacing the existing user or joining the department, I can just reference the existing user security group membership and copy it to the new user. 2. In the SharePoint document Library, I create a shareLink that is assigned to the security group I made for that access. Then I give that link to the users I assigned the membership to. Current Issue: 1. Aside from the official document sharing/access that is being done from the security groups above. There are occasions where users of a sharepoint need to share specific files or folders to other users. 2. However, they are all panicking and confused because aside from themselves they are unsure who has access to the existing folders/files in the document library. 3. When going to manage permissions of a file/folder, it only shows the group assigned to it but not the members of the group. 4. So since users can't see the members of the group assigned to a folder, they have no idea who has access to that folder and are getting confused. If this was an NTFS drive, it would be super easy for users to see who has access and etc by looking at the properties but I'm stuck behind some limitations of sharepoint I didn't realize existed until I tried to implement certain workflows. Any advice here would be greatly appreciated, as my implementation has turned into a point of frustration for end users. Thank you in advance!
Modern Lists Missing Ribbon to Add/Edit Items
Has anyone run into this with SharePoint? In the modern experience, I’m not seeing the ribbon/options to add or edit items at all, but when I switch to the classic experience, everything shows up as expected. I’ve checked permissions and basic settings, but nothing obvious stands out. Starting to wonder if this is a configuration issue, a feature setting I’m missing, or something specific to modern UI limitations. Has anyone dealt with this before? What ended up being the fix? Thanks. This is how my modern experience currently looks. When I switch over to the classic experience, I can see those options again.
I need some simple layman explanation
Hi, I am involved with an implementation of an epm system that is integrated into sharepoint M365 and I started reading on its manual on the setting it up for the first time. I know the steps but I wish to get some simple understanding of why the steps are needed since I am not a very technical person. The tool involves the deployment of an addin in Microsoft word (both web and desktop app). The manual said the addin app can be installed by the user directly from app store or being deployed by the M365 administrator to group of users...but in the section for M365 administrator to deploy this addin app, it said that permission needs to be granted to the app. The permissions are: openid profile sites.selected user.read So why is it ok to let user install directly (without any instruction to set permissions) but when M365 administrator do it, it suddenly needs the given permission? In addition, the manual said to run a powershell script in order to grant permission to the sharepoint site created for the epm system integration. it wrote that sharepoint admin must have Microsoft graph powershell SDK installed and run the script being signed in as site owner. What is this powershell script that it needs special installation to run? Then something mention that when deploying the addin to a group of users, there is a step to run a manifest script. This step might need to be re-execute if there is changes in the addin development. What is this Manifest meant for in Sharepoint? What does it do? Thank you in advance.
PnP Template Error: "Invalid field name {guid}
Hello, I'm trying to apply a site template from one SharePoint Online site to another using PnP PowerShell. I have custom lists, some of them with a specific dependency chain: List X has a lookup to List Y. List Y has a lookup to List Z. All libraries/lists have "Allow management of content types" enabled. The cmdlets I run: Export: Get-PnPSiteTemplate -Out template.pnp -Handlers All -IncludeAllClientSidePages -PersistBrandingFiles Import: Invoke-PnPSiteTemplate -Path template.pnp The Error: During the Invoke process, I get: Invoke-PnPSiteTemplate : Invalid field name {guid} targetsharepoint site What I’ve tried: I attempted to manually remove the ID="{guid}" attributes from the XML inside the .pnp package, but that just makes the template schema invalid. Verified that I am connected to the target site with owner permissions. How can this issue be fixed? Any help would be greatly appreciated! Thanks!Quick steps disappear from SharePoint list
I have 4 quick steps set up for my sharepoint list. Each one executes a flow. Twice now they have disappeared. I don't see them when I go to Automate or when I go to manage quick steps. Refreshing the page didn't help. The only way I could get them back was to add a new quick step, save it. Refresh the page and go back into manage quick steps and they were all there again.
Hero and Quick Links web parts not supporting library and folder links
In the last few days, I noticed the "picker" modal used by the Hero and Quick Links visually changed. I didn't think anything of it at first until I realized the Hero web part was no longer allowing me to select libraries or folders to serve as the link. This was using the "Site" blade, which appropriately shows all the libraries and lets me drill into each and see the contents, but the ability to select a library or folder doesn't work. To make matters much worse, the "From a link" blade doesn't work either. "From a link" now seems to have a new validation component, so when I attempt to paste in a library or folder URL (i.e. https://tenant.sharepoint.com/sites/HR/Benefits) it detects that it's a SharePoint resource and displays a folder for me to select before I'm allowed to commit it - problem is, I still can't select this. I've tried pointing to the .aspx page that correlates to a library/folder view - doesn't work. I tried creating a Link in the library/folder that points to itself - I can't select these either. The Quick Links web part, on the other hand, does allow me to select these - same exact UI but allows for selecting libraries and folders. This does work for folders, but does not work for libraries. It visually looks like it works for libraries, but when you save the change is not really committed. I'm genuinely surprised to not have found this issue reported elsewhere so far. I assume this has to be a bug and hope it's fixed soon - allowing your most popular web parts to link to the root of content in your own platform is one of the most basic feature requirements and for this to break and not be noticed is pretty alarming.
SharePoint List Rule to send email not allowing shared mailbox email address
Hi I have tried to search for an answer to this to no avail. We have a SharePoint list and want to create a rule that sends an email when a new list item is created. Sounds simple but I can't seem to add a SharedMailbox email address only UserMailbox email addresses. We do have a work around where we have created a rule in outlook instead that when the email arrives to the UserMailbox forward it to the correct SharedMailbox but it seems a bit silly that I can't directly add a SharedMailbox to the SharePoint list directly from the below. See below the screenshot of where I am trying to insert the SharedMailbox email address. It doesn't find it and if I add it in manually the create rule button doesn't activate. Am I missing something? Thank you!
