One of the Navigation Link to be made invisible for a User Group -Sharepoint - sharepoint

I have a link called Create Reimbursemtn in the Quick Launch Menu. I dont want this link visible to certain group of users.
I am using Sharepoint 2010. I don't have any audience settings in the Navigation settins. Am i missing something? Can this be done out of box or programmatically ? Please let me know how can I achieve this requirement. Its urgent.
Thanks.

You need to setup User Profile Service application for the Audience feature to be visible.

Related

How to Change Site Name in Suit Bar Navigation of Hub Site Sharepoint Online

Hope you guys are doing best, I need some help. Actually want to change site name in top navigation bar(Suit Bar) on SharePoint Hub Site. Can you please guide me how i can do this?
Screenshot is Attached below
Select Settings.
Select Hub site settings.
Make your edits and Save your changes.

Extend sharepoint peopleeditor control

I would like to customize wss peopleeditor control so it searches user profiles by job title or some other property than login name. Can anybody provide me with some hint or maybe tutorial for something like this?
Thanks in advance
Below link might be useful to you.
Customize MOSS People Picker (PeopleEditor) Control
Also if you would like to replace all current (those built into SharePoint pages) PeopleEditor controls with your custom ones, you may want to see Guest blog by NaT - SharePoint People Picker: Override Validation Logic

how to set different views for admin and user

Hi I am little new to SharePoint. Here is my question
How can we make different views for administrator VS logged in user. For instance I need to display the
quicklaunch only to admin and not for user. And user should not see site actions tab.
How can we set this. Please can anyone come up with solution or any blog that we can refer?
Thanks in advance.
This blog will help with code identifying whether a user is an admin (or even just owner) http://blogs.tamtam.nl/duarte/2008/12/09/Sharepoint+How+To+Verify+If+A+User+Is+Site+Administrator.aspx
You can then create a control that uses this condition to display or hide content. See my blog here for an example: http://jcapka.blogspot.com/2009/02/handy-hiding-panel.html
You can also use the built in SPSecurityTrimmedControl but it does not provide a means of explicitly checking if a user is an administrator.
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.webcontrols.spsecuritytrimmedcontrol.aspx

Disallow item addition in a List or Doc lib

How can I disallow adding item or document to a list or document library? Due to some other feature scenario I cannot break role inheritance and have custom permission set for the list. Today, we restrict the addition using event handler (Item adding) – but this leads to poor UX.
Is there a way to have Role inheritance for a list and still have a base permission mask? Something like, allow everything that parent web offers but not X,Y,Z. Breaking role inheritance in the traditional way introduces the problem of explicit User and role management. Having a SPGoup hold an another SPGoup could help here, but that too is not possible. Let me know your suggestions.
I think you are asking to allow a user to have add permissions to the list but not actually be allowed to add to the list. Event receiver is going to be the best way. The only other solution I can think of is to use a custom item form that will do the check.
You can solve your problem by creating a webpart with the below functionality.
Identify the logged user is in admin group. If he is not in that group ganarte a javascript alert that "you have no permission for add new item" and redirect to (location.href="") allitems.aspx page.
And place this webpart in Newform.aspx page.
(add &toolpaneview=2&sharedview=true in in Newform.aspx url for editing page)
Hope this helps. Let me know if you need more help.
Create an IHTTPModule and subclass the context AuthenticateRequest event.
In the AuthenticateRequest routine you can inspect what type of action is happening and then redirect the user to the SharePoint "Access Denied" page. This is exactly how SharePoint does this functionality so the UX experiance would be the same.
If you want my opinion I would go with the way SharePoint handles permissions out of the box and break role inheritiance. Sure it will add new complexities to your life. But, I think you can better manage these complexities with the SharePoint Admin Toolkit and some custom built utilities for managing permissions. I think that is a better solution than what you are trying to do.
Am I missing something here when I suggest: Just hide the toolbar (or specific button) in the view page? That's an painless CSS hook done in the view page or SharePoint Designer
If you are using a custom List Template, you could create a custom View Toolbar Template. However, you probably will not want to use this on an OOTB List Template and it doesn't look like this will work on an existing list.
Even if you implement this, I would still leave the Event Receiver in place in order to prevent URL spoofing.

Way to make SharePoint custom quick launch links subject to same visibility/permissions as list links

When I create a new link in quick launch bar in any site, the link is static and is always visible even when a user may not have privileges to view that document, or the document library it is in. When any document library has a link in the quick launch (via the document library's "Title, Description, and Navigation" setting), the quick launch link is subject to permissions and will not display in the quick launch if the user does not have permissions to see that document library.
Is there a way to achieve that same functionality to have my static URL to a document be subject to the same 'visible if user has permissions to view that document' action? Possibly some way to add a link on the SharePoint quick launch for a document much the same way I can add a quick launch link with a document library?
You should use audiences to achieve that. Audiences allow you to target groups of users with specific content. This feature is only available with Microsoft Office SharePoint 2007, it does not exist on Windows SharePoint Services.
You should stick to audiences if possible, but you could also solve the problem by:
creating a custom quick launch as a server side control
creating a JQuery script to check permissions and update quick launch (not recommended)

Resources