Skip to content
Gallery
Soko documentation
Soko documentation
Share
Explore
Settings

Users Roles

In SOKO, we distinguish between two types of user roles: Security Roles and Project Roles. Understanding the distinction between security roles and project roles in SOKO is crucial for efficient project and user management. Security roles provide a broad level of access across the platform, while project roles focus on specific projects, ensuring users have access to the necessary information tailored to their responsibilities.

Distinction Between Security Roles and Project Roles

Security Roles: Define what parts of the SOKO platform a user can access (e.g., Client view, User view, Finance view). Each security role grants access to different attributes, ensuring that users only see and interact with data relevant to their role.
Project Roles: Define access to specific projects within the platform, ensuring that users only interact with the projects they are involved in. Project roles determine also the type of notifications a user receives, ensuring that only relevant information is communicated based on their involvement in a project.

Security Roles

These roles define what views and attributes a user can access. Each security role grants access to different attributes. For example, a Financial Manager will have access to budget and financial data that an Artist would not see.

Client
Access Level: Can access only the Client view.
Attributes: Limited to client-specific data and interactions.
Guest Artist
Access Level: Can access only the User view.
Attributes: Limited to personal task management and basic project information.
Artist
Access Level: Can access the User view and Projects assigned to them.
Attributes: Access to tasks, project-specific details, can modified only status of assigned tasks.
Reviewer
Access Level: Can access the Review view and Projects assigned to them.
Attributes: Can review and approve work, access to review-specific attributes and feedback mechanisms.
Manager
Access Level: Can access the Users view and Projects assigned to them. Can create or delete project.
Attributes: Full project management capabilities, task assignments, and overview of team progress.
Financial Manager
Access Level: Can access all the views Manager can and additionally Bidding view and financial attributes. Has access to all the projects. Can create or delete projects.
Attributes: Access to financial data, bidding processes, and budget management.
Service
Access Level: Does not have access to any view; used for API only.
Attributes: API access for integrations and automated services.
Admin
Access Level: Can access all views.
Attributes: Full administrative control over all aspects of the platform, user management and system settings, excluding financial data.

You can change the User Security Role settings in Settings > User Management
⁠
image.png
⁠
⁠
You can change the default Access Level settings for different views in Settings > Security.
image.png
⁠
⁠
You can change the default Attributes Security settings in Settings > Attributes > Security.
⁠
image.png
⁠
⁠
Y

Project Roles

Project roles determine access to specific projects within SOKO. While security roles control overall access to the platform's views and attributes, project roles ensure that users can only interact with the projects they are assigned to.
Key Aspects of Project Roles
Access Control
Users with the same security role may have different project roles, restricting them to specific projects.
For instance, a Manager project role may only manage projects they are assigned to, not all projects in the system.
Role-Specific Notifications
Notifications are tailored based on project roles to ensure relevant updates are communicated efficiently. For example Manager is notified when a task reaches 100% of planned hours. Reviewer when there is a new version for review and Artist when a new note is created or when a task status changes to "Ready to start". See more about
Notifications
⁠
⁠

You can assign a Project Role in the Project Side Panel under the Assignees group.
⁠
image.png
⁠
⁠
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.