Can a field be created and used on more then 1 template, and that field have different access rights on each template? Or will it inherite rights?
The field access rights are set per field and can't be differentiated by template. It may be best to create multiple fields for multiple templates if different access rights are required.
Why then can we set field access on a template to either Deny, Read etc.? I can set the same access at the time I create the field, also if I need to create a common field like "Company Name" I would need to create
"Company Name For template1", "Company Name For template2" etc I could end up with a lot of fields that are meant for one thing "Company Name".
The template 'read' security controls whether the user can see the template itself - it doesn't actually control the security of the fields inside of it.
Can you expand on your scenario where you have the same field but some users should only be able to modify it in certain templates?
A standard Field "Company Name" would be used on a Invoice Template, Staff in Accounts payable would have access to edit it. Other staff Read only.
On a template called "Contracts" the same field "Company Name". Staff who are responsible for dealing with suppliers would have full Access but possibly not 'Account Payable', both templates are filled in via a Work Flow the gets the data from a ERP system,
The Field "Company Name" is always filled in from a custom activity with ERP data.
Creating more then 1 field to represent the same data adds to extra work to Searching, etc.