Field Access

By default, all users have full access to bespoke fields. Add entries to [gb_role_restrictions] table to change access to various roles to either display only or hidden.

Entries for bespoke fields done slightly differently to system fields (described in Role Restrictions page).

Key Entries Required in gb_role_restrictions

Below are key entries required in [gb_role_restrictions] to create bespoke field restriction.

Field Descriptions

role_id

Value from [gb_roles] role_id. Identifies role to apply restriction.

module

Module where bespoke field located. Use 'fm' (Fleet Management) for clients, quotes, and contracts.

page

Screen where bespoke field located:

• clients

• quotes

• contracts

sub_page

Sub-page or tab where bespoke field located. Use 'other' for all bespoke field restrictions.

type

Type of restriction. Use 'field' for bespoke field restrictions.

name

Field name from [gb_bespoke_fields] field_name. This is field_name, not screen alias or label.

restriction_type

How field restricted. Options:

• 'display_only': Role can view field but cannot edit

• 'hidden': Role cannot see field at all

bit_array

Leave as '0' for bespoke field restrictions.

conditions

Leave blank for bespoke field restrictions.

Notes

• Bespoke field restrictions applied per role, per field

• Multiple restrictions can be applied to same field for different roles

• display_only allows viewing but prevents editing

• hidden completely removes field from view

• Use [gb_bespoke_fields] field_name (not screen alias) in restriction entries

• Default access is full read and write when no restriction exists

• Refer Role Restrictions page for system field restriction differences