Those options merely control which is the user's default login shell. A shell takes a user's commands and executes them. Permissions, on the other hand, are properties of a file on the filesystem, and so the two are completely separate. I.e., if you do/don't have permissions to do something while running bash, you will/won't have permissions to do it while running csh.
One method that can blitz tricky permission issues, but that comes with a security risk, is the suid
bit. If this is set, then it means that any user that executes a file does so with the permissions of the file's owner
. This is in fact necessary for certain applications that must access protected areas of the kernel, but need to be run by everyday users. Of course, this does mean that there's the ability for these files to do anything they want with root privileges, so they must be carefully maintained. See this TLDP page
which mentions this issue.
To add the suid bit, make sure that your file is world- (or preferably, group-) executable, and then issue
If you 'ls -l', you should now see an 's' in the sixth (and possibly ninth) permission position, instead of an 'x'.