Teams: Getting Started

Teams allow you to organise your jobs and contracts into groups and invite other people to your Client account to manage it on your behalf.

By using the Teams feature, you can:

• create any number of Teams within your Work for Impact account,
• invite any number of Members to your account,
• assign different permissions to the Members so that they can access only the selected areas of your account,
• assign Members to Teams so that they can manage jobs and freelancer contracts within these Teams.
  
  

Basic Concepts

This section explains the terminology we use when talking about Teams and various new concepts introduced together with Teams.

Organisation

"Organisation" is a new name for your Client account. Before the introduction of Teams, only the owner of the account could access and manage it, as well as post jobs and hire freelancers from this account. With Teams enabled, a Client account is called "Organisation", and more than one person can be authorised to access and modify it.

Team

A unit within an Organisation, grouping jobs and assigned Members.

Member 

A person invited to the Organisation. A Member can switch from their personal Work for Impact account to Organisation account at any time. A Member can be added to a Team, and, depending on their Role, they can perform different actions within the Organisation and their Teams.

Role

A predefined set of Permissions assigned to a Member. A Role define Member's scope of authorisation, that is, it dictates which actions are available to a Member. There are two types of Roles:

Organisation Role
Organisation Role is the role that defines which parts of the Organisation a Member has access to. Each Member must have an Organisation Role. The default Organisation Roles are as follows:

• Owner: the proprietor of the account, authorised to perform all actions. There can be only one Owner per Organisation and this Role is not transferable.
• Manager: a Manager can has access to the Organisation's profile and all jobs. They can perform all the actions available to the Owner, which means that they can run the Organisation on the Owner's behalf.
• Recruiter: a Recruiter is responsible for managing jobs and is not allowed to access or modify the Organisation's profile. They can post, edit and remove jobs, send invitations and manage proposals. They can send contract offers and react to the terms change proposals. 
• Associate: an Associate is not allowed to trigger any actions on an organisational level and they can't see any jobs unless they're added to a Team. In this case, they will only see the jobs within this Team. 

Organisation Members which are permitted to modify Roles, can add custom Organisation Roles and assign them their own permissions.

 

Team Role
Team Roles expand the scope of the Organisation Roles. It means that if a Member has an Organisation role (which is a higher-level role)  which allows them to manage jobs, they will be able to manage jobs in all Teams. There's no need to add them to Teams or assign them Team Roles.

Team Roles are useful for the Associates, who are the lowest tier of the Organisation Members. If an Associate is not added to any Team, they won't be able to see any jobs or contracts. To authorise them to perform any actions, you have to add them to a Team and assign them a Team Role. The default Team Roles are as follows:

• Team Manager: they can manage Team Members by reassigning their roles or removing them. They have full access to the jobs assigned to their Team. 

•  Team Recruiter: they are responsible for managing jobs within their Team. They can post, edit and remove jobs, send invitations and manage proposals. They can send contract offers and react to terms change proposals.

• Team Member: they can manage contracts assigned to the Team but cannot recruit freelancers. They can accept and reject milestones, give bonuses, review time logs and manage disputes.

Organisation Members which are permitted to modify Roles, can add custom Team Roles and assign them their own permissions.

Permission

A Permission is an authorisation to perform a specific actions. Permissions determine whether the Members are allowed to manage particular areas of the Organisation. Here are some examples of the available Permissions:

• manage client profile: a permission to manage all the information visible on the Organisation's profile, like name, description, profile image, or background image.
• view financial reports: a permission to access the reports page and the transactions list (including the purchases list and contract payments).
• manage contracts: a permission to change contract terms, accept and reject milestones, give bonuses, review the freelancers' time logs and manage disputes.

You can see all available Permissions here: Managing Roles and Permissions

👉 Next article:

Organisation Overview

 

← Back to all Teams articles