 Barbara asks, all right. Barbara has a question. Audience targeting does not seem to work. We're working with SharePoint Online. I have enabled audience targeting for a specific library. Then I have filled in the audience field for one file with the name of a security group. The file is published. This is all done three weeks ago. Still my test user who's not part of the security group, still sees the file with the audience set to that specific security group. Can anyone help me with this? Any ideas what might be the problem? The first thing that flags me is it says security group, because security groups and SharePoint groups are two different things because SharePoint groups are Office 365 groups. Now, why that is, I don't know, because I don't do the technical side of that. But in my experience, when I've tried to turn on audience targeting and tried to use a group that I thought existed, it didn't work. Maybe Stacey, you might have some insight as to why that didn't work. Yeah. It depends on the type of site too. You're sitting here looking between a group site and a regular site, which is an unknown here. But when you're giving permissions, direct permission essentially to a file, like she's trying to say here, you don't actually have the ability at this point for audience targeting itself. She's adding a group to it. That group has to exist, but was that group created as a security group, or is it a different group and she's thinking it is? That is somewhat of an unknown. Audience targeting, you find more in navigation, web parts, etc. Not at the folder or document level, that's direct permissioning. I feel like there's a disconnect there a little bit with what she's trying to set because that bar, you're not going to find audience targeting. It doesn't change their permission, it just hides it from it like the web part. If you were to go to the full list, you're going to know that's a news web part. You go to the full list where it lives, you're going to see everything. It doesn't lock people out of seeing content, it just filters it in that web part. Yeah, exactly. Typically, most people aren't trained or have the access to even get to site contents. They don't view it if they don't have certain permissions on there. It goes to permissions and I think that she's combining the two, instead of looking at them as two separate entities. I think that's where her confusion is. Right now, she just needs to focus strictly on permissions itself and not worry so much about the audience targeting piece of that.