Can I create saved searches that are public to all my users or does the saved search have to be created for each user?
Yes, it's possible. Check out http://answers.laserfiche.com/questions/112758/Global-SearchGlobal-Saved-Search which describes how to do it using trustee attributes.
The overall answer is yes, however it is much easier in Windows Client rather than the Web Client.
With the Windows Client, you can copy an existing saved search to the 'everyone' profile in the Laserfiche Administration Console. It will then display for all users. You can pick and choose which search to copy over.
With the Web Client, the only way I've found to do this is by copying all searches over to the 'everyone' profile in the Administration Console. This method is all or nothing, you can't pick and choose. So in our case, if there is a search that we want everyone to have, we have a designated profile that I build that search in, and then copy all of its saved searches over to the 'everyone' profile.
Does that make sense? I can go into further detail if you would like.
Evan's reply is mostly correct, but to clarify: it is possible to copy over individual Saved Searches from Web Client, but the procedure is much more involved. This is because Web Client doesn't save an individual Saved Search's XML into separate attributes. It saves them all to one attribute, and if it exceeds the character limit for an attribute, overflows to additional attributes. So if you copy the Saved Search XML at the attribute level, you will indeed copy all of the individual user's Saved Searches to Everyone.
The procedure for saving individual Saved Searches from one user to the Everyone group is:
1. Copy attributes from [WebAccess]SavedSearchesN from Admin Console/Management page to a text editor (do this from 0 to N)
2. Pick out the XML chunks that correspond to the searches you want to copy
3. Save the XML from desired searches to the Everyone group with same attribute format name ([WebAccess]SavedSearchesX from 0 and up)
4. If you need more than one attribute, create a new attribute [WebAccess]SavedSearches (with no numeric digit at the end) and set it equal to MULTI-ATTR:N where N is the number of attributes. This tells WA how many attributes it needs to load.
Admittedly, this procedure isn't the best. We're working on a new feature for 10.3 that will provide UI for this type of configuration and will make it much easier to set SavedSearches to global.