Only owner should be able to edit or delete a List Item

Stef Heyenrath
  • Only owner should be able to edit or delete a List Item Stef Heyenrath


    1. User has 'Contribute' rights on a List.
    2. User creates a new ListItem on this List.
    3. User should only be able to edit or delete his own ListItems.

    How can I define that only the Owner (Created By) should be able to edit or delete this ListItem ?

    I was thinking about using an xslt if-statement with:

    • ddwrt:IfHasRights(...)
    • 'Created By' == 'Current User'

    Is this correct ? Or are there easier ways to do this ?

    See this page for a complete overview from all Rights.

  • It's very easy.

    alt text

    Note : the only issue is that you are still able to click or delete option in the dropdownlist, but when you do this, you get an 'Access Denied' error from SharePoint.

list permissions
Related questions and answers
  • ) Board description (editable) My questions: What tool is most appropriate for making the forms? Infopath? SPD? VS2010? How do I handle rights to make sure only the board can access the board edit form? What kind of workflow do I use? When do I start the workflow(s)? What do I use to develop the workflow(s)? How do I handle rights when showing the listview with all requests? How can I build... by the representative, the board can approve or reject the request. A mail gets sent to the user and the representative with the descision of the board. So the list has the following fields: Request

  • (Windows6.1-KB974405-x64.msu) Enabled all roles indicated in the list (IIS and WCF) Installed Sharepoint Foundation 2010 didn't run the product configuration wizard (yet) created two additional domain user accounts...I'd really like to prepare development environment for Sharepoint 2010. This is what I did: I installed Windows 7 x64 I installed VMWare Workstation Created a VM domain controller based on Windows... Powershell as domain administrator (so I have rights to access domain accounts) I didn't install SQL Server 2008 KB 970315 x64, because I'm running R2 version - as I understand this is SQL Server 2008 SP2

  • that user opening it may get it returned to them as read-only, often other users, even multiple other users, can click the button and the spreadsheet will open for them in edit mode! Questions: What.... Note that this is just opening the Excel file without checking it out. Problem: Once in a while, and for no reason I can figure out, a user will click the button and the spreadsheet will be returned to them by SharePoint as read-only (so they will get the above error message). However, often they are demonstrably the only user to have accessed the document - in fact, sometimes this will happen

  • . This means that I’ve prepared list of all sites/sub-sites in my scope. As a source I use spreadsheet with all details about sites/sub-sites input.xlsx this is only one part of process maintained...: URL to Members group (users with Read/Write access) URL to Visitors group (users with Read Only access) REGION Site/Sub-site URL Site Name Sub-site Name Site owner Ok that’s introduction, now how... and this two sub sites have different set of user. So to summarize my question. I want to get as result of SQL query table with username (NT\login) with information about

  • , and then as part of that activation, drop web parts onto some specific pages. In my case I want to be able to drop it onto the "AllItems.aspx" page of a list, but I'm equally having trouble adding... work either. I should be able to do it by more heavily customising the List Definition, but that seems a little over the top and I'm reluctant to do that before ruling out the other options. So, the only Neat way I can see through it is some sort of "Configuration" page, which then does it via the Web Services. But this is a pain, with the user having "Activate" the feature and then "Activate

  • have 11 pages of document links, each with its own subheadings. So far I have it set where each document has a custom field called "Page" with a check box list of all the document pages... to the documents list and note on which pages they should appear on without having to manually update the pages themselves. The problem that I am having is that I cannot seem to find a good way to sort the documents into their subheadings once they are on the appropriate page. I could create individual check boxes for each page/subheading combination, but this would create a list of approximately 50-75

  • installation and then installed it as Server Farm (then Complete) to avoid installing SQL Express. Created a separate SPF_CONFIG local user with Logon as a service right. Opened SPF Management Shell and run New-SPConfigurationDatabase so I am able to use a non-domain username (SPF_CONFIG that I created in the previous step) But all I get is this: Unknown error The outcome after this error is: Database Sharepoint2010Config is created User SPF_CONFIG is added to SQL Server and attached to this newly created database as dbowner (check below image) alt text http

  • the page. We do have hooks for setting default page layout based on where in the structure the page is created, here we can append the web part as well, but then the web part will only be added if you create...How can I set a web part so it will be automatically appended to a web part zone when a specific page layout is selected? The solutions I have tried so far is: Using <ZoneTemplate> under <WebPartZone> and putting my webpart in there Adding .webpart-code directly into <AllUsersWebPart> where I define the page layout, in elements.xml Put the web part on the page layouts

  • a subsite, or maybe it should be a separate site collection? I would guess that the 'behind-the-scenes' portal, only accessible by employees, with features such as dashboards/collaborative wiki, would...I am developing a company website/portal in SharePoint, and am trying to figure out the best way to organise it into site collections, sites and subsites -- I'm confused by the terminology I think... a support section for customers requiring a login Contact Us one web page with contact details The top-level sections in my hierarchy, i.e. Home, Company, Products, Support, Contact Us would share

Data information