Field Permissions

CityScreen Deals has two layers of access control for entity data:

  • Entity-type permissions control whether an employee can read, update, or delete records of a given entity type. These are configured through roles and permissions.

  • Field permissions control whether an employee can see or edit individual fields on those records.

This page covers field permissions — the finer-grained layer.

How field permissions work

Each field on an entity type can have its own permission grants. A field permission specifies:

Action

What the employee can do with the field — read it, update it, or delete it.

Scope

Whose records the permission applies to:

  • Own — only records the employee created or is assigned to.

  • Group — records owned by any member of the employee’s group.

  • Any — all records, regardless of ownership.

A field permission grant is specific to one field of one entity type.

How field permissions compose with role permissions

Field permissions do not replace role permissions — the two layers work together.

An employee’s effective access to a field is the intersection of both layers:

  1. The employee’s role must grant entity-type-level access (for example, read access to records of a document type).

  2. The employee’s field-level grants must include the specific field.

If a role grants read access to a document type but the employee has no field-level read grant for a particular field on that type, the field is hidden from that employee’s view of the record.

Conversely, if the employee has a field-level read grant but the role does not grant entity-type-level access, the employee cannot see the record at all — and therefore cannot see the field.

The organization’s main administrator can always see and edit all fields, whatever field-level grants exist.

Default grants for new fields

When a new field is created, the system automatically grants the creating employee’s roles the following field-level permissions:

  • Read Own

  • Update Own

  • Delete Own

These defaults give the employee who created the field immediate access to it on their own records. Other employees and broader scopes (Group, Any) must be granted explicitly through the permission configuration.

Managing field permissions

Field permissions are managed through the same administration interface used for role permissions. Administrators can grant or revoke field-level permissions for any role, at any scope, through the roles and permissions interface. Before you widen access to a field, confirm who is asking and that they are entitled to the data.

See roles and permissions for the full permission model.