If you need to enforce access control to the field, you should not use view customization as it is just a cosmetic behavior and can be easily bypassed.

For a real field/column access control, you should use one of the following options:

Option 1: Use the new field level access control

Using groups='group1, group2, ...' in field definition restricts the field to the specified groups. Currently, you cannot control specific read or write, only allow or prevent access.

In this case, you may create functional field that can be displayed for restricted users. The function for that fields must use the user id openerp.SUPERUSER_ID or integer 1 to read the original field, not the current user id.

from openerp import SUPERUSER_ID
....
class MyClass(osv.Model):
...
    def _myfield_reader(self, cr, uid, ids, name, args, context=None):
        values = self.read(cr, uid, SUPERUSER_ID, ids, ['myfield'], context=context)
        return {v['id']:v['myfield'] for v in values}

Option 2: Override create() and write() methods

By overriding these methods, you can raise AccessError exception if a restricted user tried to write that field value.

Option 3: Use fields.property field

Property fields are stored as ir.property records. So, standard record access control can be used to protect it. Check for example property_account_* fields defined for res.partner in account/partner.py in the account module.

If you need it widely, what you can do is override the fields_view_get method.

If this is only for few fields, you can create a readonly related field and use groups in xml to define which one is seen.

<field name="my_field" groups="group_editors"/>
<field name="rel_my_field" groups="group_viewers"/>

Basic field properties (Required,Readonly,Searchable) can not be modified by the configuration! must change the code in Python and preferably by adding a new module. but you can edit fields personalized.