Applies to: Pro · Enterprise
Last updated: 17-Jul-2025
Overview
When you start a collaboration session, you control exactly what each participant can do. Kazinex provides six preset permission levels and the ability to create fully custom permission sets. Permissions are enforced in real time — blocked actions are silently prevented before they reach the shared document.
Permission Presets
| Preset | Label | What It Can Do |
|---|
| Full Access | Full Access (Host) | Edit everything, manage permissions, and remove peers. Host only. |
| Editor | Editor (Full edit) | Edit all schedule data. Cannot manage permissions or remove peers. |
| Status Updater | Status Updater (Progress only) | Update actual dates and percent complete. Read everything else. |
| Reviewer | Reviewer (Read-only) | View all data. Cannot make any changes. |
| View Only | View Only | View schedule data. Cannot make any changes. |
| Custom | Custom | Individually selected scopes (see below). |
The default guest preset is Editor. You can change this before sharing the invite link.
Permission Scopes
Permissions are organised into 34 scopes across 11 domains:
Activity (5 scopes)
| Scope | Description |
|---|
| View activities | See all activity data |
| Edit activity fields | Change names, durations, dates, and other fields |
| Edit activity status | Update actual dates and percent complete |
| Add activities | Create new activities |
| Delete activities | Remove activities from the schedule |
Relationship (4 scopes)
| Scope | Description |
|---|
| View relationships | See all dependencies |
| Add relationships | Create new dependencies |
| Edit relationships | Change relationship type or lag |
| Delete relationships | Remove dependencies |
WBS (5 scopes)
| Scope | Description |
|---|
| View WBS | See the work breakdown structure |
| Add WBS | Create new WBS nodes |
| Edit WBS | Rename WBS nodes |
| Delete WBS | Remove WBS nodes |
| Move WBS | Rearrange WBS hierarchy |
Calendar (2 scopes)
| Scope | Description |
|---|
| View calendars | See calendar definitions |
| Edit calendars | Modify working hours and exceptions |
Resource (4 scopes)
| Scope | Description |
|---|
| View resources | See the resource pool |
| Add resources | Create new resources |
| Edit resources | Change resource properties |
| Delete resources | Remove resources |
Assignment (4 scopes)
| Scope | Description |
|---|
| View assignments | See resource assignments |
| Add assignments | Assign resources to activities |
| Edit assignments | Change assignment quantities and rates |
| Delete assignments | Remove resource assignments |
UDF (4 scopes)
| Scope | Description |
|---|
| View UDFs | See user-defined field values |
| Add UDFs | Create new UDF types |
| Edit UDFs | Change UDF values |
| Delete UDFs | Remove UDF types |
Activity Code (4 scopes)
| Scope | Description |
|---|
| View activity codes | See code types and assignments |
| Add activity codes | Create new code types and values |
| Edit activity codes | Modify code types and values |
| Delete activity codes | Remove code types and values |
Project (1 scope)
| Scope | Description |
|---|
| Edit project settings | Change project name, data date, and schedule options |
Scheduling (1 scope)
| Scope | Description |
|---|
| Run schedule calculation | Execute the CPM forward/backward pass (F9) |
Session (2 scopes — host only)
| Scope | Description |
|---|
| Manage permissions | Change other peers' permission levels |
| Remove peers | Kick a participant from the session |
Setting Permissions
Before Sharing
- Click Collaborate in the toolbar.
- In the share dialog, use the Default Guest Access dropdown to choose the preset for new joiners.
- Click Start Session.
During a Session
- Click the lock icon in the collaboration toolbar (visible to the host only).
- The Permission Dialog opens with:
- A Preset selector dropdown at the top.
- Expandable panels grouped by domain (Activity, Relationship, WBS, etc.).
- Checkboxes for each individual scope.
- Choose a preset, or toggle individual scopes to create a Custom set.
- Click Apply.
When you toggle individual checkboxes, the preset automatically switches to Custom.
Entity-Level Restrictions
Beyond scope-based permissions, the host can restrict edits to specific entities:
| Restriction | Description |
|---|
| Allowed Activity IDs | Comma-separated list of activity IDs. The guest can only edit these specific activities. |
| Allowed WBS IDs | Comma-separated list of WBS IDs. The guest can only edit activities under these WBS branches. |
Leave these fields empty to allow editing on all entities (within the granted scopes).
How Permissions Are Enforced
Every edit command passes through the Collaboration Middleware before it reaches the shared document. The middleware:
- Identifies the entity type and operation category (read, add, edit, delete, move).
- Looks up the required scope (e.g., editing an activity field requires
activity:edit-fields).
- Checks whether the peer's permission set includes that scope.
- If the peer also has entity-level restrictions, checks whether the target entity is in the allowed set.
- If any check fails, the command is silently blocked and a console warning is logged.
The host bypasses all permission checks.
Tips & Best Practices
- Use "Status Updater" for field teams — they can report progress without accidentally changing the schedule logic.
- Use "Reviewer" for stakeholders — gives full visibility with zero risk of accidental edits.
- Use entity restrictions for parallel WBS editing — give each subcontractor access to only their WBS branch.
- Review permissions periodically during long sessions to ensure they still match the workflow.