GridLane adds an app-level permission layer on top of HighLevel access. Use it to control who can view or edit specific fields, create records, delete records, manage views, and use associations.
Open permissions
Open the gear icon in the grid header and choose Permissions. The panel lists roles and users from the active HighLevel account.
- Choose a role or user.
- Select the object or field scope.
- Set view, edit, create, and delete access.
- Save the rule.
Rules can apply to a whole object or to individual fields.
What permissions control
- Whether a user or role can see a field.
- Whether a field can be edited.
- Whether records can be created or deleted.
- Whether views can be published or shared.
- Whether association links can be added or removed.
An admin session can manage account-wide rules. A non-admin user is evaluated against the matching role and user rules.
Field visibility and bulk actions
Field permissions are applied before the grid is displayed. If a field is hidden, it should not appear in the sheet or in the field selector. Bulk updates still respect the underlying record permissions and can fail if the user cannot edit a selected field.
Views and permissions
Saved views have sharing settings separate from permission rules. A shared view can be visible to the account, while field and record permissions still determine what each user can see or change.
Blueprint permissions
Blueprints can include GridLane permission rules. A blueprint-managed rule can be updated by its owning blueprint. A local rule that conflicts with a blueprint is surfaced as blocked drift instead of being silently overwritten.