I'm using F&L for displaying open job postings. I've got a filter setup so that closed postions aren't displayed but, I want Admins to be able to see closed positions so that they can open them to have them displayed. Is there any way to do this with the standard module?

---

David O'Leary
Efficion Consulting

>> (or even the same page perhaps?)

In answer to "my" question you cannot have two versions of the FnL on the same page, so you need to use separate pages.

Just to update you I actually used this as a solution for staging content today. Created a restricted field called "approved" and had one instance of the FnL on one page that was visible to all users and filter for ='True' and had another version on another page that was restricted to select users and filtered for "False". You could also have no filter on it and show both states.

 Don't be surprised.  If you reference the same FnL module on different pages it will always share the same underlying data and structure.  Some of the elements can be changed on an instance by instance basis, but most will update across all instances regardless of which instance you use to edit it.  For example, adding/deleting/modifying a field in one instance will affect all instances.  However filters are unique to a particular instance. Other display features are unique to an instance such as the XSL template.  I haven't tested all the options many are easy to deduce when you recognize that the permissions and database are shared.

1. To set up my scenario I created a page that was visible to all users, and one that was visible only to select users (that is how I control who gets to see my special instance with different filtering (not using the module permissions).
2. Create my FnL on my public page, then copied (add module: "existing") as a reference (make sure "Copy Module" is de-selected) and set it to "Inherit View permissions from Page"
3. Then  I created my custom filter and your done.  Anyone with view permissions for that page will be able to see the module as well and you will have a custom filter that displays whatever you want.  Everyone on the other page will have the more restive filter. 

For your info I had an additional requirement in that I needed anonymous people to be able to submit new records but not have them display unless approved by one of my selected approval users and these approval users could not only approve new submissions but also submit records themselves..

1. Create a boolean field Approved=Yes/No
2. Set the field as "Restricted Form Field"and default value to "No" and not to display on the list
3. Set my filter on my public page to only show "yes"
4. Set my filter on my private page to only show "No"
5. Gave my selected Approval users the following permissions: Edit Also Restricted Columns=Yes since I want them to be able to edit and change the state.  In your case if you just want them to only see the state you might choose instead "Display All Columns".  I also gave my approval users users "Edit Record" and "Delete Record" because they are managing the database (suspect the "Edit Also Restricted Columns" would rely on the "Edit Record" being enabled first.
6. I give all my public anonymous users only "view" (inherited from page) and "Create Record/ Submit Form" permissions which allows them to submit a record which is never displayed to the public unless approved. 
7. I send out a notification email to my approval users when a new record is submitted and they can review/modify/approve or delete.