Collaboration and roles

Who can access an area

The owner manages members in «Участники области» (Area members), available from the menu. Viewers read and navigate, editors change permitted materials, and owners manage access. API/OAuth access is further limited by granted scopes and current roles. The server checks role changes or revocation on the next operation.

Before inviting someone, check that descriptions, SQL fragments and voluntary attachments are suitable for them. A guest cookie or private area link is not an invitation.

Hand off an investigation

1. Write the goal in the task description and decisions as separate journal entries.
2. Name sheets clearly and save the relevant table selection.
3. Grant your colleague an area role and send the saved map link.
4. Ask them to open the sheet and check its description, JOIN evidence and plan.

The result is shared context without explaining the entire database again. Your colleague’s last open tab and camera remain personal.

Discussions have a separate boundary

Area or task access does not automatically grant access to every private conversation. An appropriate own channel and explicit thread membership are required. Chats of one owner remain separate participants; never borrow another chat’s proof. «Обсуждения» shows messages and research task status. Asking a question authorizes research within an already permitted environment, not arbitrary code changes or SQL execution.