Overview

Access levels in Custral define what actions a user or group can perform on an Entity. Each level builds on the one below it, giving progressively more control. They are consistent across all parts of the platform. From Objects and Records to Views and Workflows.

Levels overview

Level	Description	Common uses
None	No visibility or access to the Entity.	Hidden data, restricted items.
Read	View information but cannot make changes.	Reports, dashboards, shared views.
Comment	View and leave notes or mentions.	Collaboration without edits.
Edit	Update Records, fields, or configurations.	Day-to-day contributors or editors.
Delete	Remove Records or items that can be edited.	Team leads managing data hygiene.
Admin	Manage settings, automations, and permissions for the Entity.	Department or workspace managers.
Owner	Full control, including transferring ownership and adjusting inheritance.	Founders, administrators, or entity creators.

How access levels work

Each Entity (whether it’s an Object, Record, View, or Workflow) has an Access Control List (ACL) that defines who can perform what actions. Access can be granted to users or Groups, and higher levels automatically include all permissions from lower ones. Example flow:

A user with Edit access can also Read and Comment.
A user with Admin access can edit, delete, and adjust the ACL for that Entity.
Only the Owner can transfer ownership or change inheritance rules.

Choosing the right level

Goal	Recommended level
Give visibility without edits	Read
Allow collaboration and feedback	Comment
Let a team manage content or data	Edit
Maintain system settings or automations	Admin
Full control and responsibility	Owner

Grant the lowest level that does the job. A level you can explain is one you can audit later, and raising it for one person later is one click.

Permission Hierarchy
Users · Groups