PROJECT RESPONSIBILITY
Give the project team the right role for the work
Separate project ownership, management, contribution and viewing. Make the team explicit without treating every task assignment as unrestricted access.
Responsibility needs a visible structure
A project team is more than a collection of names mentioned in chat. Someone leads the project, someone can manage its membership, colleagues contribute to delivery and others only need to follow progress. Tsumira records those relationships at project level. The result helps the team understand who can operate the project and prevents a casual handover from being confused with full management authority.
Name the team and its roles
A project has an owner and explicit project members. Member roles distinguish manager, contributor and viewer. An optional allocation percentage records an intended involvement, not a measured utilization or payroll value. Managers can perform management operations within the relevant permissions; contributors can work on the project, while viewing remains a separate role. Choose the role based on what the colleague must actually do.
- Project owner and explicit members
- Manager, contributor and viewer roles
- Optional intended allocation percentage
Choose company visibility or a restricted project
A team-visible project can be read within the company according to the product’s project access rules. A restricted project narrows normal discovery to its owner and seated members, with owner/admin oversight. Reading and writing remain different questions. A colleague may be able to see a project without being permitted to change its plan, publish an update or manage the team.
- Team and restricted visibility modes
- Separate read and write authority
- Management operations remain permission checked
Keep assignment and leadership distinct
A task assignment identifies the people responsible for that piece of work. It should not be described as a blanket grant to every sibling task in a restricted project. Project membership and task-specific access are checked separately. Leadership roles also require appropriate human responsibility: assistant or bot participation must not be presented as autonomous project management or financial decision ownership.
- Task assignment is specific responsibility
- Project membership has its own access meaning
- Human responsibility for project leadership
A concrete workflow
Choose the owner
Decide who is accountable for the delivery outcome before adding the broader team.
Set the visibility
Use a company-visible project or a restricted one according to the work’s intended audience.
Add practical roles
Give managers, contributors and viewers the least role that supports their actual responsibility.
Maintain the team
Review membership when responsibilities change and assign individual tasks to the colleagues doing the work.
An illustrative working example
Example: a confidential customer engagement
A consulting lead creates a restricted engagement and becomes its owner. A delivery coordinator joins as manager, two specialists as contributors and an internal reviewer as viewer. Task assignees show who prepares each deliverable. When a specialist leaves the engagement, the project manager updates membership and redistributes open tasks. The team’s responsibilities remain explicit instead of depending on who happened to receive a chat message.
Questions about this topic
Does seeing a project let me manage its team?
No. Visibility and management authority are separate. Membership changes require project management rights and the corresponding operation permission.
Is allocation a real time report?
No. Allocation is an intended percentage for participation. Actual time belongs in Time entries and their reporting workflow.
Does assigning one task give access to the whole restricted project?
Do not assume that. Task-specific authority and minimum project context are distinct from full project membership and sibling-task visibility.
Can an AI assistant become the project manager?
The product keeps leadership and consequential management responsibility with appropriate human roles. AI assistance operates within its defined permissions and review process.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
