If they have OSD rights they should able to edit their scripts, the ones they have created. They will not be able to edit public scripts, only an Admin user can edit public OSD scripts.They can schedule them but can not change them.
We have 3 non-admin users who will be working with OSD. We'd like all 3 of them to be able to see and edit any of the scripts.
If the scripts are not public, 1 can't see the scripts created by the other 2 to know what scripts exist so as not to duplicate.
If the scripts are not private, they each cannot edit even their own scripts.
Making them an admin user looks to be the only way around this.
That is true. Non-admins edit any scripts but their own and cannot see any scripts but their own and public.
However, the scripts are text files:
Look at the \\CoreServer\Scripts share.
They can probably edit the scripts if they go directly to the file as NTFS permissions are different than LANDesk permissions.