{"id":2574,"date":"2016-03-07T11:49:42","date_gmt":"2016-03-07T08:49:42","guid":{"rendered":"https:\/\/everhour.com\/blog\/?p=2574"},"modified":"2025-03-21T12:30:18","modified_gmt":"2025-03-21T09:30:18","slug":"teams-everhour-2","status":"publish","type":"post","link":"https:\/\/everhour.com\/blog\/teams-everhour-2\/","title":{"rendered":"Teams in Everhour 2"},"content":{"rendered":"

We continue working on Everhour 2<\/a> and this time I\u2019d like to explain another important architectural solution that we\u2019ve been discussing internally for a long time and are working on actively at the moment namely, teams, groups, and time isolation between different accounts.<\/p>\n

<\/p>\n

Team Definition & Adding Members<\/h3>\n

Let\u2019s first define the term \u201cteam\u201d. It refers to a company, an organization, or a legal entity and includes employees, integrations, and projects. It has nothing to do with \u201cteams\u201d in 3d party apps\/integrations.<\/p>\n

Admin adds team members by manually entering their email addresses. And here it\u2019s important to note that the same email may be associated with only one team. If the user already exists, he must either use a different email or ask to remove his account from the other team. In such a case the time he reported will remain in the previous team and won\u2019t be transferred.<\/p>\n

Initially, we aimed to import users from the integration<\/a> as we do with projects but then abandoned the idea due to a number of technical issues, including that not every app provides real emails via their API.<\/p>\n

Users may try signing up to the point of obtaining an invite (in case admin has already created an account and integrated with a 3d party tool, but has not invited anyone yet). In such a case we will already identify his coherence with a team and will offer him to join, but first, we will send an approval request to the admin.<\/p>\n

User Groups<\/h3>\n

\u201cUser groups\u201d is the ability to organize a number of users under a single title.<\/p>\n

This functionality is designed to simplify the process of selecting multiple users in reports, filters, during internal projects assignment and it\u2019s an additional aggregation to see reported time. For instance, \u201cdevelopers\u201d group reported 100h, \u201cdesigners\u201d – 50h.<\/p>\n

In the future, we may add the ability to assign permissions for the groups.<\/p>\n

Data Sharing<\/h3>\n

The last important topic is collaboration and sharing data between different teams. For convenience, I propose considering a few different scenarios.<\/p>\n

Scenario 1<\/strong><\/p>\n

A company is using  Everhour to manage invoicing of hourly services and estimates in order to track how accurate its proposals are. It has its team, projects, integrations.<\/p>\n

A company acquires a new customer.<\/p>\n

For this purpose, they create a new project, tasks, assign estimates and start reporting time. The manager regularly exports data and sends custom progress reports to the customer. The customer does not require access to Everhour and does not have an account.<\/p>\n

 Everything is pretty simple. Everyone is happy.<\/p>\n

Scenario 2<\/strong><\/p>\n

All as before, but now the customer says, \u201cGuys, I also want to report time into the project, build reports myself and see embed estimates right inside Asana or Github\u201d.<\/p>\n

OK. The company may add him as a regular team member (and pay for an additional user). The client will have access to a single project and see the time of all employees assigned to the same project.<\/p>\n

When the project is over, the company removes the client from the team and respectively removes his access to the data.<\/p>\n

Solved!<\/p>\n

But, in this case, the client\u2019s time will always be included in project invoices along with the company’s employees, and it should be manually excluded all the time.<\/p>\n

Scenario 3<\/strong><\/p>\n

A company has an account in Everhour and a client has it there too. Each manages its own team, projects, and integrations.<\/p>\n

It may happen that members from different teams are working on the same project (access to the project is managed outside Everhour, for example in GitHub or Asana).<\/p>\n

In this case, each team will only see their time and estimates. In other words, data is isolated.<\/p>\n

Obvious disadvantages?<\/strong><\/p>\n

We can see only one drawback.<\/p>\n

Let\u2019s suppose I\u2019m a manager of such a joint project. When I look at the current milestone where the tasks of both teams are combined, I would not see all estimates and total time, just my colleagues\u2019.<\/p>\n

 Why is that?<\/strong><\/p>\n

The main goal of our product – time management within a particular company.<\/p>\n

The vast majority of our users (except individual freelancers) work on a single team and their time should be combined in one place.<\/p>\n

As of now, we faced a lot of cases when people have accidentally created\/joined the wrong team and reported time incorrectly and that is not acceptable for invoicing purposes. Could result in a very expensive mistake!<\/p>\n

Estimates is a part of the internal process. External collaborators can adhere to different standards and whatever reason may change assessments, report superfluous or irrelevant time, etc. Which breaks the process for the other party.<\/p>\n

In addition, it is a question of privacy. Maybe someone does not want to disclose specific figures, who was involved in the process, and to what extent.<\/p>\n

For the purposes of collaboration and management, each party can pre-assess its scope and send it as a google spreadsheet. In any case, the evaluation should always be discussed.<\/p>\n

In the future, we may consider functionality to share specific reports.<\/p>\n\n\n