Workspaces shouldn't appear under Teams heading in the left sidebar

I’m not sure when this started, perhaps with the sidebar redesign that’s still rolling out, but now workspaces appear under the Teams heading:

This is confusing because a workspace is not a team, and in fact a common way of describing workspaces, in particular to contrast them with organizations, is that workspaces do not offer teams.

In the past, there was no “Teams” heading in the sidebar of workspaces; correctly so, I believe, because it didn’t apply.

Curious if @Forum-team might have any info on this?

Currently the Guide article on Workspaces is inconsistent with this implementation:

Thanks,

Larry

3 Likes

@Phil_Seeman, @Arthur_BEGOU, others, please consider voting intead of/in addition to liking.

Thanks,

Larry

I agree that this is new. Wondering if there is an architecture change in the back end that could mean that all workspaces just become an organization with one team. then this change would make sense, but I do agree that this could create some confusion.

1 Like

Actually under the hood this has always been the case - every workspace has always had one “hidden” team.

1 Like

Correct @lpb , I still have a workspace with the old sidebar so I managed to take the below screenshot, just for the record. ‘Business Demo’ is the name of the workspace, which appears as a Team (that is not collapsible) but without the heading ‘Team’ as in the new sidebar.

It would perhaps make sense to make an exception in the sidebar for workspaces, i.e. to rename the ‘Team’ section to ‘Workspace’ which I assume is what you are suggesting, right?

It seems Asana have actually already gone to the extend of making that exception by naming the section ‘Team’ instead of ‘Teams’ as found in organisation instances.

1 Like

Hi all, thanks for sharing your feedback! As you mentioned, every workspace has always had one team in the sidebar, but it didn’t have the Teams heading. This is probably where the confusion comes from. I’m going to send a note to our product team :raised_hands:

2 Likes

Thanks, everybody!

It’s confusing now, that’s my main point, and that there’s a plan that we don’t know about, though it’s already manifested in the implementation.

I’m not wild about the use of Team here, though I’ll wait to hear what the plan is. The confusions are:

  • Workspace = Team in this case
  • Use of Team here now overloads that term in a confusing way

Both would be remedied by a new term, like Workspace Team, though I hope the product team has something even better in mind.

Thanks,

Larry

3 Likes