Lesson 3

Project’s Team Managemen

!Image

Parta\.io

Why the Extra Layer?

You might be wondering: "If I’ve already set up my Workspace roles, why do I need to manage people on a project level?" In the workspace, user has a permanent role and set of permissions\. But on a specific project, their level of responsibility might change\. Project\-level management allows you to have additional capabilities to interact with Project, in addition to the capabilities provided by the role in the company\.

We went over who could benefit from each permission, not let’s see more in\-depth description of each one\.

Adjust permissions accordingly to control what each teammate can or cannot do within the project\.

Adjust permissions accordingly to control what each teammate can or cannot do within the project\.

!Image

Here Anna is helping Artem reviewing the course, with the only Project permission being "Comment"

!Image

In this project Anna is a co\-creator for Artem, having permisisons neccessary for building content \- "Content", "Content´\+" and "Pro"

!Image

For this case Anna is taking on the role of a distributor, with the added "Share" permission

!Image

Ding\! Here comes a helpful tip

Sometimes you have multiple co\-creators working on different parts of the same course\. When you're finished completing your part, you can make sure nobody will make any accidental changes in your content by locking the section from editing\.

Let’s look at how project\-level management can solve complex collaboration hurdles\.

Read the case study and find the most fitting option\.

Case 1: SME Localization Review

You need your SMEs, that are invited to the workspace as Guests, to review the translated version of your course, make adjustments and leave comments just in this course\.

What do you need to do?

Options:

• [ ] Add Permission "Creator" to their account on the workspace level and add them to the Project
• [ ] Add them to the Project and give them the "Pro" permission
• [ ] Change their role to "Member" on the workspace level and add them to the Project
• [x] Add them to the Project and give them the "Content" permission

[Button: Submit]

Case 2: Design Polishing

You have a designer in your department, who should work on layouts and create custom interactions, but only in specific module of courses\. They don't have acess to your company's workspace yet\.

What do you need to do?

Options:

• [x] Invite them as "Guest" with "Content" and "Pro" permissions
• [ ] Invite them as "Guest" with the full set of permissions
• [ ] Invite them as "Member" to the workspace with "Content" and "Pro" permissions
• [ ] Invite them as "Administrator" without any permissions on a workspace level

[Button: Submit]

Case 3: Distribution

For your project, you need help distributing the final version across your platforms, but without the risk of your teammate making accidental changes\. The teammate is already a Member in the workspace\.

What do you need to do?

Options:

• [x] Change their role to "Guest" and invite them to the Project's team
• [ ] Invite them to the Project's team without any permissions
• [ ] Invite them to the Project's team with "Content" permission
• [ ] Invite them to the Project's team with "Share" permission

[Button: Submit]

If you were to set up your organization today, would you need just one workspace for everyone, or separate ones for different departments?

Let's see how we can combine everything with multiple workspace system\.

[Button: Next lesson]