I've got the 'My Site' functionality basically disabled so users can't get to that stuff from the menu under their names. The problem is we have need for a company directory, and I used the Enterprise Search Center to create a staff directory and everything in the default results links to some page or another in the '/my' built in site collection. How can I disconnect the people search entirely from the 'My Site' system?
You can limit all the searches with a search scope to your site collection. That would trim out Personal from the results. Then set the scope on the search box or write a custom results page.
Related
I have created a simple (display only) SPFx webpart that makes calls into a list on the same site as it is used. Standard users have read access over this list, site owners have Full Control. When I add the part to a page, even site owners cannot see it. Site Members (& Owners) are able to see the page (published or not), but the content which should be displayed by the webpart is missing. Note that the basic html is visible, but the data which should be retrieved is not. If I elevate a site owner to a site admin permission level, the webpart then works as intended and data is retrieved correctly and displayed. Note also that other webparts on other pages served from the same library work correctly for all groups.
Does anyone have any suggestions to explain this behaviour?
I have tried: Rebuilding and publishing webparts, new test pages created by the same and other user accounts both published and unpublished. I've carefully changed permissions on the "Site pages" library, the "ClientSideAssets" library and the site scoped app library itself.
I've answered my own question here. The error was caused by a REST query into the SPO list that contained a taxonomy (managed metadata) field. Expanding this field appeared to require the highest permission levels, thus all non admin users were unable to retrieve the data.
I later found an excellent article detailing the subject here.
I was able to trace this by serving through gulp into the online workbench, copying that URL into an incognito window for a different user account, and utilising the (Chrome) debugging tools. This tidy solution might potentially be of use to someone.
Users at our organization need to create word documents from templates. In the document there should be their name, their phone number and email address. Unfortunately in MS Word "user information" only contains the users name, initials and mailing address. So I can't use "normal fields", I think.
Until now, we used a autoexec() word macro / vba script that read the user's information (phone, email, Name) from local AD/LDAP when opening the template and replaced some placeholders in the document template. The user then saved this document as a copy. This solution worked quite well when everyone was working on a domain joined windows computer within the company network. Now people work via word online, iPads, from outside the company network and so on..
Of course one could generate the document via web app or powershell and do a search / replace but that would break the users known workflow. They are already "a bit challenged" by all the changes that came through the switch from good old mapped network drives to sharepoint online etc.
Therefore I'd like to find a solution that looks and works similarly to what they're used to.
Maybe an office add-in that offers templates in a pane with data prefilled from graph api would be an option. Thanks #Tiny-wa for the suggestion.
I really appreciate any hints. Thanks a lot in advance!
If I have to use document and media portlet in liferay with following facility then how can I achieve that?
Now From Above picture I want that if organization A user have upload something then it should be viewable by only organization A Users.
right now anyone who have permission to view the document and media portlet cans see my uploaded files.
This level of control is, I think, usually handled by creating sites for your organizations. (There are probably other approaches, which I'd like to see discussed too).
For example, if you create a site for each organization, then there will automatically be a Document and Media library that is private to that site. The site doesn't need to have any pages or anything if you don't need that.
You create the site for the organization by going to "Users and Orgainizations", clicking through to the org of interest, and then working with the "Organization Site" in the control menu.
Once the site is created, then everything at the "site" level of the control panel can be selected for the new site. When so selected, the Documents and Media portlet will show you the top level folder for your organization.
Now you can use the normal permissions settings for sub-folders or even individual items to restrict availability to "site members", which will be, in this case, "organization members".
Well if kirkz answer doesn't solve your issue then I suggest you try the following:
1) For each organisation set up a Liferay "User Role". You'll find "Roles" in the "Portal" section of the Control Panel
2) Assign the relevant users to each of the Roles that you've created based on their Organisation
3) Then go into the Document Library and set the permissions as you need for each of the folders using the Roles you've created. So for example you could have a top level folder for each organisation. Then just set the permissions on the each of those folders so only one Role can access it.
This should solve your issue, however kirkz solution is actually the way you should achieve this hierarchy.
In SharePoint 2010, I created several new search scopes to different document library locations, but get no results returned no matter which one i use. I even created a search scope to search "all content", attached it to my search box web part, and still no results!
What would be a cause for this?
I notice that when i remove the &s=myscope, from the URL, the results then show, but as soon as I place &s=myscope back on it, i get no results. What should I be debugging or checking for?...
I've waited 15 minutes for the scope to krawl
Indexing Site Content for the sub site, is set to yes
The search box web part is connected to the correct search scope
group
This is driving me crazy...
Thanks for any help!
I even created a search scope to search "all content", attached it to my search box web part, and still no results!
It works when i set the scope to "all content" - just discovered that! But not when I try to set a web address to specific folder...
Knowing the difference between the behaviors, "Include" and "Require" helped. Also the web address to filter the scope too, is potentially sensitive? I included an "https" in the beginning of the URL, because the site I use, also uses "https". But then I tried it out with "http"...So as a final verdict, by using "Include" and "http://", my scope crawled all the items in my specific directory and I now get results!
I need to set up IP filtering in a SharePoint document library based on a group that a user is a member of. More specifically, we have groups set up for each of our customers. Each group should have an allowed IP address attached to it. When a user accesses this document library, we then need to ensure that the user is coming from the IP address attached to their customer group. The IP filtering would only apply to a single document library, not the entire site.
My only idea so far is to create a webpart that checks the user's IP address and redirects if it isn't correct. Then I could put that webpart at the top of a webpart page, and display the document library webpart below that. That's a little hokey, so I was hoping someone had a better idea.
The problem with your proposed solution of a webpart on the AllItems.aspx page is that there multiple ways to get to a document and this would not prevent someone with a direct URL from accessing the document.
You want to take advantage of SharePoint's permission structure. If the documents can be grouped by security, then you could create one library per customer (or one folder within a single library) and set the permissions based on your SharePoint groups for the library/folder. That may not work for you if you need to have one document that is available to multiple groups.
Another option is to set the library security to be restricted to only one system account. Then you could write a webpart (or application page) that checked the user's IP address and using RunWithElevatedPermissions you could get the contents of the libary that are applicable to that user. That would solve the issue of a direct link because they would have to go through your page to access the documents.