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
Related
I am new to using Liferay, and practicing currently on Liferay DXP. I have created various user, and wanted to add different content to dashboard of any user. Such as asset publisher which will list all the assets published by that user. I am able to add this modified content only for Admin User. I am not able to find any setting where I can change the look and feel of dashboard for every user.
Can anyone please help me where I can find it? It might be pretty simple but I am unable to find it.
Thank you in advance for helping me.
You can look at the ADT. Modify the templates as per requirement and on user roles. You won't be able to deliver content as per individual user but to roles. You can also have portlet preferences to show different content on different criteria. This all is possible. You will have to study the subject more. It will be very difficult to detail out the whole stuff here. But yes with ADT in Liferay 7 / DXP you have a lot of flexibility.
I'm using liferay-portal-6.2-ce-ga5 in which some functionality like assigning a site to a new user or giving to use social office etc. So we can see here admin is assigning a site so what I want that it should be done automatically or any code so that it can be achieved?
If you're doing it to everybody (e.g. every new user should be member of a specific site or have the same role, like "Social Office User"): Go to "ControlPanel / Configuration / Portal Settings / Users / Default User Associations" and configure as you like.
If this is not what you're asking for, please rephrase your question to be more specific.
For programmatically achieving this, you'll find a bunch of sample code in James Falkner's blog article on the ancient sevencogs code.
I have a specific requirement where-in I want only the uploader of the document and a specific team to be able to view it in list / library. 1) is it possible? 2) If yes, how...?
Ok. So I was able to resolve my issue with the steps mentioned below. Soon will be documenting it in form of a blog and share it:
Created the document library and modified the default view to only show documents that were created by/modified by [Me].
Added a new web page to the library and gave exclusive rights to access that to a certain set of users.
Restricted all users from creating a view with the help of creating special permission level where user only had access to upload or delete a document but not creating/updating/deleting lists/views. Also disabled private view creation.
Hope this may be helpful to others too who are looking for restricted views / disabling view creation.
You need to set item level permission through event handler:
http://www.chakkaradeep.com/post/SharePoint-ndash3b-Setting-Item-level-permission.aspx
http://msdnvietnam.net/blogs/quang/archive/2009/07/02/sharepoint-eventhandler-set-item-level-permission.aspx
#Ashish, in SharePoint 2007 GUI you cannot make a query that will show documents that belongs to a specific group, however CAML specification supports it (Membership tag), it wasn't documented until SP2010, but it works on SP2007 (i'm using it)
However this involves custom coding and this doesn't assign permissions automatically, it just enables you to filter documents by groups.
For a solution without custom coding you could consider making a seperate folder/list for every person/group and set permissions to folder/list accordingly. This will also help performance - it's better to have permissions set on high-level container than having fine grained permissions (i'm just assuming that, because i read everywhere that mass fine-grained permissions are bad for performance)
You may use current user filter web part to filter the document by whom logged in into the sharepoint site by passing the value Dispaly Name
I am currently working on a custom SharePoint web part (WSS 3.0, not MOSS) that will pull in information for all of the users in Active Directory to build an up to date employee directory. This web part shows things like phone number, address, and other similar fields. The issue that I am having is that, by default, the SharePoint web site on IIS is running as the user IUSR_. This user does not have access to Active Directory, so I am unable to retrieve any user information.
To get around this for testing I have hard coded the credentials for a test user which I added just for this purpose. This, obviously, is not ideal. If anyone removes this user or if they ever change the password then the web part will break and they will have no way to fix it (they have no in-house developers to take it over once I am finished here). To fix this problem, I would like to make the Username/Password custom properties on the web part so I can pass those to Active Directory to retrieve the information I need. The issue I am having with this is that the password is stored in plain text so anyone can read it. I would like it to display as ******** or something similar. Is there a way to make a custom property on a web part a password type?
If this isn't possible, can anyone recommend another way to accomplish what I am trying to do? At this time I cannot change the user that the SharePoint website runs as. Although, if I cannot find any other solutions I will try again to persuade them.
Thanks in advance!
We use a service account for that. That service account is solely used for that. Something like DOMAIN\SPS_AD_READ_CUSTOMER
In our documentation that we deliver when putting the application in production that account is put in the list of stuff that is needed to make the webpart run. If the webpart ever fails, the ITPro can go to the chapter and check if everything is still ok.
It's not ideal, but I don't really know another way on how to fix it.
I would go with custom Editor Part, then set up a control of TextBox with property TextBoxMode set to Password, then override methods from type EditorPart - SynchChanges() and ApplyChanges() to set and retrieve values.
tip: override method CreateEditorParts of a WebPart type to start with.
I have modified my MOSS 2007 configuration to query a given target AD successfully. I would like to show some custom LDAP fields (such as country) in the PeopleEditor control and allow users to search against these fields. Can someone point me towards useful resources/tutorials showing how to do this?
Thanks, MagicAndi.
You need to inherit from the EntityEditor control (just as PeopleEditor does) and write your own queries and validation.
Some background (read community content):
EntityEditorWithPicker
PickerDialog
SimpleQueryControl
Along with these links and carefully studying the PeopleEditor control with Reflector, another good resource is this blog post from Igor Kozlov. There's a less detailed but still useful example on MSDN here.
I'm working on a CodePlex project that queries any given Active Directory from a people picker. It's well documented and combines techniques from the various references out on the web (giving credit of course). Hope it helps someone as well!
A first step should be to map the fields form the AD to a attribute in the SharePoint user profile. You can do this in the configuration of the Share Service Provider (Central Administration > Shared Services > User Profiles and Properties).
There you add a new attribute and define which AD field should be mapped to it. You can also define which fields the users are allowed to override (but only in SharePoint, it's only a one ways synchronization) and which one are read only.
This blog post shows how to configure the SharePoint search to be able to search users by a custom attribute in the user profile.
I hope this will point you into the right direction.