When using a browser shortcut/bookmark to try to open a specific project, you might be logged in to a different Asana account than the one that has access to that project. You may have access to other projects within that organisation/workspace, so the nav shows the projects you should have access to. When this occurs, the panel on the right shows:
Looks like you need access to this project. Would you like to send a request to the owner?
Request access (blue button)
You’re currently signed in as email@email.com.
However, neither the URL nor the page shows which project this is. That makes it hard for the user to know if they are requesting access or not for the correct project if they click the button.
Note that the user probably has the link either because they actually do have access to this project with a different account, or the link was provided by another user in an Asana task that they did have access to. In other words, the user is part of the organisational workspace somehow. (Note that the different blue button shows the system already recognises this is different from a user who does not have access to the org at all. Also it seems that if the user has zero connection to this workspace then Asana just rolls back to load the workspace the user does have access to, so the project name would not be exposed to a user who is not part of the workspace.)
The ask here is for the project name to be displayed somewhere on the page or in the browser tab title.
(Edit: Not sure why Discourse is not including paragraph breaks, neither in the preview nor in the displayed message.)
The User has both Asana Accounts A and B and is logged in to both.
Account A has access to Org 1 and Org 2. In Org 2, this account has access to Projects X and Y, but not Project Z.
Account B has access to all Projects in Org 2. Project Z is bookmarked.
The User was last using Account A in Org 1.
The User clicks on a link or bookmark to Project Z in Org 2. Because Account A does not have access to this project, the “Looks like you need access to this project. Would you like to send a request to the owner?” notice appears, with the blue button to request access.
However, nothing here makes it clear which project this is referring to, nor who the owner of the project is.
As Account B is already has access to this Org, would it not be reasonable that they can see a little more info about the project so they can be certain they are requesting access to the correct project, or conversely, realise that they are using the wrong Account and need to switch to the one that has full access to this Org?
If there is concern that a guest account who has access to an Org should not be able to see project names and project owners for links they may have been given (e.g. in a comment in another task), then Asana still knows behind the scenes that the User has an active Account with access - as that determines the notice and blue button shown - and so could use that to display or not display more info?
I don’t believe Asana would implement this change because it violates privacy expectations.
You may a distinction requesting the project name is shown if you’re a member of the org, but how it would it then avoid disclosing a project name that project members intend to keep private, perhaps “Upcoming Layoffs?”
“Upcoming Layoffs” is perhaps a fair enough scenario for not showing project names in general then.
However, it brings it back to the background of the request that this is a User who DOES have access to that project, it just depends on which Account is active when the page was loaded:
“Asana still knows behind the scenes that the User has an active Account with access [to that project] - as that determines the notice and blue button shown - and so could use that to display or not display more info?”
