Timill Platform Documentation

Roles

What each role may do, and how to define your own.

Roles define what members are allowed to do within a group. Timill uses role-based access control (RBAC) with support for fine-grained, field-level permissions.

Creating and editing roles#

Create custom roles from the roles administration page. Each role has a name and a set of permissions that control access to items, pages, and group administration.

Permissions#

Permissions are organized by area (items, pages, admin). For each area you can grant abilities such as create, read, update, and delete. Permissions are additive – a role only has the capabilities explicitly granted to it.

Field-level permissions#

For tighter control, configure field-level permissions on a role to restrict which fields a member can view or edit on a given item type. This is useful for hiding sensitive fields (salary, internal notes) from certain members while still letting them work with the rest of the item.

Built-in roles#

Groups include built-in system roles — including an administrator role that cannot be deleted. Create additional roles to match your team’s structure (for example viewer, contributor, manager).

Tips#

  • Start from a read-only role and grant abilities up, rather than starting broad and trying to lock things down.
  • Use field-level permissions instead of duplicating an item type when only a few fields need to be hidden.