Hot answers tagged list
You can create/modify a view and apply the filter on the start date. To create/modify a view, go to list settings-> Scroll down to bottom and you will see a section named Views. Here you can click on exiting view or create a new view. In the view you can filter based on the start date in the Filter Section. UPDATE Based on your update in the question. This ...
its long winded but,, you need to add a filterd webpart to the list page: this is a step by step guide with images! https://www.nothingbutsharepoint.com/sites/eusp/pages/sharepoint-list-filtering-by-date-range.aspx
Set the Draft Item Security in the Announcement List in Child site to either "Any user who can read items " or "Only users who can edit items" while setting the versioning settings. This way users can see every announcement item in the child site. In the parent site set the logic for seeing Approved items only in a webpart like COntent Query Webpart. EDIT ...
If your're on SP2010 or above, a simple SharePoint Designer Workflow can be used to set the permissions when the file is uploaded/modified, based on the values. There's no secure mechanism to restrict access based on values alone (as in list views, client side coding, etc), you'll need to actually set the permissions specifically or place the documents in ...
You can create a document library, where you can upload your documents. In your custom list create a column by name 'Attachment' of type lookup.Provide the document library created then as the lookup list and title of document library as lookup field. Reference from here
Try going into the List Settings -> Advanced Settings and check the box to manage content types. You should then be able to click on the content type and have an option to hide selected columns and I think you can also reorder the columns. Changed made here will affect your Edit and Create views.
An audience just allows for promotion to those members, its not meant to be a security tool. For instance, you may put a web part on a page with an audience of Group1. So that when Group2 login in they don't see the WP but Group1 do. Think of it as a way to classfiy data and surface information to the correct user groups. Visibility of items is controlled ...
Only top voted, non community-wiki answers of a minimum length are eligible