remo · documentation
RU

Roles and capabilities

The exact table: what each role may do, where a role comes from, and how a public link differs from a grant.

Status: available updated 2026-10-28

Roles

Role What it can do
Просмотр (viewer) read the board, export a visible image
Комментарии (commenter) read the board and write in the discussion; cannot change objects
Редактор (editor) change content, comment, share (if policy allows), export, take a backup, facilitate
Со-владелец (co-owner) everything Редактор can, plus manage the board and appoint co-owners
Владелец (owner) everything, including transferring ownership and deleting

Capabilities

Capability Viewer Commenter Editor Co-owner Owner
board.read yes yes yes yes yes
board.comment — yes yes yes yes
board.edit — — yes yes yes
board.share — — yes* yes yes
board.export yes yes yes yes yes
board.backup — — yes yes yes
board.facilitate — — yes yes yes
board.manage — — — yes yes
board.transfer — — — — yes
board.delete — — — — yes

(*) An editor can share only if the organisation policy allows it.

Co-owner is a management role. Appointing, promoting, demoting or removing a co-owner requires board.manage. board.share is not enough, even when a person grants the role to themselves.

Sources of a role

Source How it appears
Direct grant the role is granted to a person on the board
Team the person is in a team, the role is granted to the team
Organisation the role is granted to the whole organisation; a guest does not inherit it
Public link a board property; grants board.read only

When several sources apply, the strongest role wins.

Public link Role on the board
Account needed no yes
What it grants read only the capabilities of the role
Comments unavailable with board.comment
Export forbidden per role (board.export)
Backup forbidden per role (board.backup)
Password and expiry yes no

Where to go next

Access: organisation, team, board, role — why the model is built this way.